back to notes

New Team Assignment Checklist

New Team Assignment Checklist

Review stats via existing reports and tool Meet with PO & SM Review Agile Manifesto Become familiar with Business Needs Discuss Dev Team makeup Review Scrum - terminology including Scrum Team vs Dev Team Review PO duties Review SM duties My duties as a coach Meet with SM, SM 1-1 and with PO on a regular basis SM shadows me - they need to develop coaching ability Discuss Current Team and their Challenges Measure of success is working software Schedule level set meeting with Dev team

Team Agile Manifesto Scrum Basics Emphasis on continuous, incremental delivery …to either… Production or Integrated test for a major release Business Agility Finish what you start Teamwork, Collaboration, Improvement Backlog Refinement…2 sprint minimum (story writing workshop) Ref Mike Cohn Story definition--> As a User, I want, So that PO defines what, not how AC's…Given, When, Then Story size by interacting with TechTeam INVEST Enter into tool Points Some POC/Spike stories ok Story Writing Workshop…also do once per quarter (PI Planning) First sprint planning

Coach SM 1-1 Daily scrum is coordination not a status reporting Continuous progress Id impediments and impact ASAP SM is servant leader…review chart…so is DEV/QA Mgr Dev/QA work together Dev/QA Mgr need to support not direct Dev/QA Mgr need to be SME if applicable No scope creep…if additional story necessary, move another out Review burndown, listen for progress and communication disconnects  

New PO Checklist, SAFe ART environment, when informal training is needed

Agile Manifesto Spreadsheet Values and Principles Some key differences from the waterfall approach 3 major tools used: Scrum, SAFe, Rally

Scrum Overview Scrum Framework Chart Intro 3 roles…Dev Team, PO, SM Scrum events Meeting sequence and they work together Sequence Chart

Scrum Meeting Specifics Daily Scrum / Standups Event Scheduled Backlog Refinement Sprint Review, Encourage to do as you go End of Sprint if needed Sprint Retrospective -Use sample chart

Program Level Meetings Scrum of Scrums Demo's for Mgt at end of each Sprint/Iteration…by PO

Backlog & Story Refinement Story definition & the refinement process Story estimation Acceptance Criteria Technical stories Spike stories Shoulder Taps

Sprint/Iteration Planning Definition of Ready Standard or Existing Team Definition Definition of Done PO accepts all stories to be included Minor adjustments to story definitions and estimation sometimes necessary

PO Responsibilities Use detail list from Scrum Guide

Retrospective Team Self analysis and improvement - PO should attend

Program Review Status Demo by PO's

Team Working Agreement Meeting etiquette…start/end on time, discuss ideas not people, comm is constructive, no review for those who are late, no multi-tasking, etc. Use existing agreement(s) Definition of Ready/Definition of Done Basic behaviors, ie, Update the tool regularly and before daily Scrum

SAFe - How teams are organized and execute in a multiple team environment Intro to Agile Release Train & Lean-Agile process chart How stories are organized: Epics, MBI's, Features Scrum of Scrum meetings

Tool Navigation

Current Team situation

Kanban teams

Setup 1-1 Meetings

Mention industry standard terms Iteration - Sprint Blocker - Impediment MBI - MVP Grooming - Product Backlog Refinement LeanBan - Lean Agile



last updated august 2019