Agile Project Management and How to Approach

1. Agile Project Management

2. Waterfall [Big Bang] Vs Agile approach
• Waterfall Model came from construction and Manufacturing in
Industry. Last 15 yrs Agile Came from Software Industry.
• Waterfall more used in industry which resists revisiting and revising
like construction industry or manufacturing of any prior Phase once is
complete.
• Waterfall process is linear Sequential Flow [one u pass phase rarely
come back or iterate [partly in those industry cost of revisiting is high]
Or to go back to changes in requirements as result different project
different approaches to change management.

3. Agile [lean inventory] Vs Big Bang
• Agile Principles : Keep inventory of Requirements helps
customer/business to visualize more clearly.
• Less requirement = more easy to conceptualise product for customer
[what is coming out as product end result]
• Vs Big Bang Waterfall [All requirement at once before start of project]
hard for customer to give requirement at once. As result requirement
cutting each other, product no clearity till it arrives, only after arrival
start seeing more problem lead to rework..[which again redirects to
agile from water fall]

4. Typical SDLC Cost
• Earlier customer/business picks deviations less it cost. [requirement
change during implements all previous phase needs repetition.]

5. Agile 12 principles Or Agile Manifesto
• Highest priority to stratify customer in early [phases] continuous
delivery.
• Welcome change requirement even late phases in development. Agile
harness change for customer Competitive advantage.
• Deliver working software continuously from once a 6 months to once
month or week. Better get directions early from customer Early.
• Business people and developers should work together daily.
• Build project around motivated individuals give them environment
and support to get job done.

6. Agile 12 principles Or Agile Manifesto
• Most Effective method of requirement gathering is face to face
conversion.
• Working software is primary measure of success vs completion of
phases of development.
• Agile promote sustainable development: sponsors, users, developers,
should maintain constant pace indefinitely. [ hence focus motivated
individuals]
• Continuous attention to technical excellence and good design
enhance agility.

7. Agile 12 principles Or Agile Manifesto
• Simplicity – art of maximising the amount of work not done – is
essential [ less rework, better requirements user Story writing]
• [From The Nature: Sustainability theme e.g left leaning tree on road
to grab sunlight [not every tree grows same way ] Self organized
teams lead to better architecture , requirements and design for
customer.
• At Regular interval team reflect how to become more effective
At regular interval it tunes or adjust behaviour accordingly [Which side I
should grow to get more sunlight [tree] continuous shapes changes as
it evolves. How river flow ? Saying Pani apna rasta khod nikal leta hai.
Its continuous its agile its finding new ways to flow]

8. Waterfall Agile
Plan Driven Learning Driven
Infrequent Communication Frequent Communication
Deliver once Big design 9-12 month Big Bang Smaller delivery, business focus phases, [1-2 months]
Development done in layers, presentation,
persistence, business etc.
Develop end to end functional slices each month
which customer can see and conceptualize, developer
can control rework, management can direct real value
add.[like tree adjusting, water finding ways to flow]
Integration at Completion of each layer Continuous integration [daily builds]
Testing end of Project[functional testing]
Develop and Test at End
Fully automated Continuous testing [unit & functional]
Test Driven Development
High Cost To Change Low Cost to change
Must nail down requirements upfront Expects, accommodates, changes to requirements
Big design Upfront Rough Design upfront

9. Agile Vs Waterfall
Individual and
Interactions
Working software
Customer Collaboration
Responding to Change
Strong collaborative
teams
Process and Tools
Comprehensive
documentation
Contract Negotiation
Following a Plan
Individual Work
Packages
Over
Over
Over
Over
Over

10. Agile Controls : Is not like self growing Jungle
• Product Vision : High level summary of desired outcome.
• Release Planning : conducted at beginning of release as stories are taken by
team. A required agile activity.
• Iteration Planning : list of prioritize Feature that is converted into work during
release planning
• Daily Standup: Where Team member tell what they have accomplish, what is
upcoming work, what issues they are facing. [Daily Scrum]

11. Scrum Is management of complex Agile Projects

13. Scrum Lifecycle

14. Agile Terminology: Product Backlog