All team members from Applications, CSC, and INO should be involved in the iteration planning meeting.
If work planned for the iteration will impact another applications project team or require a resource from another applications project team, that team's project leader should be informed and make sure that the team is represented in the iteration planning meeting.
Preparation
The applications project leader should prepare an agenda in advance of the meeting that highlights the stories that are expected to be addressed and that indicates whether INO resources will be needed for the iteration (if known). The agenda should be sent to the project team and to the ASG and DSG project leaders from INO.
The applications project leader should send an Outlook appointment to the project team to communicate the time and location of the meeting. Iteration Planning Checklist
Consider the following types of tasks/stories as they relate to the work planned for the iteration: CSC related questions
What user documentation is needed for the iteration?
What changes to training curriculum is needed for the iteration?
What testing will be needed for the iteration outside of normal story acceptance testing?
INO related questions
What changes to the infrastructure are planned for the iteration? (Databases, web sites, desktop operating systems, or server software).
Will there be any deploys to test or to production?
If so, when?
Will the team be implementing new tools during the iteration?
What assistance from INO will be needed to implement the tools?
Are changes to current development tools needed?
Is performance or load testing appropriate during the iteration?
If a public website is being built, what kind of penetration testing is needed during the iteration?
Will there be any deploys to WebApps? If so, is all the necessary software installed on Citrix?
Technical Debt Stories
What technical debt needs to be addressed during the iteration? Consider:
Infrastructure code (for data access, unit testing, FitNesse, etc)
Build server/continuous integration setup
References
Renee Kingsland's blog post on iteration planning.
Techniques for running iteration planning and estimating: http://www.renaissancesoftware.net/blog/archives/36. These techniques are being used successfully by the SALSA team. Contact a SALSA team member for more information.
- All team members from Applications, CSC, and INO should be involved in the iteration planning meeting.
- If work planned for the iteration will impact another applications project team or require a resource from another applications project team, that team's project leader should be informed and make sure that the team is represented in the iteration planning meeting.
PreparationThe applications project leader should prepare an agenda in advance of the meeting that highlights the stories that are expected to be addressed and that indicates whether INO resources will be needed for the iteration (if known). The agenda should be sent to the project team and to the ASG and DSG project leaders from INO.
The applications project leader should send an Outlook appointment to the project team to communicate the time and location of the meeting.
Iteration Planning Checklist
Consider the following types of tasks/stories as they relate to the work planned for the iteration:
CSC related questions
- What user documentation is needed for the iteration?
- What changes to training curriculum is needed for the iteration?
- What testing will be needed for the iteration outside of normal story acceptance testing?
INO related questions- Are changes to current development tools needed?
- Is performance or load testing appropriate during the iteration?
- If a public website is being built, what kind of penetration testing is needed during the iteration?
- Will there be any deploys to WebApps? If so, is all the necessary software installed on Citrix?
Technical Debt StoriesWhat technical debt needs to be addressed during the iteration? Consider:
- System Documentation
- Desired code refactoring
- Project setup tasks
- Infrastructure code (for data access, unit testing, FitNesse, etc)
- Build server/continuous integration setup
References