Quick overview of Aglie process used in software development. Customers are more engaged in this process and product acceptance rate will be higher.

1. Rev 2
rajesh.nadipalli@gmail.com

2. Concept/Idea
Business
Requirement Doc
Functional Spec
Doc
Engineering
Design Doc
Execution
Agreement
Build
Test
Customer Demo
Production
rajesh.nadipalli@gmail.com

3. Sprint
2
Customer Product Release
Sprint Sprint
Asks Backlog Planning
1 3
Sprint
4
rajesh.nadipalli@gmail.com

4. Release Sprint Sprint
Planning Planning Execution
• Iterative
•Tactical
• Product Vision • Iterative • Scope is fixed
• Release Theme •Plan Sprint window • Daily Scrums (15 min)
• Define User Stories • Plan number of Sprints • Product should be
• Prioritization • Break stories to shippable at end of
• Executive buy in development tasks Sprint
• Release Date • Estimate effort • Unfinished stories, go
(generally Quarter) • Identify Dependencies back to product backlog
rajesh.nadipalli@gmail.com

5. Place Stories
Into Sprints
Are stories too large – Epic vs Story ?
Dependencies?
Additional stories?
Will tasks be completed in
a sprint?
Buffer for uncertainty
Decompose
Estimate
Stories
Are stories still too large?
Will a story span multiple sprints?
rajesh.nadipalli@gmail.com

6. As a Facebook User
I want… INVEST
• an interface which I can view emails Independent
•from external sources ( gmail, yahoo etc) Negotiable
•each source should be visually separated Valuable
•updated every 5 minutes Estimatable
Small
So that I can … Testable
•get single view of all my emails
•be more productive
Acceptance Criteria
•Functional service with no severe bugs
•Data is accurate
•Data is up to date (max 5 min latency)
rajesh.nadipalli@gmail.com

7. Sprint Development
Sprint Planning
• Work on tasks
• Update progress daily
• Plan for next Sprint • Mark user story as complete
• Plan tasks per User Story (as per Def of Done)
• Estimate effort per task • User acceptance of
• Assign task to engineers completed stories
Sprint Updates
• Sprint Retrospective
• Update Product Backlog
rajesh.nadipalli@gmail.com

8. Each dev team should
decide this before
start of sprint and
follow this for every
user story
rajesh.nadipalli@gmail.com

9. Product Owner Scrum Master Dev Team
• Business • Process • Technology
Knowledge Knowledge Knowledge
• Vision & Goals • Facilitate • Self-organizing
• ROI • Remove • Deliver quality
• Communications impediments product 1-4
• Support PO and weeks
Dev team with • Follow agreed
process upon definition
• Metrics, Stats on of done
Sprint progress
rajesh.nadipalli@gmail.com

10. rajesh.nadipalli@gmail.com

11. rajesh.nadipalli@gmail.com