Duke Workshop PnT Agile Practice pnt-agile@redhat.com RED HAT CONFIDENTIAL - INTERNAL USE ONLY
AGENDA ● What is Agile ● Why Metrics ? ● Agile Report explanations RED HAT CONFIDENTIAL - INTERNAL USE ONLY
THE HISTORY OF AGILE RED HAT CONFIDENTIAL - INTERNAL USE ONLY
Hoo can tell us what Agile is? RED HAT CONFIDENTIAL - INTERNAL USE ONLY
AGILE SOFTWARE DEVELOPMENT From Wikipedia, the free encyclopedia Agile software development is a set of principles for software development in which requirements and solutions evolve through collaboration between self-organizing , cross-functional teams . It promotes adaptive planning, evolutionary development, early delivery, and continuous improvement, and it encourages rapid and flexible response to change. Agile itself has never defined any specific methods to achieve this , but many have grown up as a result and have been recognized as being 'Agile'. RED HAT CONFIDENTIAL - INTERNAL USE ONLY
AGILE MANIFESTO We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working software 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. RED HAT CONFIDENTIAL - INTERNAL USE ONLY
PRINCIPLES OF THE AGILE MANIFESTO Our highest priority is to satisfy the customer through early and Working software is the primary measure of progress. continuous delivery of valuable software. Welcome changing requirements, even late in development. Agile processes promote sustainable development. The Agile processes harness change for the customer's competitive sponsors, developers, and users should be able to maintain a advantage. constant pace indefinitely. Deliver working software frequently, from a couple of weeks to Continuous attention to technical excellence and good design a couple of months, with a preference to the shorter timescale. enhances agility. Business people and developers must work together daily Simplicity--the art of maximizing the amount of work not throughout the project. done--is essential. Build projects around motivated individuals. Give them the The best architectures, requirements, and designs emerge environment and support they need, and trust them to get the from self-organizing teams. job done. The most efficient and effective method of conveying At regular intervals, the team reflects on how to become more information to and within a development team is face-to-face effective, then tunes and adjusts its behavior accordingly. conversation. http://agilemanifesto.org RED HAT CONFIDENTIAL - INTERNAL USE ONLY
METRICS RED HAT CONFIDENTIAL - INTERNAL USE ONLY
WHY SHOULD WE USE METRICS? CONTINUOUS IMPROVEMENT RED HAT CONFIDENTIAL - INTERNAL USE ONLY
WHY SHOULD WE USE METRICS? FORECAST THE FUTURE RED HAT CONFIDENTIAL - INTERNAL USE ONLY
WHY SHOULD WE USE METRICS? SEE THE REALITY RED HAT CONFIDENTIAL - INTERNAL USE ONLY
WHY SHOULD WE USE METRICS? ANALYZE TRENDS RED HAT CONFIDENTIAL - INTERNAL USE ONLY
WHY SHOULD WE USE METRICS? MAKE BETTER DECISIONS RED HAT CONFIDENTIAL - INTERNAL USE ONLY
NEVER USE METRICS FOR... INDIVIDUAL INSTEAD OF TEAM PERFORMANCE RED HAT CONFIDENTIAL - INTERNAL USE ONLY
NO! Let’s take a look at the Avengers velocity to Metrics are team see if we are better specific RED HAT CONFIDENTIAL - INTERNAL USE ONLY
Agile Reports RED HAT CONFIDENTIAL - INTERNAL USE ONLY
RED HAT CONFIDENTIAL - INTERNAL USE ONLY
INTERPRETING: Velocity Observations: Team always over commits to work ● Team completes around 40 story points ● on average Potential discussions during Retrospectives: Is there something in our process slowing ● us down from getting work done? Do we feel pressured to commit to too much ● work? Should we try enforce a rule where we don’t ● commit to more than 40 points during sprint planning? RED HAT CONFIDENTIAL - INTERNAL USE ONLY
RED HAT CONFIDENTIAL - INTERNAL USE ONLY
INTERPRETING: Sprint Burnup Observations: Team is not consistently getting work ● moved to done Large amount of work moved to done at ● the end of the sprint All of the committed work wasn't finished ● Work was added during the sprint ● Potential discussions during Retrospectives: Are the stories too big? ● Was the scope change for this sprint necessary? ● Did we consider moving something out of the sprint when ● we added a new story a few days into the sprint? RED HAT CONFIDENTIAL - INTERNAL USE ONLY
HIGH-LEVEL REPORT: Release Burnup Purpose: Visually represents progress being made towards a product’s release plan and identifies the amount of work completed over time Predicts the ideal rate of completion after creating a release plan ● Visually represents the amount of work completed towards what has been ● planned for a product’s release Helps identify if the progression of the product is on track and when stories ● are being added or removed to the release plan Why? Calculates completed story points, total amount of work, predicted burn-up ● and plots them as time progresses RED HAT CONFIDENTIAL - INTERNAL USE ONLY
RED HAT CONFIDENTIAL - INTERNAL USE ONLY
RED HAT CONFIDENTIAL - INTERNAL USE ONLY This chart is based off of kanbanery.com
INTERPRETING: Cumulative Flow Observations: Backlog has spiked several times ● Consistently small in progress ● In progress has recently spiked ● several times Potential discussions during Retrospectives: What is changed recently to cause those two big spikes? ● RED HAT CONFIDENTIAL - INTERNAL USE ONLY
RED HAT CONFIDENTIAL - INTERNAL USE ONLY
INTERPRETING: Control Chart Observations: This process is not reliable ● Standard deviation is broad ● Rolling average is increasing, it shows a ● decrease in throughput There are a few outliers ● Potential discussions during Retrospectives: What caused these outliers? ● What can be done to improve our process to narrow standard deviation and ● improve our efficiency? RED HAT CONFIDENTIAL - INTERNAL USE ONLY
AGILE IN OPEN SOURCE RED HAT CONFIDENTIAL - INTERNAL USE ONLY
RED HAT CONFIDENTIAL - INTERNAL USE ONLY
sustainable pace automated testing continuous improvement peer review technical excellence simplicity users are co-developers self organizing communication pull request test driven development continuous delivery trust #AGILE #OPENSOURCE build with stakeholders source code published inspect and adapt autonomy transparency customer satisfaction version control small teams feedbacks short iterations outside in inside out collaboration responding to change release early release often working software respect available to the public RED HAT CONFIDENTIAL - INTERNAL USE ONLY
OPEN ORGANIZATION PRINCIPLES ● Ignite Passion ● Building Engagement ● Chose meritocracy, not democracy ● Letting sparks fly ● Make inclusive decisions ● Catalyzing direction RED HAT CONFIDENTIAL - INTERNAL USE ONLY
AGILE OPEN ORG Business people and developers must work together daily throughout Letting sparks fly the project. Continuous attention to technical excellence and good design enhances Catalyzing direction agility. At regular intervals, the team reflects on how to become more Make inclusive effective, then tunes and adjusts its behavior accordingly. decisions The best architectures, requirements, and designs emerge from Building Engagement self-organizing teams. Build projects around motivated individuals. Give them the Choose meritocracy, not democracy environment and support they need, and trust them to get the job done. Our highest priority is to satisfy the customer through early and Ignite Passion continuous delivery of valuable software. RED HAT CONFIDENTIAL - INTERNAL USE ONLY
AGILE OPEN ORG Business people and developers must work together daily throughout Letting sparks fly the project. Continuous attention to technical excellence and good design enhances Catalyzing direction agility. At regular intervals, the team reflects on how to become more Make inclusive effective, then tunes and adjusts its behavior accordingly. decisions The best architectures, requirements, and designs emerge from Building Engagement self-organizing teams. Build projects around motivated individuals. Give them the Choose meritocracy, not environment and support they need, and trust them to get the job done. democracy Our highest priority is to satisfy the customer through early and Ignite Passion continuous delivery of valuable software. RED HAT CONFIDENTIAL - INTERNAL USE ONLY
THANK YOU RED HAT CONFIDENTIAL - INTERNAL USE ONLY
WHAT ARE THE BENEFITS? RED HAT CONFIDENTIAL - INTERNAL USE ONLY
INCREASED VISIBILITY The agile approach can lead to increased visibility within projects as deliverables are typically built and tested by real users much sooner than with the traditional approach. RED HAT CONFIDENTIAL - INTERNAL USE ONLY
Recommend
More recommend
