Conducting an Agile Project
If a project has been reviewed and deemed fit for Agile development, these are the steps to consider when starting an Agile project at GSA:
| Steps | Helpful Links |
|---|---|
| Review the Agile methodology and various frameworks | |
| Conduct Agile IT Investment & Technical Sprint Framework Reviews with Product Owner, Key Stakeholders, and Subject Matter Experts (SMEs) | |
| Prepare for Project Kick-off & Conduct Sprint 0 Planning Session with the (Core) Development Team, Product Owner, and Scrum Master | |
| Set up a “working board” to document user stories, sprint tasks, and the Team members responsible (and assess Team burndown). GSA IT Recommended Tools to document user stories & sprint tasks:
|
|
| Engage end users throughout the effort via follow-up, scheduled discussions, or user acceptance testing | |
| Deliver useable increment at the end of Sprint 0 and review progress to garner feedback from Key Stakeholders Feedback should be reviewed & prioritized by the Product Owner for incorporation into future sprint(s) |
|
| Conduct a Sprint Retrospective with (Core) Development Team and Scrum Master Product Owner, Management, and / or Key Stakeholder attendance are at the discretion of the (Core) Development Team |
|
| Continue consistent sprint planning and activities until project is complete. |