Mi SCAWIS Next Phase Team Configuration Teri Chaplin

Mi. SCAWIS Next Phase Team Configuration Teri Chaplin PMP, CSM, CSPO, PMI-ACP Dew. Point

Current Stop on the Mi. SACWIS Journey to AGILITY Backlogs & Planning v Single Product Backlog parsed by domain areas v Domain teams manage their Release and Sprint Backlog’s with guidance from Business Req’s and Business UAT Mgr. (meet several times a weeks on “hot” items) v 3 week release: 2 – 1 week build sprints, 1 week hardening sprint o Sprints starts on Thursday’s and end on Wednesday (refinement) o Each team identifies “Release Content” once in the release, Sprint Content weekly. Clear Case is updated and labels printed *Federal Compliance driving some practices

Current Stop on the Mi. SACWIS Journey to AGILITY Team Changes v Domain based teams most collocated (most are >10) • Business Rep (BA • Technical BA • Developers • Independent QA Testers • Business UAT Testers* • Share DBA, Technical Writers for: Training, Online Help v Practices: • Whole Team Release and Sprint Planning • Whole Team Estimating • Whole Team Stand-Ups • Whole Team Retrospectives (much learning fro the first release) (@ 100 team members)

SACWIS Task Board (So. S)

Next Stop on the Mi. SACWIS Journey to AGILITY Team Practices • Limit WIP • Eliminate “Data Fixes” • Using Spikes and doing tough stuff first! • Relative sizing for early prioritization (before selected for a sprint) • Decomposing Change Controls into smaller pieces to test sooner

Next Stop on the Mi. SACWIS Journey to AGILITY Team Practices • Tighten up – daily stand-up/sprint planning • WHOLE TEAM Ownership – generalized specialists rather than just specialists • Using user stories • Grooming Backlog continuously not just during hardening sprint • Eliminate/reduce need for hardening – UAT testing in sprint

Next Stop on the Mi. SACWIS Journey to AGILITY Tool Enablers • Better tool for managing backlogs – getting IBM Rational Team Concert but verdict is still out on it! • Automated code merge • Automated Selective Build process • Continuous Integration server/Static code analysis tools • Concise reporting of code anomalies (Sonar. Qube)

Additional Major Enhancement Project(s) • One year long effort to sunset a vendor app; Totally integrated with main app • Using separate code stream • Team of 8 including SM • Very highly skilled developers, BA’s and Testers ► Full Scrum ceremonies ► User Stories ► Testing in sprint ► Twice wee grooming sessions ► Mid-sprint estimating ► Sprint demos and mid-sprint demos (rep from main project attend) ► Automating test scripts

Major Enhancement Project(s) Challenges • Same technical build issues • Integration with main application ► Code ► Documentation ► End to End Acceptance testing • Common Release to the users – both state and private agencies • Additional 1 -2 scrum teams need to mitigate risk of being late (in process of staffing) • Second and possibly third project must be complete to sunset the old application – may come in scope for the enhancement project

Change of Topics Best book I’ve read in a long time: Being Agile – Mario Moreira http: //cmforagile. blogspot. com

Being Agile or Doing Agile • Recognizing that moving to Agile is a a journey) cultural change (it’s • Sharing and embracing the Agile values and principles (seriously folks!) • Moving to an end-to-end view of delivering value (don’t stop at just the build portion) • Adapting your governance to focus on value (enough with the cost, schedule, and scope!) • Evaluating employee willingness (employees are your brainpower!) • Gaining continuous feedback from customers (adapt toward customer value) • Adapting the reward system to align with the new culture (toward team and value) • Assessing executive support (build engagement along the way)

Introduction to Agile for Leaders Totally changed the approach to training: • What is Agile – really • Crossing the chasm from Innovators/Early Adopters to the Followers/Laggards • Culture change from the top • Showing the video http: //www. youtube. com/watch? v=x. Fnt. Fd. EGgws