What is Scrum?
For developers in a Scrum framework, the differences between Scrum teams and traditional development teams create very different environments. For one, the self-organizing teams of Scrum mean that developers can gravitate toward work that they better understand. Instead of working on only what they receive instruction for, Scrum developers can pick up assignments that they know more about. Scrum teams are also multi-disciplined, and developers work hand in hand with other roles. Traditional development environments usually have developers only work with other developers. On a Scrum team, all roles involved in the development process are present.
Scrum Theory
There are a few theories that the Scrum framework sticks to. These theories include iterative sprints, transparency, inspection, and adaptation. By applying these theories to the development process, Scrum development can operate more efficiently than traditional waterfall development.
Iterative sprints refer to the process of improving the development environment over time. In Scrum development, a project is divided into many sprints. These sprints are between 2 and 6 weeks long. At the end of each sprint, the Scrum team examines the previous sprint and plans for the following sprint. By breaking up the project into smaller time frames, the team can gradually improve methods and processes.
Using iterative sprints also benefits stakeholders. The goal of Scrum is to produce working pieces of software within each sprint. At the end of the sprint, the Scrum team should have individual components of the product that can work on their own. These components are then delivered to the stakeholders. Since stakeholders can use these working pieces, they can offer feedback on what they do and don’t like the pieces of the product that are already finished. Developers can then use this feedback to improve their work on future components and features through the use of user stories.
Transparency means that all stakeholders can see and understand the process of development. Instead of hiding practices and methods within separate departments, all parties can see and understand all areas from start to finish. By using language and terms that all stakeholders understand, different roles can communicate more effectively. Developers can understand the work and processes of other roles, even without an extensive knowledge of each role.
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