Apigee utilizes a form of AGILE implementation called "Extreme Sprints". What differentiates this from a standard AGILE sprint is that it comes after a Project Blueprint phase. As a result, the sprint schedule, user stories, backlog, etc are all determined up front and typically covers the initial 3-4 extreme sprints.
When planning for a sprint, please consider the following
- Ensure the correct attendees are present when doing Sprint user story documentation and planning. Key players include the SCRUM Master, Development Lead, Technical Architects, and Test Teams.
- Review the current list og backlog items and assumptions and constraints
- Ensure the sprint timeline and team capacity is clearly defined
- Call out and risks or issues that may impact the upcoming sprint
- Establish the communication plan if not done so already
- If testing is a part of Sprint, ensure the test teams are involved and will be fully productive during the sprint
- Build in Sprint Review and Retrospective into the Sprint schedule
- Ensure there is a clear definition of the meaning of "done". There should be specific set of criteria which should be defined up front as to when the scope if marked as complete. The reason this is important is because there could be misinterpretation of what "done" means. For example, "done" for a certain sprint could mean the code is developed but not tested. However, "done" for another sprint could mean "developed, tested, and deployed to production". Having a clear definition up front will ensure everyone is aligned when the sprint is complete
Great info. Does Apigee have any templates customers can use as a starting point?
Yes. Templates for Sprint Planning can be found under 'Deliverables' heading on this page: http://community.apigee.com/accelerator-methodology/extreme-sprint
Contributors
3 People are following this .
