1. AGILE ORGANIZATIONS
ATHER IMRAN NAWAZ
MARCH 28, 2011
Fundamentals and Practices

2. Agility: the ability to think, move, adjust and
draw conclusions quickly

3. Fundamental Ideas …
 Knowledge Workers
 Software Development is Creative,
Uncertain, Complex and Artistic
 Novelty, Creativity and Urgency

4. History
 Industrial Practices
 Software Development is different
from Manufacturing
 Practices and then Processes Evolved
 ‘Evolution’ of Agile Framework

6. It is result of consolidation of experiences over the years
Agile is Evolutionary, not Revolutionary

7. Dilbert or Drucker Organizations?
OR

8. Linear, Sequential, Non-Iterative, Closed
(Assembly line model)
Waterfall Methodology

9. Being Agile is a mindset

10. Being Agile is a Culture

11. Blueprint of Agile Software Development Methodologies
Agile Manifesto

12. Principles of Agile
Framework

13. Customer Focus
 Satisfy Customer via
Early and Continuous
Delivery of Valuable
Software
 Working on Highest
Priority Items from
Customer

14. Embrace Change
 Accept Change as part of
process, not outside of it

15. Deliver Frequently
 Deliver Working
Software Frequently and
Incrementally
 Frequency: 2 weeks to 4
weeks

16. Everyone Works Together
 Developers, Testers,
Technical Writers, Business
People
 All Work Together Daily!

17. Customer Involvement
 Customers decide what
the team works on.
Deliver business value.

18. Self-Organized Teams
 Teams determine how the
deliverables should be
met
 Servant Leadership

19. People matter
 Projects revolve around
motivated individuals and
healthy work environment
 Collaborative

20. Face to Face Communication
 Should be the Primary
Means of Communication

21. Working Software
 Primary measure of
success

22. Sustainable Development
 Rhythm
 Work/Life Balance

23. Slices of Functionality!

24. Working Example
Software:
Website to Purchase Goods
manufactured by a vendor
 Register
 Browse Catalog
 Add to Cart
 Pay

25. Working Example
Focus
 Customer Focus
 Incremental Delivery
 Working Software
 Manage Change
 Provide Review
 Get Feedback
Develop a complete slice
of functionality that lets
users register, browse,
select and pay (with
limited functionality set)

26. Technical Excellence
 Continuous Attention to
Technical Excellence

27. Visibility
 Highly Transparent Teams
 Status, Accomplishments
all visible to entire Team,
Stakeholders and
Outsiders

28. Retrospective
 Continually Evaluate
Yourself!
 Feedback key to
Improvement

29. Slices of Functionality!

30. Agile Organizations

31. Facebook
 Focus on People
 Automated Tests
 Continuous Integration
 Daily/Weekly Release
 Multi-stage Deployment
 Accelerated Learning
 Quality is everyone’s
responsibility
 People select their own
Work and Projects
http://www.limitedwipsociety.ch/en/cas
e-study.html

32. Agile Transition
 Agile practices since
1999
 Bottom-up Transition
 Teams independently
adopted Scrum
 Pull Approach rather than
Push approach
 Two-Pizza Teams

33. Myths about Agile
 The Agile movement is not anti-
methodology, in fact, many of us
want to restore credibility to the word
methodology. We want to restore a
balance. We embrace modeling, but
not in order to file some diagram in a
dusty corporate repository. We
embrace documentation, but not
hundreds of pages of never-
maintained and rarely-used tomes.
We plan, but recognize the limits of
planning in a turbulent environment..

36. SAMI Index of Agile Adoption

38. Scrum

39. Agility is the Objective - Scrum is a means

40. Scrum – Components
 Sprint – Development Cycle (typically 4 weeks)
 Roles
 Product Owner
 ScrumMaster
 Team
 Artifacts
 Product Backlog
 Sprint Backlog
 Meetings
 Daily Scrum
 Sprint Planning
 Sprint Review
 Sprint Retrospective

41. Scrum – Process Overview
 Start with prioritized requirements (Product Backlog)
 Team selects requirements to work on during the first Sprint
(Sprint Planning Meeting)
 Team defines specific tasks to complete the requirements (Sprint
Backlog)
 Team goes in a 30-day Development Cycle (Sprint)
 Team meets daily to sync up and highlight issues (Daily Scrum
Call)
 Team develops, tests and documents the functionality being
worked on
 At the end of Sprint, team demo’s completed functionality to
customers and stakeholders and gathers feedback (Sprint
Review)
 Team Analyzes its performance (Sprint Retrospective)
 Product Owner reprioritizes the Product Backlog
 Team goes through the process again (Sprint 2, Sprint 3, …….
Release)

42. Scrum Process

43. Sprint

44. Product Owner

45. Product Backlog

46. Sprint Backlog

47. Sprint Backlog

48. Iteration Burndown

49. Challenges in Adoption
 Change of Mindset
 It’s More than Just a
Change of Terminology
 Have to Adopt the
Philosophy!

50. Can you use Scrum to manage
your Final Year Projects?