It also gives other teams the chance to see how your work relates to theirs.
This gives you the opportunity to show the most important work you’ve done, talk about what you’ve learned, explain your plans for the next few weeks and answer questions. If your service is part of a larger organisation or programme you may want to open up your review to the rest of the organisation every few weeks. You’ll need a screen to show your work and enough space for people to join in. You can invite stakeholders like directors or suppliers to this meeting and use it to tell them about the user stories you’ve completed or other work you’ve done. It can also be called a sprint review or a show and tell. The team review is a regular meeting which gives team members the opportunity to demonstrate their work. Read: sprint planning by Ken Schwaber and Jeff Sutherland, the creators of Scrum Team review (show and tell) The length of the meeting will depend on how long your sprint is. You should hold them at the start of each sprint.Īt a sprint planning meeting, the team decides what to work on next and how they’ll do it. Sprint planning meetings are a feature of Scrum. See: standup meetings on Wikipedia Sprint planning meetings Good and bad standups - a video presentation by Adam Maddison, Head of Agile Delivery at Government Digital Service (GDS) It’s best if you do standups in front of your team wall. You should hold them at the same time every day. Standups should last no longer than 15 minutes. The standup is a daily meeting for the team to discuss what they’re working on and whether there are any problems or dependencies they need to resolve (for example, needing help from someone else). You might also hear these tools and techniques called ‘agile ceremonies and artefacts’. get support from senior responsible officers (SROs) and service managers.communicate (within the team and with the rest of your organisation).Using agile tools and techniques can help your digital service team to:
0 kommentar(er)
