Implementation Phase
In this phase, the activities and tasks outlined in the Effort Estimated Task List are executed in a bid to create a working product of the project. The main inputs to this Agile phase include the Sprint Backlog and the Prioritized Product Backlog. The various project deliverables are created, Daily Standup Meetings conducted as well as refining, which involves the reviewing, fine-tuning and updating of the Product Backlog.
The following are the activities done during the implementation phase:
1. Creation of Deliverables- it is during the implementation phase that the Agile team works on the activities outlined in the Sprint Backlog so as to come up with the Sprint Deliverables. The activities being done have to be tracked in a way. An Impediment Log is also created and any challenges that the Development Team goes through updated in it.
2. Daily Standup- this is just a meeting conducted on a daily basis. The members update one another regarding the progress as well as any challenges that they may be facing.
3. Refining a Prioritized Product Backlog- the Product Backlog has to be updated regularly and kept well. A meeting may be held to discuss the changes made to the Product Backlog, and the discussion is added to a Prioritized Product Backlog.
At the end of this phase, an Updated Prioritized Product Backlog, Sprint Deliverables and Updated Impediment Log are generated.
Recommended Further Reading
The following materials may assist you in order to get the most out of this course:
Course Contents
Section 1: Agile Project Management
Section 2: Using the Agile Manifesto to Deliver Change
Section 3: The 12 Agile Principles
Section 4: The Agile Fundamentals
Section 5: The Declaration of Interdependence
Section 6: Agile Development Frameworks
Section 7: Introduction to Scrum
Section 8: Scrum Projects
Section 9: Scrum Project Roles
Section 10: Meet the Scrum Team
Section 11: Building the Scrum Team
Section 12: Scrum in Projects, Programs & Portfolios
Section 13: How to Manage an Agile Project
Section 14: Leadership Styles
Section 15: The Agile Project Life-cycle
Section 16: Business Justification with Agile
Section 17: Calculating the Benefits With Agile
Section 18: Quality in Agile
Section 19: Acceptance Criteria and the Prioritised Product Backlog
Section 20: Quality Management in Scrum
Section 21: Change in Scrum
Section 22: Integrating Change in Scrum
Section 23: Managing Change in Scrum
Section 24: Risk in Scrum
Section 25: Risk Assessment Techniques
Section 26: Initiating an Agile Project
Section 27: Forming the Scrum Team
Section 28: Epics and Personas
Section 29: Creating the Prioritised Product Backlog
Section 30: Conduct Release Planning
Section 31: The Project Business Case
Section 32: Planning in Scrum
Section 33: Scrum Boards
Section 34: Sprint Planning
Section 35: User Stories
Section 36: User Stories and Tasks
Section 37: The Sprint Backlog
Section 38: Implementation of Scrum
Section 39: The Daily Scrum
Section 40: The Product Backlog
Section 41: Scrum Charts
Section 42: Review and Retrospective
Section 43: Scrum of Scrums
Section 44: Validating a Sprint
Section 45: Retrospective Sprint
Section 46: Releasing the Product
Section 47: Project Retrospective
Section 48: The Communication Plan
Section 49: Formal Business Sign-off
Section 50: Scaling Scrum
Section 51: Stakeholders
Section 52: Programs and Portfolios