coade introduction
TRANSCRIPT
04/12/2023
Scrum?Hans-Peter Samios – Scrum Master
WHY?What problems did we have?
We want this
Our “Health Reviews” ...
There Had To Be A Better Way …
Agile Adoption is Low Risk
© 2007. Intergraph Corporation. All Rights Reserved.
Approach
December 2007– Bob Schatz – Ex VP Development Primavera, Agile Infusion
January 2008– Executive Team Formed – Omegas– First pilots commenced – Squids, Sprinters
February – March 2008– Determine training and engagement model– Additional pilots, remote
April – May 2008– Product Team Meetings – 3D, IM, 2D
June - December 2008– 22 teams in 7 locations involving 150 people
June 2009– 42 teams in 7 locations involving 360 people
February 2010– 63 team means that “Everyone is on Scrum teams”
We’ve only just begun …
ANOTHER CORPORATE INITIATIVE – GREAT …
But what’s in it for me?
© 2007. Intergraph Corporation. All Rights Reserved.
Have Fun!
04/12/2023
Image courtesy of “The Borg” – remember Rule Number 6
February 2008 Survey – Team Feedback
“This is awesome - morale is higher in this environment and the sense of belonging to a team is high”
“Everything from development to documentation is self contained” “Focus is on team accomplishments and not individual performance” “Physical interaction with task items on a daily basis seems good” “Face to face location improves frequency of communication” “Overhearing each other keeps everyone up to speed throughout the day” “Impressed by all the done tasks” “Impressed by the burn down chart – not as many unknowns in the middle of the release” “Really liked the test results – proof in that it was demo’d and didn’t crash”
© 2008 Intergraph Corporation. All Rights Reserved.
Jul-09: Do We Think We Are Producing More?
55% say we are producing more– Only 8% say we are producing less– Net very positive
© 2007. Intergraph Corporation. All Rights Reserved.
Jul-09: Do We Think We Are Producing Higher Quality?
62% say we are producing better quality– Only 11% say we are not– Net very positive
© 2007. Intergraph Corporation. All Rights Reserved.
Jul-09: Do People Like This Change To Scrum?
69% are positive about the change to Scrum
– Only 15% are not– Net very positive
© 2007. Intergraph Corporation. All Rights Reserved.
Jul-09: Would You Continuing Using Scrum If It Were Your Choice?
77% say “YES”
© 2007. Intergraph Corporation. All Rights Reserved.
AGILE / SCRUM 101Introducing Agile / Scrum
© 2007. Intergraph Corporation. All Rights Reserved.
04/12/2023 © 2007. Intergraph Corporation. All Rights Reserved.
Our View of Software Development
Why Agile?
3 things we wish were true– The customer knows what he wants– Our teams knows how to build it– Nothing will change along the way
3 things we have to live with– The customer discovers what he wants– Our teams discover how to build it– Many things will change along the way
“Scrum / Agile is a risk mitigation technique when our assumptions about predictability do not hold”
© 2009. Intergraph Corporation. All Rights Reserved.
04/12/2023 © 2007. Intergraph Corporation. All Rights Reserved.
What is Scrum?
An Agile Project Management framework : – A wrapper for existing engineering practices – Small cross-functional; self-managed teams – Prioritized queue of work– Time-boxed iterations– Multiple, frequent feature-driven planning activities– Early detection and removal of obstacles – User demonstration and collaboration– Inspect and adapt cycle– Sustainable pace for the organization
Scrum is not a methodology – it is a pathway” -- Ken Schwaber (Boulder, Co, Nov. 2005)
04/12/2023 © 2007. Intergraph Corporation. All Rights Reserved.
Scrum on a Page
1234
Product /ReleaseBacklog
SelectedBacklog
.
.
.N
1234
SprintBacklog
DailyScrum
30 DaySprint
SprintPlanning 1
SprintPlanning 2
SprintReview
Product Feedback
SprintRetrospective
Team / ProcessFeedback
ProductOwner
ScrumMaster
Team
Roles:
Stakeholders
04/12/2023 © 2007. Intergraph Corporation. All Rights Reserved.
Roles and ResponsibilitiesProduct
Owner
ScrumMaster
Team
Roles:
Stakeholders
►Defines the features of the product, decides on release date and content►Is responsible for the profitability/value of the product (ROI)►Prioritizes features according to market and/or user value►Can change features and priority every 30 days►Reviews work results with team
►Ensures that the team is fully functional and productive►Enables close cooperation across all roles and functions and removes barriers►Shields the team from external interferences►Ensures that the process is followed. Issues invitations (eg daily scrum)
►Cross-functional, seven plus/minus two members►Selects the iteration goal and specifies work results►Can do everything within boundaries of project guidelines to reach iteration
goal►Organizes itself and its work►Demos work results►Customers: represent the users►Functional managers: represent the organization►Other interested people
ProductOwner
ScrumMaster
Team
Stakeholders
Scrum Team
© 2007. Intergraph Corporation. All Rights Reserved.
Agile Environment – Temporary Start
04/12/2023
© 2007. Intergraph Corporation. All Rights Reserved.
Agile Environment – First Built Plan
04/12/2023
© 2007. Intergraph Corporation. All Rights Reserved.
Agile Environment – After One Year
04/12/2023
04/12/2023 © 2007. Intergraph Corporation. All Rights Reserved.
Task Board / Pull System
Backlog Items Tasks In Process “DONE”
Sprint Goals 1. Provide…. 2. User will… 3. Improve…
© 2007. Intergraph Corporation. All Rights Reserved.
How Does It Get “Done”?
04/12/2023
© 2007. Intergraph Corporation. All Rights Reserved.
Example – Daily Scrum Meeting
04/12/2023
© 2007. Intergraph Corporation. All Rights Reserved.
Example – Daily Scrum Meeting
04/12/2023
© 2007. Intergraph Corporation. All Rights Reserved.
Example – How to Ensure “Done”
04/12/2023
04/12/2023 © 2007. Intergraph Corporation. All Rights Reserved.
Release Burn-down
Shows total remaining points in release plan
04/12/2023 © 2007. Intergraph Corporation. All Rights Reserved.
Release Forecast
Shows whether future plan (light colored chart) based on current data
04/12/2023 © 2007. Intergraph Corporation. All Rights Reserved.
Project Scope Change
Shows the impact of changes in the scope
04/12/2023 © 2007. Intergraph Corporation. All Rights Reserved.
Work Category
Shows, in particular, the impact of “unplanned” items versus our expectation for unplanned work
04/12/2023 © 2007. Intergraph Corporation. All Rights Reserved.
Epics
Shows progress on the main epics in the release.
FURTHER READING"No one has to change. Survival is optional“ W Edwards Demming.
Additional Information
PPM Scrum / Wiki Home Page– http://share.intergraph.com/ppm/spknowledge/tab2/scrum1/Wiki%20Pages/Home.aspx
PPM Scrum Guidelines– http://share.intergraph.com/ppm/spknowledge/tab2/scrum1/Wiki%20Pages/PPM%20Scrum%20Guideli
nes.aspx
What To Do Now That You Have Finished This Training– http://share.intergraph.com/ppm/spknowledge/tab2/scrum1/Wiki%20Pages/Checklist%20-%20Post%20
Team%20Formation.aspx
Useful Scrum Links– http://share.intergraph.com/ppm/spknowledge/tab2/scrum1/Wiki%20Pages/Useful%20SCRUM%20link
s.aspx
The Journey Continues …
…
04/12/2023 EDIT THIS IN "HEADER & FOOTER" UNDER THE "INSERT" MENU
37
04/12/2023
Integrating the Engineering Enterprise…
End