The document proposes adopting an agile software development process to address current project problems like siloed work and lack of transparency. It summarizes the agile manifesto and Scrum framework, including roles like product owner and Scrum master. An implementation plan is outlined, with activities like sprint planning, daily stand-ups, and retrospectives. Metrics are suggested to measure velocity, defects, testing coverage. Management support is requested to shift mindsets to agile, provide training, tools, and accept that initial sprints may not go smoothly as the team learns.

1. Agile Software Development
proposal
Sajjad Mansoor
6/7/13

2. Current project problems
• Individual disciplines working in silos
• Ineffective/inefficient handoffs
• Lack of ownership
• Product/feature knowledge not distributed
• Very little transparency in how/why “new
work” gets absorbed in development
• Extremely high Stress levels

3. Align with Management
Expectations
• Predictability:
» delivery ‘on schedule’
• Quality:
» no missing functionality
» better user experience
» no high priority defects
» build quality from the ‘get go’
• Efficiency:
» doing the right things, the first time
» responding to new demands in a timely fashion

4. Agile Manifesto
• Individuals and interactions over Processes
and tools
• Working software over Comprehensive
documentation
• Customer collaboration over Contract
negotiation
• Responding to change over Following a plan
That is, while there is value in the items on
the right, we value the items on the left more

5. Adopting SCRUM
SVRD

6. SCRUM Basics – 3 X 3
• 3 Roles
• Product Owner - TBD
• Scrum Master – Floating the idea of a rotating Scrum Master
• Scrum Team
• 3 Activities
• Sprint Planning
• Daily Scrums (Stand up meeting
• Sprint Review
• 3 Artifacts
• Product Backlog
• Sprint Backlog
• Burndown Chart(s)

7. Planning before we embark
• SVRD (Product Back Log – PBL)
• Needs prioritization by Product Owner
• Decompose PBL into
» Theme(s)/Sub theme(s), – Individual features?
» Epics – group of related User Stories
• Identify Teams/Roles
Product Owner (PO)
Scrum Master (SM)
Team
• High Level Estimation of PBL
• Define Sprint Duration & Number of Sprints
• Resource Plan
• Identify Team Room
• Training to the team in the new way of working
• Identify potential opportunities for Continuous Integration – Unit Test, Integration
Test, Static/Dynamic Code Analysis, SCM, Acceptance Test, Regression Test
• Brainstorm Test Driven Development, Pair Programming, etc..
• Identify workflow for defects vs. enhancement requests

8. Execution
• Sprint Planning Meeting
• Identify items in Prioritized Product Back Log
(PPBL)
• Decompose them into User stories which should
be (Important, Negotiable, Valuable, Estimatable,
Small, Testable) – further decomposed into Tasks
• Define Sprint Goal
• Define & Agree “DONE” for each Task

9. Sprint Execution continued.. Daily
Scrums (~ 15 minutes)
• Every Scrum Team member answers 3
Scrum questions:
» What did you do yesterday?
» What will you do today?
» What issues do you face?
• Members pick Tasks for next day
• Scrum Master updates Burndown

10. End of Sprint
• The Demo – Team with Product Owner
• Present Deliverable(s)
• Review progress
• Get feedback
• Retrospective – Just the team
• Review progress
• Review client feedback
• Identify improvements
» what to keep doing
» What to stop doing
» What to start doing
• Preplanning meeting for next sprint

11. Metrics
• Team Velocity
• Burn Down Chart(s)
• Defects/KLOC
• # of functions automated in Unit Test
• Identify functions which most often change
• Code Coverage
• Code Complexity
• PBL snapshot before and after sprint

12. Need Management Help in:
– Tweaking the mindset of the Organization that
adopting Agile is not a choice, but a decision
that needs to be implemented
– Team training on Agile
– Tools needed to implement
– We might/will fail in our first few sprints
– Team Room