Adaptive Agile in Action – A Case Study
Expectations from Team:
- Very basic of Agile is to have development at fast pace
- Handle the 6 months Project road-map in smaller 14 days sprints
- Adapt to frequently changing client requirements
- Client and Project Teams work closer than in any other Project Management Model
Challenges we had in project:
- Requirements were changing on daily basis and this could have affected the whole product so we decided to go for adaptive agile method
- End date to deliver the project was fixed
- Customer wanted to be a part of the Project closely
- Delivering lots of content with in fixed deadline was a challenge
How we handled those challenges:
- Daily SCRUM meetings, Project Road map broken down into Mini Projects or Sprints
- Framework per Sprint ensuring each Sprint should have appropriate “User Stories”
- Client, Product Owner and BA worked closely through meetings, walkthroughs, midpoints and progress reports
Everyone to follow the Daily Stand-up rule of answering three questions:
- What I accomplished yesterday?
- What I will be accomplishing today?
- Any Impediments
(Ground Rule: Daily SCRUM to be wrapped up within 15 minutes)
Key Learning
- Agile gives you the ready work product at the end of every sprint…Client can share the findings and recommendations at any time once a sprint is over and move towards the “BIG PICTURE” of completing the Project Road-map
- It gets easier to Ready to accommodate changes if the Project Teams follows the “Adaptive Agile Methodology”
No comments:
Post a Comment