Are you measuring what really counts?

Slides:



Advertisements
Similar presentations
© 2007 BigVisible Solutions, Inc. All Rights Reserved Coaching Solutions Agile Project Start v
Advertisements

Are Parametric Techniques Relevant for Agile Development Projects?
Iteration Planning.
How to Implement Agile in Your Organization
Service Delivery – your ticket to play
Test Automation Success: Choosing the Right People & Process
Delivering Enterprise Projects Using Agile Methods Brent Barton May 23, 2006.
Release Planning – Test Role and Responsibilities Emergence Tech Training / emergencetechtraining.com.
Morning – 9am Getting Started Agile Manifesto Values & Principles Scrum Framework ~~ 10:40 to 11:00 Break ~~ Scrum Roles Backlog Grooming Estimation.
IT Governance Capability Maturity within Government
SE 450 Software Processes & Product Metrics 1 Quality Systems Frameworks.
Agile Methodologies for Project Management By – Komal Mehta.
Trusted IT Group. The challenge: 40 active, concurrent IT projects  Unsatisfactory Project Delivery.
Gaining Support for a Sustainable Agile Transformation Dennis Stevens, VP Enterprise Engagements LeadingAgile November 12, 2013.
Project Human Resource Management
Management Guidelines IT Governance Institute
Test Organization and Management
Certificate IV in Project Management Introduction to Project Management Course Number Qualification Code BSB41507.
Release and Iteration Planning September 13, 2008.
Extreme/Agile Programming Prabhaker Mateti. ACK These slides are collected from many authors along with a few of mine. Many thanks to all these authors.
Agile Metrics It’s Not All That Complicated. © 2011 VersionOne 2 Welcome – About your Trainer, Katia Sullivan VersionOne Product Trainer and Agile Coach.
Cultivating Agile Requirements
Enterprise Agile #LAKC2015.
Intended for Knowledge Sharing only Optimizing Product Decisions with Insights THE PRODUCT MANAGEMENT & INNOVATION EVENT 2016 Jan 2016.
Continual Service Improvement Methods & Techniques.
A Noble Product Owner – Who Can Find? Kim Hardy, Agile Coach CSM & SAFe Program Consultant.
Delivery Method: Online Duration: 180 Days Scrum Developer Certified (SDC™)  Participants will become familiar with the concepts, advantages, and challenges.
The Security Sprint By Ramnath Cidambi. Agile and DevOps DevOps is a “recent” concept though the building blocks have existed for a while – The understanding.
Barnes & Noble Alonda Morgan. Agile UX Agile.
Outline Risk Identifying risks to your project Change Managing change for your project.
1 Chapter 9 Implementing Six Sigma. Top 8 Reasons for Six Sigma Project Failure 8. The training was not practical. 7. The project was too small for DMAIC.
Advanced Software Engineering Dr. Cheng
Example Presentation: Alignment, Launch & Adoption
Rapid Launch Workshop ©CC BY-SA.
Agile Project Management
CLE Introduction to Agile Software Acquisition
CSC 355 – Newer Approaches to System Development Life Cycles & Processes, Spring 2017 March 2017 Dr. Dale Parson.
Project life span.
Agile Training – Agile Overview
Data Architecture World Class Operations - Impact Workshop.
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Identify the Risk of Not Doing BA
Please sit at the appropriate table with your IC/Principal.
Assist Knowledge Development, Ltd.
Scrum CS These outstanding slides were created by Kevin Schenk, BS in Computer Science, Purdue University, 2012.
Software Engineering (CSI 321)
By: By: Agile Scrum Master Online Training.
Navigating an Agile Transformation
Project & Program Governance
Chapter 3: The Project Management Process Groups: A Case Study
TSMO Program Plan Development
Change Agents Why your Transformational IT Initiative Will Fail Without Them Terri Campbell Sr. Director of Change Leadership.
CEN 4010 Intro to Software Engineering Professor Alex Roque
Competency Based Learning and Development
Sample Agile Assessment Report for XYZ Company
Managing Change and Other Keys to Successful Implementation
Establish Process Governance
How to Successfully Implement an Agile Project
Attend|Learn|Grow Taking Your Career to the Next Level
Agile practices for documentation teams
Sprint Planning April 2018.
Introducing ISTQB Agile Foundation Extending the ISTQB Program’s Support Further Presented by Rex Black, CTAL Copyright © 2014 ASTQB 1.
Cobit Framework.
Automating Profitable Growth™
Extreme Programming.
Scaled Agile Frameworks
Agenda Start with Why What Are Best Practice Frameworks, and Why Do We Need Them? Best Practices Defined Lean, Agile, DevOps and ITSM/ITIL 4 The Increasing.
Adapting Agile in Pharmaceutical Industries
Module 9: Capability Maturity Model (CMM) and Self-Assessment
What makes a Good Agile Team
Presentation transcript:

