Scrum Framework: Difference between revisions
No edit summary |
|||
| (10 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
[[Category:Agile:Articles]][[Category:Agile]][[Category:Scrum]] | [[Category:Agile:Articles]][[Category:Agile]][[Category:Agile:Scrum]] | ||
The Scrum framework was first presented by Ken Schwaber and Jeff Sutherland at the OOPSLA conference in 1995. The definition for the framework and the underlying source is the | The Scrum framework is currently the most widely known and used agile framework in the world, and was first presented by Ken Schwaber and Jeff Sutherland at the OOPSLA conference in 1995. The definition for the framework and the underlying source is the The Scrum Guide which is periodically updated and is a concise guide of the components and how scrum works. | ||
Scrum is intended to be a framework rather than a process or methodology, in that, there is just enough structure, (for those organisations that like structure,) and enough space for interpretation of how to do the work in an agile way within the structure. | |||
Scrum is quite simple to understand, but also difficult to master especially if the environment has been conditioned with traditional project delivery approaches such as Waterfall for example, and so hands on practice is strongly recommended to explore how Scrum works in different contexts and discover what is needed to succeed. | |||
[[File:Scrum.jpg|500px|Scrum Framework]] | [[File:Scrum.jpg|500px|Scrum Framework]] | ||
==Sprints== | |||
When using the framework, [[Sprints]] are used as protected timeboxes that are fixed in duration and provide a rhythm or heartbeat to the work, and provide opportunities to inspect and adapt the work. | |||
==Scrum Events== | ==Scrum Events== | ||
There are a few simple events in the framework and include: | |||
* [[Sprint Planning & Product Backlog Refinement]] | * [[Sprint Planning & Product Backlog Refinement]] | ||
* [[Daily Scrum]] | * [[Daily Scrum]] | ||
* [[Sprint Review]] | * [[Sprint Review]] | ||
* [[Sprint Retrospective]] | * [[Sprint Retrospective]] | ||
Although classed as an activity and not an event, also check out: | |||
* [[Product Backlog Refinement]] | |||
==Scrum Roles== | ==Scrum Roles== | ||
There are only three roles in the framework: | |||
* [[Scrum Roles]] | * [[Scrum Roles]] | ||
* [[Development Team]] | |||
* [[Product Owner]] | |||
* [[Scrum Master]] | |||
==Scrum Artefacts== | ==Scrum Artefacts== | ||
Scrum artefacts include the Product Backlog, Sprint Backlog and the Increment: | |||
* [[Scrum Artefacts]] | * [[Scrum Artefacts]] | ||
* [[Working With The Product Backlog]] | |||
* [[Product Backlog Items]] | |||
==Scrum Theory== | |||
The underlying theory and influences for the framework: | |||
* [[Empirical vs Predictive Control Processes]] | |||
* [[5 Scrum Values]] | |||
* [[Sprints]] | |||
* [[Definition of Done]] | |||
==Common Scrum Metrics== | |||
* [[Sprint Burndown Chart]] | |||
* [[Velocity Chart]] | |||
* [[Burnup Chart]] | |||
==See Also== | ==See Also== | ||
* [[Scaling Scrum]] | |||
* [[:Category:Scrum|Scrum Category]] | * [[:Category:Scrum|Scrum Category]] | ||
==References== | ==References== | ||
# [http://scrumguides.org The Scrum Guide] | # [http://scrumguides.org The Scrum Guide] | ||
Latest revision as of 22:58, 9 December 2018
The Scrum framework is currently the most widely known and used agile framework in the world, and was first presented by Ken Schwaber and Jeff Sutherland at the OOPSLA conference in 1995. The definition for the framework and the underlying source is the The Scrum Guide which is periodically updated and is a concise guide of the components and how scrum works.
Scrum is intended to be a framework rather than a process or methodology, in that, there is just enough structure, (for those organisations that like structure,) and enough space for interpretation of how to do the work in an agile way within the structure.
Scrum is quite simple to understand, but also difficult to master especially if the environment has been conditioned with traditional project delivery approaches such as Waterfall for example, and so hands on practice is strongly recommended to explore how Scrum works in different contexts and discover what is needed to succeed.
Sprints
When using the framework, Sprints are used as protected timeboxes that are fixed in duration and provide a rhythm or heartbeat to the work, and provide opportunities to inspect and adapt the work.
Scrum Events
There are a few simple events in the framework and include:
Although classed as an activity and not an event, also check out:
Scrum Roles
There are only three roles in the framework:
Scrum Artefacts
Scrum artefacts include the Product Backlog, Sprint Backlog and the Increment:
Scrum Theory
The underlying theory and influences for the framework: