A Tale of Two Different Roles Tommy Norman Agile Practice Lead Agenda Scrum Masters amp Project Managers The Agile Project Manager Agile Adoption Implications Making It Work Tommy Norman ID: 635247
Download Presentation The PPT/PDF document "Scrum Master & Agile Project Manager..." 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 Master & Agile Project Manager: A Tale of Two Different Roles
Tommy Norman, Agile Practice LeadSlide2
Agenda
Scrum Masters & Project Managers
The Agile Project Manager
Agile Adoption Implications
Making It WorkSlide3
Tommy Norman
Agile Practice Lead
Scrum Certified
Microsoft MVP
AgileNashville.com
TommyNorman.com
@
tommynorman
Scrum VideosSlide4
Nerds of Rock, May 7thSlide5
Survey
Scrum Master / Agile Organization
Project Mgr. / Waterfall Org.
Agile PM / Mixed Org.
I don’t know what the hell I am!Slide6
Scrum Masters & Project ManagersSlide7
Scrum Master
Responsibilities?
Qualities?Slide8
Scrum Guide“The Scrum Master is responsible for
ensuring
Scrum is understood and enacted. Scrum Masters do this by ensuring that the Scrum Team adheres to Scrum theory, practices, and rules
.”Slide9
Scrum Guide“The Scrum Master is a
servant-leader
for the
Scrum Team.”Slide10
Scrum Guide“The Scrum Master helps those outside the Scrum
Team understand
which of their interactions
with the Scrum Team are helpful and which aren’t. The Scrum Master helps everyone change these interactions
to maximize the value created by the Scrum Team.”Slide11
Product Owner
Development Team
OrganizationSlide12
Development Team
Team Self-Organization
Remove Impediments
Facilitate Events
Scrum CoachSlide13
Product Owner
Backlog Management
Empirical Planning
Maximize Value
Scrum CoachSlide14
Organization
Scrum Rollout
Scrum Coach
Foster Change
Increase EffectivenessSlide15
Collaborative Teams
Maximize
Product
Value
Maximize
AgileAdoption
Maximize
Product
DeliverySlide16
Project Manager
Responsibilities?
Qualities?Slide17
PMBOK“The person assigned by the performing organization to lead the team
that is
responsible
for achieving the project objectives
.”Slide18
Common PM Resources
“Developing
the
project plan”
“Managing the project budget”
“Managing Communication”“Managing the project stakeholders”
“Managing the
project
team”
“Managing the
project
schedule”
“Managing the
project
conflicts”“Managing the project delivery”“Managing the
project risk”
Holy
Crap!!Slide19
Vendors
Functional
Manager
Other
Departments
Business Owner
Development Team
OrganizationSlide20
Maximize
Product
Value
Maximize
Process
Adoption
Maximize
Product
Delivery
Audit
Budget
Maintain
Servers
Business
Case
Allocate
Resources
Deliver
Services
Deliver
Features
Cooperative TeamsSlide21
The Agile PMSlide22
Agile Project Manager
Responsibilities?
Qualities?Slide23
Agile
How is the Agile PM Different?
WaterfallSlide24
Waterfall vs. AgileSlide25
Waterfall vs. Agile
Command & Control
Self-OrganizingSlide26
Waterfall vs. Agile
Jan
Dec
Analyze
Design
Develop
Test
DeploySlide27
Waterfall vs. Agile
Dictatorships gets stuff done
Democracy is messySlide28
Agile
Why Do We Sometimes Have Both?
WaterfallSlide29
New Agile Team
What do
we do?
We’re supposed to self organize, I think.
What does that mean?
This Agile stuff is
kinda
stupid.Slide30
Agile & Non-Agile Teams / One ProductSlide31
Agile Inside Waterfall
Analyze
Design
Construction
DeploySlide32
Scrum-but
Our scope and timeline are fixed.
We constantly rearrange teams.
We create detailed functional specs.
We have analysis, design, & QA sprints
We don’t have cross functional teams.
We don’t self-organize.
Our sprints are 4 months long.
We push tons of new stuff into sprints.Slide33
Agile AdoptionImplicationsSlide34
Little ‘a’ vs. Big ‘A’ Agile
agile
Focus on mechanics
Local optimization
Engineering focused
AgileFocus on valuesOrganizational optimizationCompany wideSlide35
Agile Values & PrinciplesSlide36
Agile Values
Individuals and Interactions
Processes
and Tools
Working
Software
Comprehensive Documentation
Customer Collaboration
Contract Negotiation
Responding to Change
Following
a PlanSlide37
Agile Values
Individuals and Interactions
Processes
and Tools
Working
Software
Comprehensive Documentation
Customer Collaboration
Contract Negotiation
Responding to Change
Following
a PlanSlide38
Transition vs. Dysfunction
We can’t do Agile thing XYZ.
We’ll do ABC in the meantime.
Here is our plan to get to XYZ.
We can’t do Agile thing XYZ.
We’ll do ABC like we always have done.Slide39
Mechanics Without the Values
Search Catalog
As a registered user I want the ability to search the online catalog so that I can find items to purchase.
Business Value: 600 Story Points: 8
Functional
SpecificationSlide40
Story Points & VelocitySlide41
What are some others?
Waterfall Values
Agile PracticesSlide42
Setup for Failure
Poor
Agile Practices
Poor
Waterfall
Values
Help!!!!Slide43
Making It WorkSlide44
Know Which One Your Are
A man’s got to know his limitations.Slide45
Study the Agile Values & Principles
Value
MechanismSlide46
Identify Your Values & Principles
On time and on budget
Customer value
Solving Technology Problems
Quality DeliverablesSlide47
Agile Adoption Backlog
Working Software
Individuals &
Interactions
Working Software is our primary measure of Progress.
Continuous attention to technical excellence
and good design enhances agility.
The best architectures, requirements, and designs
emerge from self-organizing teams.
Potentially shippable code at the end of each Sprint.
Continuous Integration build every check in.
Test Drive Development
Pair Programming
Daily Standup Meetings
Team dedicates 10% of Sprint to grooming.
1
2
3
4
5
6
Mastering
Exemplifying
Not Implemented
Struggling
Striving
FailingSlide48
Plan for Continuous Improvement
Assess Progress Frequently
Form Communities of Practice
Prioritize Areas of Concern
Make Incremental ImprovementsSlide49
Systems Thinking
Lean
Agile
Agile Maturity Models
Scrum
Kanban XP
TDD…Slide50
Little ‘a’ vs. Big ‘A’ Agile
agile
Focus on mechanics
Local optimization
Engineering focused
AgileFocus on valuesOrganizational optimizationCompany wideSlide51
What You Can Start Doing Tomorrow
Focus on Agile Values
Educate Everyone
Create an Agile Adoption Backlog
Inspection & AdaptSlide52
Q & A
tnorman@hollandsquare.com
@tommynorman
www.hollandsquare.com