Agile for the Masses: How to Make Any Team More Effective - John Wetenhall
description
Transcript of Agile for the Masses: How to Make Any Team More Effective - John Wetenhall
JOHN WETENHALL • PRODUCT MARKETER • ATLASSIAN • @JPWETENHALL
Agile for the MassesHow to make any team more effective
Questions?
Ask live: bit.ly/ask-atlassian !
Log in with your email you used to register
Who am I?
• Product Marketing - Confluence + Confluence Questions
• @ Atlassian since May 2013• Scrum Master for Collaboration PMM
team
Track AdaptPlan
Agile for everyone
Agile for everyoneCore concepts
Agile for everyoneCore conceptsAgile applied
Agile is not just about software
Agile is not just about software
Agile is not just about software
5.4
Agile for marketers
Agile for marketers
Agile for marketers
Agile for marketers
Who is your “customer”?
What are you shipping?
Team Customer Product
Team Customer Product
Team Customer Product
Team Customer Product
Team Customer Product
Team Customer Product
Team Customer Product
Team Customer Product
Core concepts
Agile is a cycle
Track AdaptPlan
Sprint
Sprint components
Sprint: 2 weeks
Sprint components
Sprint: 2 weeks
Sprint planning
Sprint components
Sprint: 2 weeks
Sprint planning
Scrum Scrum Scrum Scrum Scrum Scrum Scrum Scrum Scrum Scrum
Sprint components
Sprint: 2 weeks
Sprint planning Retrospective
Scrum Scrum Scrum Scrum Scrum Scrum Scrum Scrum Scrum Scrum
Sprint
Notify Customers of Confluence 5.4
Notify Customers of Confluence 5.4
Write email content
Notify Customers of Confluence 5.4
Take product screenshots
Write email content
Notify Customers of Confluence 5.4
Write announcement blog
Take product screenshots
Write email content
Confluence 5.4 Marketing LaunchNotify Customers of
Confluence 5.4
Write announcement blog
Take product screenshots
Write email content
What do tasks look like?
What do tasks look like?
What do tasks look like?
IssueIssue Issue
IssueIssue Issue
Sub-task
Sub-task
Sub-task
Sub-task
Sub-task
Sub-task
Sub-taskSub-task
Sub-task
EpicIssueIssue Issue
Sub-task
Sub-task
Sub-task
Sub-task
Sub-task
Sub-task
Sub-taskSub-task
Sub-task
Marketing Epics
Marketing Epics
5.4
Marketing Epics
5.4
Marketing Epics
5.4
Marketing Epics
5.4
Marketing Epics
5.4
Marketing Epics
5.4
Sprint
Epic
Sprint Sprint Sprint
Key roles: Scrum Master
• “Servant leader”• Facilitates:• Scrum, planning, retrospective meetings• Tracks roadmap• Coordinates with other teams
Key Roles: Product Owner
• Source of truth for goals/objectives• Prioritizes the backlog• On our team: Ryan Anderson
Key roles: Team
• Everyone else• Owns estimates and work• Self-organizing
Agile applied
Track AdaptPlan
Sprint
Track AdaptPlan
Sprint
Sprint planning goals
Sprint planning goals
Sprint planning goals
Start before you meet
Start before you meet
Issue
Sub-task
Sub-task
Start before you meet
Issue
Sub-task
Sub-task
Step 1: Clarify Priorities
Prioritize epics
Step 2: Translate priorities into work
Planning poker
1/2 1 2 3
5 8 13 20
Step 3: Estimate work
Notify Customers of Confluence 5.4
Write announcement blog
Take product screenshots
Write email content
Step 3: Estimate work
Notify Customers of Confluence 5.4
Write announcement blog
Take product screenshots
Write email content2
21
3
2
Step 4: Sum it up
Track AdaptPlan
Sprint
Track AdaptPlan
Sprint
• 10 minute limit• What did you accomplish
yesterday?• What will you accomplish today?• Any blockers?
Daily Standup
Track and complete work
Track and complete work
Track and complete work
Track and complete work
Track AdaptPlan
Sprint
Track AdaptPlan
Sprint
Complete sprints in JIRA
Run Retrospectives in Confluence
Run Retrospectives in Confluence
Run Retrospectives in Confluence
Run Retrospectives in Confluence
Run Retrospectives in Confluence
Repeat the cycle!
Sprint: 2 weeks
Sprint planning Retrospective
Scrum Scrum Scrum Scrum Scrum Scrum Scrum Scrum Scrum Scrum
Any team can be Agile
Keys to becoming Agile
Who is my customer? What product am I delivering?
Principles > process
Focus on delivering value
Thank you!
JOHN WETENHALL • PRODUCT MARKETING • ATLASSIAN • @JPWETENHALL