Continuous integration
The Scrum Team uses continuous integration to add new and altered features into the product increment either at the end of a Sprint or when it is appropriate. Risks are minimized because only the most recent features of the product version are being modified. All Scrum Team members are basically safe from making unnecessary changes to the product. There are several benefits associated with continuous integration (CI):
1. Risk Reduction – The practice of integrating code results in a reduction of risk on the Scrum project. When the Scrum Team integrates work on a regular basis, this amounts to faster detection and correction of defects in the code. CI also reduces the disparity between the current condition of the product and the code in the developer’s possession.
2. Reporting and Analysis – When the Scrum Team includes review and substantiation activities into the CI process, value is added for the both the delivery team and managers. Metrics can be extracted regarding project health which can be used for trend detection and historical data purposes. These types of data elements are available to support retrospectives after each Sprint and provide value to reinforce the project’s intended direction. Examples of product metric categories include but are not limited to: unit testing, dependencies and levels of complexity.
Recommended Further Reading
The following materials may assist you in order to g
et 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