Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device.

Shared links
Shared links
How-to articles
How-to articles
Project task report blueprint
Project task report blueprint

Results will update as you type.

OpenLMIS Mission and Vision
Demo
Community
Implementations
Functional Documentation
Product Roadmap
Project Management
Developer Guide

You‘re viewing this with anonymous access, so some content might be blocked.

Team Lead/Scrum Master tasks

Updated Jan 16, 2019

Team Lead/Scrum Master tasks

Jan 16, 2019

1 Team Meetings to schedule
2 Sprint Planning
3 Daily Sprint Standup
4 Sprint Showcase
5 Sprint Retrospective
6 End of Sprint tasks
- 6.1 How to Create and Start a Sprint in Jira

The Sprint Process Overview presentation is located here: https://docs.google.com/presentation/d/1hd0Qt5R98Suzi7NWG5jS6gZVYgqGvwFe8qphCYRZPW8/

Reference docs:http://scrummasterchecklist.org/pdf/ScrumMaster_Checklist_12_unbranded.pdf

Team Meetings to schedule

The following meetings are scheduled by each team lead, and only the development team is required for these meetings.

Daily standup

Backlog grooming (once per sprint) Please include @Wesley Brown in these meetings.

Estimation (story sizing if this will be separate from backlog grooming) https://www.pointingpoker.com/ Article about sizing:https://www.planningpoker.com/blog/sprint-estimation-pointing-scales/

Sprint Q&A: As needed, the team lead, dev members, will meet to ask questions about tickets that are in backlog grooming. During this time they may want to include the product owner (Mary Jo) so that they can receive guidance on the ticket, or guidelines to implement. It's important that the prioritization of each team's sprint has been reviewed by the product owner before the sprint starts, or once the sprint has started.

The Sprint Showcase is scheduled every two weeks at the end of each showcase. @Sam Im (Deactivated) has created the recurring meeting series in ZoomOpenLMIS. All team members should participate, and showcase to external and internal stakeholders. Meeting invite is here:

Topic: OpenLMIS End of Sprint Showcase

Time: May 9, 2018 6:00 AM Pacific Time (US and Canada)

Every 2 weeks on Wed, until Dec 05, 2018, 16 occurrence(s)

Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/360184207

Sprint Grooming

The team lead is responsible for the following tasks, or can coordinate with the team to ensure the tasks are complete:

Add tickets to the Backlog Grooming page for the upcoming sprint

Review all tickets with the dev team to identify any questions in the ticket, agree on ticket acceptance criteria, size (if there is time)

Prioritize and categorize tickets within the backlog grooming page

Help with breaking down stories/tickets:

Sprint Planning

The team lead is responsible for leading the sprint planning meeting, and all members in the development team are required.

Team calendar and sprint schedule is available and updated to review the capacity

If there was a previous sprint, the velocity has been captured to help plan

Development team begins tasking out each of the tickets (this process helps outline what is needed to complete the ticket, although it is expected that more tasks will be found as ticket work begins)

@Sam Im (Deactivated) review each team's sprints and the tickets that were committed (if there are any changes or questions to acceptance criteria, Sam will mention it in the ticket)

Daily Sprint Standup

The team lead is responsible for leading the daily standup, and all members in the development team are required.

View Jira current sprint board, each team member tells the team: What did you do today? (Ticket #), Do I have any blockers for tomorrow? Anything you need from others (code reviews, testing)? Posted in #general slack channel

Move tickets as needed during the standup, dev team should talk about the Ticket # they are working on, and the task they are working on

When a ticket is moved to In QA, they must ask: Who will be assigned to QA? If the ticket is moved to In QA and will be assigned to someone that is not at the standup, it will be posted in the #QA Slack channel and the assignee will be mentioned.

Invite product owner, QA lead as needed (the team lead will decide if anyone outside of the team is needed to join a standup, or they will mention the person in the #dailystandup or #general channel)

Sprint Showcase

The team lead is responsible for coordinating with the development team about what will be showcased. If there are recordings for the showcase, the team lead will play them during the showcase.

Coordinate team's demonstration of each ticket that was worked on during the sprint

Play any recordings as needed

Discuss sprint report (stats) for your team during the showcase

When a team member is showcasing, they should first briefly explain the business value, or the value of the ticket, to provide context of why it was done.

After the first 3 sprints showcases, we will review if we want to make any changes. Here are some ideas:

Sprint Retrospective

The team lead is responsible for leading the retrospective, and all members in the development team are required to attend.

Set up Retrospective board: http://www.ideaboardz.com/, http://www.funretrospectives.com/, https://boardthing.com/main

Set up the retrospective board for each team, and remind them in slack to post their notes on how they feel the sprint went for them. Meet as a team to review the outcomes, and discuss any items that they want to change (action items) for the next sprint.

Tips for a distributed team retro: https://www.atlassian.com/blog/software-teams/run-retrospective-distributed-team-fun
I recommend using http://www.ideaboardz.com/ and selecting their "Retrospective" board. Then adding some examples in each of the columns so that the team has an idea of what to add.
1. Send the link out to everyone before you meet for the retrospective.
2. Allow everyone to add stickies on their own time.
3. When the scheduled meeting takes place, everyone can discuss what they've already written.
4. End goal of the retrospective will be to come out with any improvements.

Record notes from Retrospective and mention @Sam Im (Deactivated) to review here: Retrospectives (naming convention should be: yyyy-mm-dd Team Name Retrospective)

Overall retrospective: Team leads and managers review outcomes of each team's retrospective and help implement changes if needed (this is led by @Sam Im (Deactivated))