Brent M Dingle PhD For the last few centuries science has been attempting to break matter down into ever smaller bits in the pursuit of understanding And this works to some extent ID: 397112
Download Presentation The PPT/PDF document "Scrum, Agile Design, Task Calendars" is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
Slide1
Scrum, Agile Design, Task Calendars
Brent M. Dingle, Ph.D.
“For
the last few centuries,
… science
has been attempting to
break
matter down into ever smaller bits, in the pursuit of understanding.
And
this works, to some extent...
but
putting things back together in order to understand them is harder,
and
typically comes later in the development of a scientist
or
in the development of science.”
-
Nicholas A.
Christakis, M.D., Ph.D.Slide2
SetupThere are many books and theories and strategies onAgile Design and SCRUMGo read themWhat follows is a simplified overviewWith specific details for this courseEvery business manages things
the same but differentThis course is no exceptionSlide3
Main Points and Goals of TeamworkEveryone must workCommunication must existTeam Progress must be measurableIndividual Progress must be measurable
Everyone is accountableDeadlines must be metProduct must be deliveredSlide4
Traditional vs Scrum ComparisonCommand and ControlPlan what you expectEnforce the plan, sometimes regardless of changing conditions
Estimate everything up frontDelivery at end (of contract)
Traditional
Old project management concepts
were not very adaptive
Planning was assumed to be absolutely
correct at the beginning
and nothing would go wrong
Most companies today have
switched to more
AGILE
and adaptive management
and planning strategies…Slide5
Traditional vs Scrum ComparisonCommand and ControlPlan what you expectEnforce the plan, sometimes regardless of changing conditions
Estimate everything up frontDelivery at end (of contract)
Self-directed teams
Learn as we go
Plan for changes
Embrace change to deliver best product
Use Inspect and Adapt
Continuous delivery of working functionality
Traditional
Scrum
We will be using a SCRUM
based Agile Design ApproachSlide6
SprintsOur application of SCRUMs and Agile DesignDivides time into SprintsTypically each sprint is 2 weeks longSlide7
Summary PointDevelop from Success to SuccessSlide8
Every WeekEvery week (roughly every Thursday night)each team MUST create a buildIt must be runnable and testableIf something prevents the project from runningThen it is NOT done and should NOT be in the buildTest everything before committing
This meansevery Friday you have a deliverable productfeatures should increase each weekSlide9
Every SprintThe presentation minimally shouldDemonstrate what was done/added/improved upon since the previous sprintHighlight what each team member contributed for the current sprintIndicate what will be done in the next sprintBriefly mention anything preventing progress
AlsoEvery team member should speakThe team should look like a team and act like a team throughout the presentation
At the End of Every Sprint
(roughly every 2 weeks)
each team will
Give a presentation and demo of the game (in-class)
Complete evaluations on other team members
Begin planning for next Sprint
Other tasks as needed
check with instructors each sprint
What did you get done?
What
will you do
next?
What is in your way?
Continually think:Slide10
History of Scrum1986: Scrum was first defined as a flexible, holistic
product development strategy where a development team works as a unit to reach a common goalHirotaka Takeuchi and Ikujiro
Nonaka Paper: New New Product Development Game
Scrum is an
iterative
and
incremental
agile
software development
framework
for
managing
software projects and product
or application
development
.
ASIDE: In rugby football, a scrum refers to the manner of restarting the game after a minor infraction
Scrum
enables
the creation of
self-organizing teams by
encouraging
communication
between all team members and disciplines in the project.Slide11
Scrum is an
iterative
and
incremental
agile
software development
framework
for
managing
software projects and product
or application development.
Scrum
enables
the creation of
self-organizing teams by
encouraging
communication
between all team members and disciplines in the project.
What is SCRUM
iterative
incremental
agile
framework
managing
development
enables
self-organizing teams by
communication
1986:
Scrum was first defined as a flexible, holistic product development strategy where a development team works as a unit to reach a common goalHirotaka Takeuchi and Ikujiro Nonaka Paper: New New Product Development Game
ASIDE: In rugby football, a scrum refers to the manner of restarting the game after a minor infractionSlide12
How to SCRUMSCRUMs occur every day (every class)Short status report of each team memberAnswer 3 questions:
What did you get done?
(
since the previous scrum
)
What will you do
next?
(
before the next scrum
)
What is in your way?Slide13
Scrum RolesWho are the ParticipantsScrum Team Members (“The Team”)Scrum MasterProduct OwnerStakeholders / Everyone Else
The Students
The Instructor(s)
Sometimes a StudentSlide14
Scrum Roles: Team and Ground RulesThe key to Scrum is operating as a teamThe longer a team is together,
the more effectively it operatesCreating a set of “ground rules” may help create a more collaborative environment to operate within as a teamSlide15
Scrum Roles: Scrum MasterFacilitates the Scrum FrameworkUpholds Scrum values and practicesOversees the Scrum MeetingsHelps the team be as efficient
as possibleWorks for the TeamFacilitates continuous improvementHelps remove barriers
Enables the team to accomplish ScrumSlide16
Scrum Roles: Product OwnerUltimate responsibility and authorityInterface to the customerConveys the vision to the teamDetermines when a feature is done
implicit link to qualitySingle person, not a committeeIs available to the teamSlide17
Framework Overview
Product
Backlog
Sprint
Backlog
Daily Scrum
Meeting
Potentially
Shippable
(
Incremental)
Product
24 hours
1-5 weeks
Sprint
Planning
Part 1
Sprint
Planning
Part 2
Sprint
Review
Sprint
Retrospective
Start Here
Move to
the RightSlide18
Stories in the Product BacklogFeatures and requirements are tracked as Stories in the Product Backlog
Each story must contain a description, priority, and estimate
For this course
(most)
STORIES = ASSETS
Product Backlog = Master Task ListSlide19
Sprint Planning – Part 1“The What”
What stories (tasks) are going to be worked on this sprint?Slide20
Sprint Planning – Part II“The How”
Do any of the stories need to be broken into tasks?
If you already decomposed
the game this should
be a simple activity
You now need “volunteers” to work on each task needed for the current sprintSlide21
The Daily Scrum
Remember to Record
Task Progress
Status your progress to the team
Keep track of
what you have done
what you are doing
and what you will be doingSlide22
Sprint Release
Check stuff into D2L
and
Create a marker point in the version control systemSlide23
Sprint Review/Demonstration
This is your presentation and demo at the end of each sprintSlide24
Sprint RetrospectiveThe Scrum TeamPossibly other stakeholdersPurposeEvaluate what is and is not working
Plan ways to improveDocument lessons learnedInspect and Adapt opportunity – for the sake of the Team
OutputWays to improve as a teamMay be a change to processCan be captured as a Story/Task and added to the product backlog
For this course
This will usually (but not always) be
the teammate evaluationsSlide25
Questions So Far?Slide26
INTERMISSIONAnd now a word from our sponsors…then on to Task CalendarsSlide27Slide28
Previously…Game Decomposes into Assetsmay be high level placeholders scenes, objects, componentsSlide29
Previously…Game Decomposes into Assetsmay be high level place markers scenes, objects, componentsAsset Identification leads toAsset Master ListSlide30
Previously…Game Decomposes into Assetsmay be high level place markersscenes, objects, componentsAsset Identification leads toAsset Master List
Which leads to
Master Task List
ASIDE:
There may be tasks that are not asset tasks
But
Assets are the starting placeSlide31
Previously…Master Task ListPriority, Estimated Time, Assigned ToSet during Sprint PlanningSlide32
Previously…Master Task ListStatus and Actual TimeUpdated during SCRUMSlide33
SelfishnessAll that is teamworkNow it’s about YOU
YOU must plan YOUR time and YOUR effortSlide34
You Previously…
Asset Sheet = Assignment Sheet
These will keep track of
what you
are expected to produce
Best created during sprint planning
for team agreement and time
estimation
They do NOT say
what
YOU
will do nor when
Need a way to plan and track
YOUR
status and accomplishmentsSlide35
Tasking WorkAt the beginning of each Sprintroughly every other Mondayeach TEAMmust have an updated Master Task
ListMUST identify all tasks planned to be worked for current sprintby who, at what priority, and what the estimated time of each isMUST show all tasks completed in previous sprints
identifying: who, priority, estimated time and actual timeeach individualmust have an updated task calendarSlide36
YOUR Task CalendarYour Task Calendar is derived fromyour team’s Master Task Listlists all the tasks you agreed to do for the current sprintstart here
Consider the following exampleSlide37
Susan has 8 tasks assigned for Sprint 1
Example for SusanSlide38
Susan has 8 tasks assigned for Sprint 1Example for Susan
Reduce to just Susan’s listSlide39
Susan must plan out how to manage those 8 tasks
Example for Susan
Reorder
and add day info stuff
to make a
Task CalendarSlide40
Susan must plan out how to manage those 8 tasksExample for Susan
Fill in the Expected Start Day
mostly based on PrioritySlide41
Susan must plan out how to manage those 8 tasksExample for Susan
This would be a good start
Assumes 2 to 3 hours work per day
Start days are in-sync with priorities
Nothing starts on Day 14
Assuming 14 days in the sprint (i.e. 2 weeks)Slide42
Susan must plan out how to manage those 8 tasksExample for Susan
This allows tracking of progress
Each day record the time spent on the task
If a task is completed record the day it happened
These updates can be done during SCRUM or just beforeSlide43
Susan Task Calendar: Daily SCRUM updates
Asset Name
Priority
Estimated
Time
Expected
Start Day
Done
On
Day
Day
1
Day 2
Day 3
Day 4
Day 5
Day 6
Day 7
Day 8
Day 9
Day 10
Day 11
Day 12
Day 13
Day
14
Generic Button Image
1
1
1
1
1
Play Game Button
1
1
1
1
1
High Score Button
8
1
12
0
Settings Button
8
1
12
0
Credits Button
8
1
13
0
Start Background Image
2
4
5
0
Level 01 Background
1
4
2
0
Level 02 Background
5
4
8
0
NOTE:
Scene, Asset Identifier, Type exist in the table
but are not shown so it can fit on the screen
On day 1
Generic Button and Play Game Button
were worked on and completed
No time was spent on other itemsSlide44
Susan Task Calendar: Daily SCRUM updates
Asset Name
Priority
Estimated
Time
Expected
Start Day
Done
On
Day
Day
1
Day 2
Day 3
Day 4
Day 5
Day 6
Day 7
Day 8
Day 9
Day 10
Day 11
Day 12
Day 13
Day
14
Generic Button Image
1
1
1
1
1
-
Play Game Button
1
1
1
1
1
-
High Score Button
8
1
12
0
0
Settings Button
8
1
12
0
0
Credits Button
8
1
13
0
0
Start Background Image
2
4
5
0
0
Level 01 Background
1
4
2
0
1
Level 02 Background
5
4
8
0
0
NOTE:
Scene, Asset Identifier, Type exist in the table
but are not shown so it can fit on the screen
On day 2
Level 01 Background was worked on
Nothing was completed
No time was spent on other itemsSlide45
Susan Task Calendar: Daily SCRUM updates
Asset Name
Priority
Estimated
Time
Expected
Start Day
Done
On
Day
Day
1
Day 2
Day 3
Day 4
Day 5
Day 6
Day 7
Day 8
Day 9
Day 10
Day 11
Day 12
Day 13
Day
14
Generic Button Image
1
1
1
1
1
-
-
Play Game Button
1
1
1
1
1
-
-
High Score Button
8
1
12
0
0
0
Settings Button
8
1
12
0
0
0
Credits Button
8
1
13
0
0
0
Start Background Image
2
4
5
0
0
0
Level 01 Background
1
4
2
0
1
1
Level 02 Background
5
4
8
0
0
0
NOTE:
Scene, Asset Identifier, Type exist in the table
but are not shown so it can fit on the screen
On day 3
Level 01 Background was worked on
Nothing was completed
No time was spent on other itemsSlide46
Susan Task Calendar: Daily SCRUM updates
Asset Name
Priority
Estimated
Time
Expected
Start Day
Done
On
Day
Day
1
Day 2
Day 3
Day 4
Day 5
Day 6
Day 7
Day 8
Day 9
Day 10
Day 11
Day 12
Day 13
Day
14
Generic Button Image
1
1
1
1
1
-
-
-
Play Game Button
1
1
1
1
1
-
-
-
High Score Button
8
1
12
0
0
0
0
Settings Button
8
1
12
0
0
0
0
Credits Button
8
1
13
0
0
0
0
Start Background Image
2
4
5
0
0
0
0
Level 01 Background
1
4
2
0
1
1
1
Level 02 Background
5
4
8
0
0
0
0
NOTE:
Scene, Asset Identifier, Type exist in the table
but are not shown so it can fit on the screen
On day 4
Level 01 Background was worked on
Nothing was completed
No time was spent on other itemsSlide47
Susan Task Calendar: Daily SCRUM updates
Asset Name
Priority
Estimated
Time
Expected
Start Day
Done
On
Day
Day
1
Day 2
Day 3
Day 4
Day 5
Day 6
Day 7
Day 8
Day 9
Day 10
Day 11
Day 12
Day 13
Day
14
Generic Button Image
1
1
1
1
1
-
-
-
-
Play Game Button
1
1
1
1
1
-
-
-
-
High Score Button
8
1
12
0
0
0
0
0
Settings Button
8
1
12
0
0
0
0
0
Credits Button
8
1
13
0
0
0
0
0
Start Background Image
2
4
5
0
0
0
0
0
Level 01 Background
1
4
2
5
0
1
1
1
2
Level 02 Background
5
4
8
0
0
0
0
0
NOTE:
Scene, Asset Identifier, Type exist in the table
but are not shown so it can fit on the screen
On day 5
Level 01 Background was worked on
and completed
It took 5 total
hrs
to complete
which is 1 more than expected
No time was spent on other items
So Starting Background Image is behind scheduleSlide48
Susan Task Calendar: Daily SCRUM updates
Asset Name
Priority
Estimated
Time
Expected
Start Day
Done
On
Day
Day
1
Day 2
Day 3
Day 4
Day 5
Day 6
Day 7
Day 8
Day 9
Day 10
Day 11
Day 12
Day 13
Day
14
Generic Button Image
1
1
1
1
1
-
-
-
-
-
Play Game Button
1
1
1
1
1
-
-
-
-
-
High Score Button
8
1
12
0
0
0
0
0
0
Settings Button
8
1
12
0
0
0
0
0
0
Credits Button
8
1
13
0
0
0
0
0
0
Start Background Image
2
4
5
0
0
0
0
0
2
Level 01 Background
1
4
2
5
0
1
1
1
2
-
Level 02 Background
5
4
8
0
0
0
0
0
0
Sprint1a Button
Test
-1
2
7
NOTE:
Scene, Asset Identifier, Type exist in the table
but are not shown so it can fit on the screen
On day 6
Start Background Image was worked on
Nothing was completed
No time was spent on other items
A new immediate need task was addedSlide49
Susan Task Calendar: Daily SCRUM updates
Asset Name
Priority
Estimated
Time
Expected
Start Day
Done
On
Day
Day
1
Day 2
Day 3
Day 4
Day 5
Day 6
Day 7
Day 8
Day 9
Day 10
Day 11
Day 12
Day 13
Day
14
Generic Button Image
1
1
1
1
1
-
-
-
-
-
-
Play Game Button
1
1
1
1
1
-
-
-
-
-
-
High Score Button
8
1
12
0
0
0
0
0
0
0
Settings Button
8
1
12
0
0
0
0
0
0
0
Credits Button
8
1
13
0
0
0
0
0
0
0
Start Background Image
2
4
5
0
0
0
0
0
2
0
Level 01 Background
1
4
2
5
0
1
1
1
2
-
-
Level 02 Background
5
4
8
0
0
0
0
0
0
0
Sprint1a Button
Test
-1
2
7
7
-
-
-
-
-
-
2
NOTE:
Scene, Asset Identifier, Type exist in the table
but are not shown so it can fit on the screen
On day 7
Sprint1a Button Test was worked on
and completed
No time was spent on other itemsSlide50
Susan Task Calendar: Daily SCRUM updates
Asset Name
Priority
Estimated
Time
Expected
Start Day
Done
On
Day
Day
1
Day 2
Day 3
Day 4
Day 5
Day 6
Day 7
Day 8
Day 9
Day 10
Day 11
Day 12
Day 13
Day
14
Generic Button Image
1
1
1
1
1
-
-
-
-
-
-
-
Play Game Button
1
1
1
1
1
-
-
-
-
-
-
-
High Score Button
8
1
12
0
0
0
0
0
0
0
0
Settings Button
8
1
12
0
0
0
0
0
0
0
0
Credits Button
8
1
13
0
0
0
0
0
0
0
0
Start Background Image
2
4
5
0
0
0
0
0
2
0
1
Level 01 Background
1
4
2
5
0
1
1
1
2
-
-
-
Level 02 Background
5
4
8
0
0
0
0
0
0
0
0
Sprint1a Button
Test
-1
2
7
7
-
-
-
-
-
-
2
-
NOTE:
Scene, Asset Identifier, Type exist in the table
but are not shown so it can fit on the screen
On day 8
Start Background Image was worked on
Nothing was completed
No time was spent on other items
Level 02 Background start is behind scheduleSlide51
Susan Task Calendar: Daily SCRUM updates
Asset Name
Priority
Estimated
Time
Expected
Start Day
Done
On
Day
Day
1
Day 2
Day 3
Day 4
Day 5
Day 6
Day 7
Day 8
Day 9
Day 10
Day 11
Day 12
Day 13
Day
14
Generic Button Image
1
1
1
1
1
-
-
-
-
-
-
-
-
Play Game Button
1
1
1
1
1
-
-
-
-
-
-
-
-
High Score Button
8
1
12
0
0
0
0
0
0
0
0
0
Settings Button
8
1
12
0
0
0
0
0
0
0
0
0
Credits Button
8
1
13
0
0
0
0
0
0
0
0
0
Start Background Image
2
4
5
9
0
0
0
0
0
2
0
1
1
Level 01 Background
1
4
2
5
0
1
1
1
2
-
-
-
-
Level 02 Background
5
4
8
0
0
0
0
0
0
0
0
1
Sprint1a Button
Test
-1
2
7
7
-
-
-
-
-
-
2
-
-
NOTE:
Scene, Asset Identifier, Type exist in the table
but are not shown so it can fit on the screen
On day 9
Start Background Image was worked on
and completed
Level 02
Background was worked on
No time was spent on other itemsSlide52
Susan Task Calendar: Daily SCRUM updates
Asset Name
Priority
Estimated
Time
Expected
Start Day
Done
On
Day
Day
1
Day 2
Day 3
Day 4
Day 5
Day 6
Day 7
Day 8
Day 9
Day 10
Day 11
Day 12
Day 13
Day
14
Generic Button Image
1
1
1
1
1
-
-
-
-
-
-
-
-
-
Play Game Button
1
1
1
1
1
--
-
-
-
-
-
-
-
High Score Button
8
1
12
0
0
0
0
0
0
0
0
0
0
Settings Button
8
1
12
0
0
0
0
0
0
0
0
0
0
Credits Button
8
1
13
0
0
0
0
0
0
0
0
0
0
Start Background Image
2
4
5
9
0
0
0
0
0
2
0
1
1
-
Level 01 Background
1
4
2
5
0
1
1
1
2
-
-
-
-
-
Level 02 Background
5
4
8
0
0
0
0
0
0
0
0
1
2
Sprint1a Button
Test
-1
2
7
7
-
-
-
-
-
-
2
-
-
-
NOTE:
Scene, Asset Identifier, Type exist in the table
but are not shown so it can fit on the screen
On day 10
Level
02
Background was worked on
Nothing was completed
No time was spent on other itemsSlide53
Susan Task Calendar: Daily SCRUM updates
Asset Name
Priority
Estimated
Time
Expected
Start Day
Done
On
Day
Day
1
Day 2
Day 3
Day 4
Day 5
Day 6
Day 7
Day 8
Day 9
Day 10
Day 11
Day 12
Day 13
Day
14
Generic Button Image
1
1
1
1
1
-
-
-
-
-
-
-
-
-
-
Play Game Button
1
1
1
1
1-
-
-
-
-
-
-
-
-
-
High Score Button
8
1
12
0
0
0
0
0
0
0
0
0
0
0
Settings Button
8
1
12
0
0
0
0
0
0
0
0
0
0
0
Credits Button
8
1
13
0
0
0
0
0
0
0
0
0
0
0
Start Background Image
2
4
5
9
0
0
0
0
0
2
0
1
1
-
-
Level 01 Background
1
4
2
5
0
1
1
1
2
-
-
-
-
-
-
Level 02 Background
5
4
8
0
0
0
0
0
0
0
0
1
2
2
Sprint1a Button
Test
-1
2
7
7
-
-
-
-
-
-
2
-
-
-
-
NOTE:
Scene, Asset Identifier, Type exist in the table
but are not shown so it can fit on the screen
On day 11
Level
02
Background was worked on
5
hrs
now have been
spent,
so time estimate was low(?)
Nothing was completed
No time was spent on other itemsSlide54
Susan Task Calendar: Daily SCRUM updates
Asset Name
Priority
Estimated
Time
Expected
Start Day
Done
On
Day
Day
1
Day 2
Day 3
Day 4
Day 5
Day 6
Day 7
Day 8
Day 9
Day 10
Day 11
Day 12
Day 13
Day
14
Generic Button Image
1
1
1
1
1
-
-
-
-
-
-
-
-
-
-
-
Play Game Button
1
1
1
11-
-
-
-
-
-
-
-
-
-
-
High Score Button
8
1
12
0
0
0
0
0
0
0
0
0
0
0
0
Settings Button
8
1
12
0
0
0
0
0
0
0
0
0
0
0
0
Credits Button
8
1
13
0
0
0
0
0
0
0
0
0
0
0
0
Start Background Image
2
4
5
9
0
0
0
0
0
2
0
1
1
-
-
-
Level 01 Background
1
4
2
5
0
1
1
1
2
-
-
-
-
-
-
-
Level 02 Background
5
4
8
12
0
0
0
0
0
0
0
0
1
2
2
3
Sprint1a Button
Test
-1
2
7
7
-
-
-
-
-
-
2
-
-
-
-
-
NOTE:
Scene, Asset Identifier, Type exist in the table
but are not shown so it can fit on the screen
On day 12
Level
02
Background was worked on
and is completed
but 8
hrs
now have been
spent,
so time estimate was very low(?)
No time was spent on other items
Play Game and High Score buttons start
is now behind scheduleSlide55
Susan Task Calendar: Daily SCRUM updates
Asset Name
Priority
Estimated
Time
Expected
Start Day
Done
On
Day
Day
1
Day 2
Day 3
Day 4
Day 5
Day 6
Day 7
Day 8
Day 9
Day 10
Day 11
Day 12
Day 13
Day
14
Generic Button Image
1
1
1
1
1
-
-
-
-
-
-
-
-
-
-
-
-
Play Game Button
1
1
111
-
-
-
-
-
-
-
-
-
-
-
-
High Score Button
8
1
12
13
0
0
0
0
0
0
0
0
0
0
0
0
1
Settings Button
8
1
12
13
0
0
0
0
0
0
0
0
0
0
0
0
1
Credits Button
8
1
13
13
0
0
0
0
0
0
0
0
0
0
0
0
1
Start Background Image
2
4
5
9
0
0
0
0
0
2
0
1
1
-
-
-
-
Level 01 Background
1
4
2
5
0
1
1
1
2
-
-
-
-
-
-
-
-
Level 02 Background
5
4
8
12
0
0
0
0
0
0
0
0
1
2
2
3
-
Sprint1a Button
Test
-1
2
7
7
-
-
-
-
-
-
2
-
-
-
-
-
-
NOTE:
Scene, Asset Identifier, Type exist in the table
but are not shown so it can fit on the screen
On day 13
Play
Game, High Score, and Setting buttons
were worked on and completed
No time was spent on other itemsSlide56
Susan Task Calendar: Daily SCRUM updates
Asset Name
Priority
Estimated
Time
Expected
Start Day
Done
On
Day
Day
1
Day 2
Day 3
Day 4
Day 5
Day 6
Day 7
Day 8
Day 9
Day 10
Day 11
Day 12
Day 13
Day
14
Generic Button Image
1
1
1
1
1
-
-
-
-
-
-
-
-
-
-
-
-
-
Play Game Button
1
1111
-
-
-
-
-
-
-
-
-
-
-
-
-
High Score Button
8
1
12
13
0
0
0
0
0
0
0
0
0
0
0
0
1
-
Settings Button
8
1
12
13
0
0
0
0
0
0
0
0
0
0
0
0
1
-
Credits Button
8
1
13
13
0
0
0
0
0
0
0
0
0
0
0
0
1
-
Start Background Image
2
4
5
9
0
0
0
0
0
2
0
1
1
-
-
-
-
-
Level 01 Background
1
4
2
5
0
1
1
1
2
-
-
-
-
-
-
-
-
-
Level 02 Background
5
4
8
12
0
0
0
0
0
0
0
0
1
2
2
3
-
-
Sprint1a Button
Test
-1
2
7
7
-
-
-
-
-
-
2
-
-
-
-
-
-
-
NOTE:
Scene, Asset Identifier, Type exist in the table
but are not shown so it can fit on the screen
On day 14
All assigned tasks were already completed
so no tasks needed to be worked
And this is expected
It is a presentation and planning daySlide57
SummaryTeamsMaintain a Master Task ScheduleAll tasks should have a description sheetBest to create/draft them as a team during Sprint PlanningAsset sheets describe what is expected to be produced for asset based tasks
Other tasks should also have a description sheet of some kindBut For “obvious” things the description sheet is often skipped
IndividualsMaintain a Task CalendarUpdate these during SCRUMSlide58
The EndQuestions?Additional material may exist past this slideFor practice and/or references