agile | we are the scrum team; we take ... - project...
TRANSCRIPT
Agile | We Are the Scrum Team; We Take Total Ownership for Deliverables
AGILE WEBINAR
Things to know…
▪ All participants will be on mute
▪ Questions are welcome
▪ Use the question box to ask questions
▪ PM and Agile trainings are valid for 1 PDU
▪ Must be in attendance for full session
▪ PDU certificate sent by the end of the day
▪ Recording and slides sent by tomorrow
© 2017 Project Insight | www.projectinsight.com
Alexa Ortega-Mendoza
Project Insight
Marketing Assistant
www.projectinsight.net
Moderator
© 2017 Project Insight | www.projectinsight.com
Project Insight
Work Better Together™ with Project Insight!
▪ Request FREE DEMO: www.projectinsight.net/trial
▪ Sign up for PI#team for FREE! www.projectinsight.net/team
Our PI#pros are here for you!
▪ +1 (949) 476-6499 x3
©2017 KnolShare
Dr. Dave Cornelius, DM, MBA, PMP, PMI-ACP, CSP, SPC
IT and Business Professional
Founder of 5 Saturdays Education Outreach Program
Author and Speaker
Agile Coach and Trainer
Learn More: www.dave-cornelius.com
LinkedIn: www.linkedin.com/in/daveauck/
Twitter: @DrCorneliusInfo
Presenter
“Believe we can make a difference.”
©2017 KnolShare
GitErDone Team
• Tess Guevara
• Michael Chern
• Dan Vo
Today’s Guest
“We accept the challenge, we make it happen, we learn and grow.”
©2017 KnolShare
The Scrum team is the builders of things (BoT). I would say one of the most important
roles in the Scrum ecosystem. The Scrum team, Product Owner, and Scrum Master are
peers. Each role provides a value that should be respected by everyone in the
organization.
The team has the autonomy to determine how and when to complete work. This new
found freedom can be daunting and at first confusing. We will discover various tools to
help the teams self-organize to deliver the right value at the right time.
Overview
Topics
▪ Agile values and principles
▪ Scrum team role
▪ Pair programming and mobbing
▪ Self-organization
Learning Objectives
▪ Understand the Scrum team role and value
▪ Learn about the Scrum ceremonies
▪ Discover how teams interact
©2017 KnolShare
▪ Individuals and interactions over processes and tools
▪ Working products over comprehensive documentation
▪ Customer collaboration over contract negotiation
▪ Responding to change over following a plan
4 Agile Values
That is, while there is value in the items on
the right, we value the items on the left
more.
Established 2001 -Utah
©2017 KnolShare
1. Customer Satisfaction through early and continuous software delivery
2. Accommodate changing requirements throughout the development process
3. Frequent delivery of working software
4. Collaboration between the business stakeholders and developers throughout the project
5. Support, trust, and motivate the people involved
6. Enable face-to-face interactions
7. Working software is the primary measure of progress
8. Agile processes support a consistent development pace
9. Attention to technical detail and design enhances agility
10. Simplicity
11. Self-organizing teams encourage great architectures, requirements, and designs
12. Regular reflections on how to become more effective
12 Agile Principles
▪ A simple way to “Plan – Do – Inspect – Adapt”
▪ Work is committed by the team
▪ Everyone has a voice and contributes to the outcomes
Scrum Framework
1. Plan & Prioritize
2. Discuss & Commit
3. Execute & Deliver
4. Inspect & Adapt
Scrum Team Role
The Scrum team provides the following value:
1. Build the sprint backlog
2. Estimate relative effort to complete User Stories
3. Evaluate and commit to prioritized User Stories
4. Deliver quality work
5. Take ownership of software/product deliverables
©2017 KnolShare
© 2017 Project Insight | www.projectinsight.com
Team Characteristics
▪ Micro Teams: 3 to 5 people
▪ Self-organizing
▪ Independent
▪ Committed to outcomes
▪ Focus on maximizing value and quality
KnolShare
©2017 KnolShare
Scrum Team Ecosystem
Prioritized Backlog
Scrum of Scrums Dependencies
Incidents
Demo Completed Work
Stakeholders
Customers
Other Teams
Product Owners
Scrum Master
Scrum FrameworkDevOps
IT Ops Teams
Scrum Developer Certification
Scrum Alliance Certified Scrum Developer (CSD)
Group Interaction #1The Scrum team ecosystem consists of Stakeholders, Customers, Product Owner, Scrum Master, Other Teams, and IT Ops team.
A. True
B. False
©2017 KnolShare ©2017 KnolShare
The Scrum Ceremonies
Plan | Build | Learn
©2017 KnolShare
Definition of Ready (DoR)
©2017 KnolShare
▪ The team’s criteria to begin work
▪ Feature Ready
▪ User Story Ready
▪ Sprint Ready
▪ Release Ready
©2017 KnolShare
Acceptance Criteria defined to identify the behaviors required to meet the delivery a
quality feature (Preferably Behavior Driven Development
(BDD) format)
Definition of Done (DoD)
©2017 KnolShare
▪ The team’s criteria for Done
▪ Feature Done
▪ User Story Done
▪ Sprint Done
▪ Release Done
©2017 KnolShare
All planned sprints related to every
Quarter are complete and accepted by product owner.
©2017 KnolShare
▪ Establish a vision of what is to be achieved and when
▪ Guides the team during Sprint Planning
▪ Helps to prioritize User Stories
▪ Guides the team to the right trade-offs
Release Planning
Major Features Sprint 1 Sprint 2 Sprint 3 Sprint 4
Authentication Login RBAC SSO
Order Entry Customer Products Shipping
▪ Product Owner defines highest priority features
▪ Team seek context and clarity to define User Stories
▪ Team define sprint goals
▪ Team create sprint backlog- 2 weeks of work
Sprint Goal Example: Implement basic shopping cart functionality
Sprint Planning
Sprint # Capacity Load Start Date End Date OOO
1 30 SP 35 SP 9/13/17 9/26/17 Bob – 9/15 &
9/22
User Stories Estimates Risks
Purchase Shopping Cart Theme 2 SP We do not know this shopping cart
product
Customize Theme 5 SP None
▪ 15-minute check in by the team
▪ Each team member describes:
▪ What I did yesterday
▪ What I plan for today
▪ What is blocking my success (impediments)
▪ Scrum Master resolves impediments
Daily Scrum / Standup
Impediment: We do not have a database set up yet!
© 2017 Project Insight | www.projectinsight.com
Sprint Execution
▪ Produce the committed Sprint User Stories
Team
PO
SM
Code & Test
Review
finished
user stories
Remove
impediment
sKnolShare
© 2017 Project Insight | www.projectinsight.com
Sprint Review
▪ Review at the end of the 2-week sprint
▪ Customers & Stakeholders come and see
▪ Team demo finished work
▪ Review sprint goals for completion
▪ Receive customer feedback
KnolShare
Retrospectives
▪ Evaluate progress during the sprint
▪ Scrum Master and Scrum team
▪ What went well?
▪ What did not go well?
▪ What can we change?
▪ At least one thing to improve each
sprint©2017 KnolShare
Group Interaction #2The Scrum Ceremonies include:
A. Release planningB. Sprint planning
C. Daily stand-up/Scrum
D. Sprint reviewE. Retrospectives
F. All of the above
©2017 KnolShare
Engineering Practices
Intentional Acts | Collaboration | Leadership
©2017 KnolShare
▪ Encourage growth through learning new skills
▪ Create an environment to get better at Agility
▪ Focus on what works for the team
▪ Create a learning community
Continual Learning
▪ Airplane Pilots are paired for safety & learning
▪ Developers are paired for quality and learning
▪ A navigator and & driver (hands on keyboards)
▪ Switch every 15-minutes
Pair Programming
©2017 KnolShare
▪ Single computer, keyboard and large monitor
▪ All team members work together
▪ Many navigators and one driver at a time
▪ Switch every 15 minutes
▪ Product Owner present –answer questions
Mobbing
▪ Describes software behavior for outside observers
▪ A software development practice to reduce defects
▪ Improves understanding of the customer wants
▪ Leads to superior software designs
Acceptance Test Drive Development (ATDD)
User Story Acceptance Test:
Given my bank account has funds and I made no withdrawals recently
When I attempt to withdraw an amount less than my balance
Then the withdrawal should complete without error
©2017 KnolShare
▪ Optimize the entire process
▪ Less Friction – More cooperation
▪ Faster time from development to production
▪ Continuous Integration (CI)▪ Improved quality and developer feedback
speed
▪ Continuous Deployment (CD)▪ Build once and deploy multiple times
DevOps - CI / CD
Continual Learning
▪ Teams learn daily
▪ Limited experiments are welcome
▪ Learn Fast – Failure is a great teacher
▪ Incremental delivery builds confidence
©2017 KnolShare
© 2017 Project Insight | www.projectinsight.com
Emergent Leadership
▪ Lead without asking permission
▪ Seize the moment when presented
▪ Ability increases with each opportunity
▪ Anyone can assume this role
KnolShare
Group Interaction #3
DevOps reduces friction and encourages more cooperation between developers and IT.
A. True
B. False
©2017 KnolShare
Summary
▪ Scrum teams are the builders of things
▪ Frequent customer feedback gives clarity
▪ Iterative approach solves issues faster
▪ Customers receive tangible value often
Any Questions?
Our Services Include:
▪ Agile Assessment and Strategy
▪ Training
▪ Coaching
▪ Enterprise Agile Release Train (ART) Launch
▪ Business and Technology Process Optimization
▪ Presentation Training and Coaching
KnolShare.org
AgilityLeadershift.com
▪ Title: Transforming Your leadership Character:
The Lean Thinking and Agility Way
▪ Game: Agility LeaderShift
▪ Collaborative Learning
Buy Book & Game on Amazon
▪ Empowering students with agility and innovation
▪ Learn more & Donate: Visit www.5Saturdays.org
5 Saturdays.org – Education Program
• KnolShare with Dr. Dave Podcast
• Industry Experts
• Business & Technology topics
• Visit www.GrokShare.com
• “KnolShare with Dr. Dave” on iTunes
• “KnolShare with Dr. Dave” Google Play
GrokShare.com to Know…
▪ Website: www.KnolShare.org
▪ Email: [email protected]
▪ Twitter: @KnolShare
▪ Blog with me on www.KnolShare.org
Contact KnolShare
©2017 KnolShare
▪ You will automatically receive your PDU certificate via email
▪ For further questions: [email protected]
▪ Earn 1 PDU for each webinar session attended
▪ To register your PDUs go to www.pmi.org and login as a member of PMI
▪ Select Course or Training▪ Provider Name: KnolShare
▪ Activity Name: Webinar - Title
▪ Input start and end dates
▪ URL: www.KnolShare.org
▪ Phone Number: 714-434-3703
▪ Email Address: [email protected]
▪ Hours Completed/PDUs Earned: 1
▪ Under PDUs claimed – Select Category
Earn PDUs
social media
join us
connect
sharefollow like
networknews
information
project management
software
blogs
tech videos
business
leadership
friends
messagetweet
projects
comment
Follow, like, subscribe!
LeadershipProduct Training
Project Insight Community
▪ Sign up for more
▪ They are all FREE
▪ Check them out today!
IT Methodology
and AgilePM Training
See you next time!