What is Quality Management?
As a general rule, quality management is a way to make sure only good products make it to customers. No matter the process or methods, any form of quality management has the same goal. Keep a product in house until it is properly finished, so that customers only get the best. In Scrum, quality management can be broken down to 3 main phases. These phases are planning, control, and assurance.
Quality Planning
The key part of quality planning is communication. It is vital to make sure all team members are on board with whatever quality management system an organization uses. As a Scrum team becomes more familiar with quality management, they follow it more easily. This gives more time for new development and testing, and less time making sure everyone has done their respective jobs.
With quality planning, continuous integration is vital for software development. The idea of continuous integration is that a software is always ready to be released. New changes are committed to the main body of code only when they are confirmed working. This means that an organization doesn’t have to coordinate with everyone to make sure every bit of code works individually. It is expected that everything works, and can produce working software upon request. Features in development are not included in these releases, but will be when they are finished and committed.
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