Product backlog
Product backlog (document) is created by product owner, It's a prioritised list of stuff which needs to be done from a business standpoint to realise the vision. It may have list items added or taken away.People, users, stakeholders outside the project often want to know what's going on. The product backlog is their only interface to the project. They don't have access to the internal Scrum activity.
Sprint planning
The product owner and Scrum master sit down and look at the product backlog to agree the small collection of priority items which, when complete resemble a visible & quantifiable element of the project. This subset should take no more than 4 weeks (better less). When complete is added to an empty sprint backlog.Separation of backlogs
Once the sprint backlog is full it will not be touched until the sprint is completed. No items which come into the product backlog will update the sprint backlog. If something needs adding the people requesting will only have to wait until the end of the sprint.Sprint begins
Each day a called a stand-up meeting takes place with the scrum master and the people doing the work.In stand-up meetings the workers say:
- Here is what I did yesterday
- Here is what I'm going to do today
- Here is what is in my way
Sprint ends
There should be a potentially shippable product. The sprint backlog may now be cleared and not be revisited.The sprint review takes place, which is a show and tell of the potentially shippable product created during the sprint.
The sprint review informs external users that progress has been made.
Product retrospective
After the sprint is over a product retrospective meeting takes place which includes the workers and and the Scrum master. It contains:- Lessons learned with a purpose
- How they will continue to work
The Product retrospective feeds back to the process of taking the product backlog and adding entries to the sprint backlog.