Are you measuring what really counts?

Agenda Why it matters? Maturity frameworks in the market What to measure? Other considerations

Icebreaker Who was the first computer programmer? Alan Turing Charles Babbage Claude Shannon Ada Lovelace

Some definitions and why it matters Maturity – desirable Agile processes are being repeated, across program lifecycles, are being measured and there is a culture of continuous improvement Maturity model – a framework for assessing program or organizational Agile capabilities Quotes I have heard….. “We have made significant investments into Agile practices and we don’t know how well we are adopting the principles” “Is our enterprise benefiting from Agile uniformly?” “Are we Agile enough? Or is our competition better at these techniques?” “How do we avoid an Agile ‘free-for-all’ which results in disparate security protocols or no common architecture”

Sample Maturity Frameworks On-line survey based assessment https://www.comparativeagility.com/ SAFe Metrics https://www.scaledagileframework.com/metrics/#T3 Spotify Health Check Model https://labs.spotify.com/2014/09/16/squad-health-check-model/ ThoughtWorks Agile Maturity Model https://info.thoughtworks.com/rs/thoughtworks2/images/agile_maturity_model.pdf

Comparative Agility On-Line Survey

SAFe Metrics – Self Assessment Tool

Agile maturity levels Capability Maturity Scale building blocks Optimized Level 4 Managed Level 3 Defined Level 2 Repeatable Level 1 Ad-hoc There is evidence that the enterprise has recognized that the issues exist and need to be addressed. There are, however, no standardized processes; instead, there are ad hoc approaches that tend to be applied on an individual or case-by-case basis. The overall approach to management is disorganized Processes have developed to the stage where similar procedures are followed by different people undertaking the same task. There is no formal training or communication of standard procedures, and responsibility is left to the individual. There is a high degree of reliance on the knowledge of individuals and, therefore, errors are likely. Procedures have been standardized and documented, and communicated through training. It is mandated that these processes should be followed; however, it is unlikely that deviations will be detected. The procedures themselves are not sophisticated but are the formalization of existing practices Management monitors and measures compliance with procedures and takes action where processes appear not to be working effectively. Processes are under constant improvement and provide good practice. Automation and tools are used in a limited or fragmented way. Processes have been refined to a level of good practice, based on the results of continuous improvement and maturity modeling with other enterprises. IT is used in an integrated way to automate the workflow, providing tools to improve quality and effectiveness, making the enterprise quick to adapt. Agile Operating Model Process & Policy People and Organizational Alignment Technology and Automation Governance Metrics Training and Communication

Target operating model KPIs & priorities Dimension Agile Topics Leading Practices Process & Policy Sprint Planning Time box the sprints to 4 weeks or less Planning of sprints collaboratively, effectively and efficiently Develop sprint goals and commit to meeting them Write requirements as user stories with clearly defined acceptance criteria Prioritize features ahead of time Apply acceptance criteria and definition of done to story acceptance Have a predictable, normalized velocity for estimation & planning Backlog grooming for every sprint Planning readiness Program backlog is ready and socialized with Product owners Socialize product vision Identify architectural requirements Release planning Program stakeholders, business owners and other resources are in attendance Participation of all team members in person or remote Business context, Product vision, and Top features are effectively communicated Timeboxes are adhered to; event starts and ends on time Risks are discussed, addressed categorized Management addresses key scope and quality challenges and makes adjustments as necessary

Spotify Health Check

Other considerations Audience Sprint teams – self awareness of what’s working and what’s not working Project management or coaches – to see patterns across multiple teams or across different programs and identify systemic problems Executive leadership – to understand if the principles are being applied that they have invested in developing Frequency Monthly can be too often….annually is too seldom…..quarterly may be right for some organizations….. Consider rotating the assessment around different programs throughout the course of a year Consider integrating it into sprint retrospectives Miscellaneous Be careful about the perception of comparing teams or programs Consider letting a program or team decide how they want to be evaluated Be careful that the assessment is viewed as about improvement and not judgement Consider the value of an independent assessor for a fresh perspective

Call to action…. Shifting to Agile without the benefits is a definition in insanity….. Does your organization invest in understanding their Agile maturity and how to continuously improve? If not, maybe you should volunteer to start an Agile maturity initiative at your organization…