What is Agile?
Another important task for the Scrum Master is to find a suitable area where the team can sit together, preferably an open-plan office. There should be plenty of wall space to display project documentation, such as the Scrum Board, the burn-down charts, the incident log and any other relevant graphs and tables, such as the Release Plan.
Developing Epics
The team is established and work needs to start on the requirements. Firstly, a broad brush approach is used and “epics” are written. These could be regarded as the chapters of the project book. The Scrum Master has an active role in locating and engaging the appropriate stakeholders and setting up and facilitating user story meetings of different types, from one-on-one meetings to user focus groups.
Create Prioritised Product Backlog
While the Product Owner is responsible for the Product backlog and its contents, the Scrum Master’s knowledge is required in coaching the team in the various prioritization techniques that can be used in Scrum, such as MoSCoW and 100-point analysis. The Scrum Master should always be on the lookout for new techniques and should be picking up pointers from retrospectives from other projects as to which techniques worked best.
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