Agile We Are the Scrum Team; We Take Total Ownership for Deliverables AGILE WEBINAR

Transcription

1 Agile We Are the Scrum Team; We Take Total Ownership for Deliverables AGILE WEBINAR

2 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

3 Moderator Alexa Ortega-Mendoza Project Insight Marketing Assistant Project Insight

4 Project Insight Work Better Together with Project Insight! Request FREE DEMO: Sign up for PI#team for FREE! Our PI#pros are here for you! +1 (949) x Project Insight

5 Presenter 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: LinkedIn: Believe we can make a difference KnolShare

6 Today s Guest GitErDone Team Tess Guevara Michael Chern Dan Vo We accept the challenge, we make it happen, we learn and grow KnolShare

7 Overview 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 KnolShare

8 Topics Agile values and principles Scrum team role Pair programming and mobbing Self-organization

9 Learning Objectives Understand the Scrum team role and value Learn about the Scrum ceremonies Discover how teams interact 2017 KnolShare

10 4 Agile Values Individuals and interactions over processes and tools Working products over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more. Established Utah

11 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 12 Agile Principles 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 2017 KnolShare

12 Scrum Framework A simple way to Plan Do Inspect Adapt Work is committed by the team Everyone has a voice and contributes to the outcomes 1. Plan & Prioritize 3. Execute & Deliver 2. Discuss & Commit 4. Inspect & Adapt

13 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

14 Team Characteristics Micro Teams: 3 to 5 people Self-organizing Independent Committed to outcomes Focus on maximizing value and quality 2017 KnolShare Project Insight

15 Scrum Team Ecosystem Prioritized Backlog DevOps IT Ops Teams Demo Completed Work Stakeholders Product Owners Incidents Customers Scrum Framework Scrum Master Scrum of Scrums Dependencies Other Teams 2017 KnolShare

16 Scrum Developer Certification Scrum Alliance Certified Scrum Developer (CSD)

17 Group Interaction #1 The 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

18 The Scrum Ceremonies Plan Build Learn 2017 KnolShare

19 Definition of Ready (DoR) 2017 KnolShare 2017 KnolShare The team s criteria to begin work Feature Ready User Story Ready Sprint Ready Release Ready Acceptance Criteria defined to identify the behaviors required to meet the delivery a quality feature (Preferably Behavior Driven Development (BDD) format)

20 Definition of Done (DoD) The team s criteria for Done Feature Done User Story Done Sprint Done Release Done All planned sprints related to every Quarter are complete and accepted by product owner KnolShare 2017 KnolShare

21 Release Planning 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 Major Features Sprint 1 Sprint 2 Sprint 3 Sprint 4 Authentication Login RBAC SSO Order Entry Customer Products Shipping 2017 KnolShare

22 Sprint Planning 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 # 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

23 Daily Scrum / Standup 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 Impediment: We do not have a database set up yet!

24 Sprint Execution Team Code & Test Produce the committed Sprint User Stories Review finished user stories PO SM 2017 KnolShare Project Insight Remove impediment s

25 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 2017 KnolShare Project Insight

26 Retrospectives 2017 KnolShare 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

27 Group Interaction #2 The Scrum Ceremonies include: A. Release planning B. Sprint planning C. Daily stand-up/scrum D. Sprint review E. Retrospectives F. All of the above 2017 KnolShare

28 Engineering Practices Intentional Acts Collaboration Leadership 2017 KnolShare

29 Continual Learning 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

30 Pair Programming 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

31 Single computer, keyboard and large monitor All team members work together Mobbing Many navigators and one driver at a time Switch every 15 minutes Product Owner present answer questions 2017 KnolShare

32 Acceptance Test Drive Development (ATDD) Describes software behavior for outside observers A software development practice to reduce defects Improves understanding of the customer wants Leads to superior software designs 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

33 Optimize the entire process Less Friction More cooperation DevOps - CI / CD Faster time from development to production Continuous Integration (CI) Improved quality and developer feedback speed Continuous Deployment (CD) Build once and deploy multiple times 2017 KnolShare

34 Continual Learning Teams learn daily Limited experiments are welcome Learn Fast Failure is a great teacher Incremental delivery builds confidence 2017 KnolShare

35 Emergent Leadership Lead without asking permission Seize the moment when presented Ability increases with each opportunity Anyone can assume this role 2017 KnolShare Project Insight

36 Group Interaction #3 DevOps reduces friction and encourages more cooperation between developers and IT. A. True B. False 2017 KnolShare

37 Summary Scrum teams are the builders of things Frequent customer feedback gives clarity Iterative approach solves issues faster Customers receive tangible value often

38 Any Questions?

39 KnolShare.org Our Services Include: Agile Assessment and Strategy Training Coaching Enterprise Agile Release Train (ART) Launch Business and Technology Process Optimization Presentation Training and Coaching

40 AgilityLeadershift.com

41 Buy Book & Game on Amazon Title: Transforming Your leadership Character: The Lean Thinking and Agility Way Game: Agility LeaderShift Collaborative Learning

42 5 Saturdays.org Education Program Empowering students with agility and innovation Learn more & Donate: Visit

43 GrokShare.com to Know KnolShare with Dr. Dave Podcast Industry Experts Business & Technology topics Visit KnolShare with Dr. Dave on itunes KnolShare with Dr. Dave Google Play

44 Contact KnolShare Website: Blog with me on

45

46 Earn PDUs You will automatically receive your PDU certificate via For further questions: Earn 1 PDU for each webinar session attended To register your PDUs go to and login as a member of PMI Select Course or Training 2017 KnolShare Provider Name: KnolShare Activity Name: Webinar - Title Input start and end dates URL: Phone Number: Address: CustomerCare@KnolShare.org Hours Completed/PDUs Earned: 1 Under PDUs claimed Select Category

47 join us tweet follow comment share software like information social media friends connect news leadership projects network tech message business videos project management blogs Follow, like, subscribe!

48 Project Insight Community Sign up for more They are all FREE Check them out today! PM Training IT Methodology and Agile Leadership Product Training

49 See you next time!