SWEN90016 Software Processes and Management
Sprint Planning Tutorial Activity
Week 8: Sprint Planning Activity (About 35 45 minutes)
Copyright By Assignmentchef assignmentchef
Tutorial Pre-Requisites
Given a tutorial has ~20 people, create 2 groups of ~10 people.
Create Scrum Teams and allocate Scrum roles to group:
A Product Owner (1)., A Scrum Master (1), Scrum Dev Team members (~ 5) and Observers (~3).
Hand out ~2 interpersonal roles per Scrum Dev Team members students should play a subtle role.
Dev Team interview Product Owner for detailed Product Backlog requirements
Sprint Goal: Client wants to make an original 3-minute video on any topic the development team knows a lot about, (Default suggestion: A Comparison of Agile & Formal SDLC for Supply Chain Mgmt. applications).
Reference:SWEN90016 Assignment 1, Question 5
Suggested scope for a 3-minute video project Product Backlog
User Story Audience
User Story Description
User Story Priority
As a producer
I want to identify the single most relevant issue for SCM applications today, so that I focus clearly on this issue in the video
As a producer
I want to identify my target audience, so that I engage clearly with my audience
As a producer
I want the message to be strictly 3 minutes, so that the message is within the audiences attention timespan
As the audience
I want to understand the main SCM issue explained in a non-technical way, so that I am motivated to watch and understand
Should Have
As a producer
I want a coherent story, so that my message is clear to the audience
Should Have
As a producer
I want a clear conclusion, so my message is persuasive to the listener
Should Have
As a producer
I want the message to be approximately 400 words so that I can comply with the time limit
Nice to have
As a producer
I want the content components to be editable on a smart phone or a tablet, so I am productive
Nice to have
As the audience
I want enlightening content, so that I learn something from the video
Nice to have
As the audience
I want an inventive presentation with graphics and cutting-edge transitions, so that I am entertained
Nice to have
As the audience
I want to hear new ideas in the conclusion, so that I am challenged
Nice to have
Reference: www.mandel.com/blog/how-to-create-3-minute-video-content
Prepare for the Sprint Planning meeting (5-10 minutes max)
The Product Owner reviews the Product Backlog, adding, updating and deleting Ussr Stories and priorities.
The Scrum Master reviews the private and confidential meeting agenda (provided by the tutor).
The Scrum Dev Team prepare questions to ask the Product Owner about the requirements/User Stories.
Prepare for estimation, refer: https://www.mountaingoatsoftware.com/agile/planning-poker
Agile Estimating: Story Size (mountaingoatsoftware.com)
8 Agile Estimation Techniques (Explained with Examples) (netsolutions.com)
Team 1:Estimation using Planning Poker
Team 2:Estimation using Bucket System (Fibonacci or custom sequence)
The Observers reviews the personality types (provided by tutor) to include in their observations.
Begin the Sprint Planning meeting (35-40 minutes max).
Estimate the Product Backlog User Stories.
First pass: consider how long each User Story will take in comparison to others
assign values of {big, medium, small, no idea epic}.Gain team consensus.
Second pass: add cheap & quick Story Points to each feature User Stories
https://www.mountaingoatsoftware.com/blog/how-can-we-get-the-best-estimates-of-story-size
Defer investing time and quality into estimation/decomposition activities until Just-In-Time.
The done Story Points link to business value items that can be delivered.
Note: the done hours do not link to business value items that can be delivered.
www.scruminc.com/story-points-why-are-they-better-than/
Story Points are considered faster, better, and cheaper than hours and the highest performing teams completely abandon any hourly estimation as they view it as waste that just slows them down.
www.mountaingoatsoftware.com/blog/video-coaching-tips-to-stop-teams-equating-points-to-hours]
Observers evaluate the communication skills and body language of the participants
Observers share notes with meeting participants. Evaluate communication effectiveness and Scrum roles.
Faculty of Engineering and Information Technology
School of Computing and Information SystemsPageof
CS: assignmentchef QQ: 1823890830 Email: [email protected]
Reviews
There are no reviews yet.