First time doing this, seems to be working well.
I am currently the Product manager/Scrum master, I have a team of 2 developers and a QA tester.
Product is organised in the following way:
- Weekly sprints.
- After a sprint ends. A sprint retrospective happens with the main stakeholder showing what has been achieved from the sprint the week before, stakeholder and I have a brainstorming session on how to improve the product. Backlog is groomed.
- Sprint planning session with the development team then takes place.
- Based on the stakeholder needs following the last sprint, sprint plan for the new sprint comprises of backlog tasks prioritised according to stakeholder needs. The new items are generally high priority tasks. These tasks are estimated based on story points which are given by the development team.
- I then use a burn down chart to track progress of the team during the sprint. I use this as a topic of discussion during daily stand ups and deal with impediments.
If the stakeholder intervenes during a sprint, I step in and tell him that he should wait until the next sprint before asking the team to do tasks outside of the sprint.
Cycle repeats itself.