Have you been adopting Agile methods across several teams but wondering if there is a consistent way to measure their health and progress? What does it even mean to be a "healthy" Agile team? Take a deeper dive with our dynamic Agile Expert, Sally Elatta, as she walks you through the top 5 metrics you need to be looking at to measure the health and performance of your Agile teams and how you can create a continuous growth process where teams, programs and portfolios are getting better quarter after quarter.

Learning Objectives: 

  • How do you really measure TeamHealth and what metrics should you look for?
  • Why it's important to look at both Qualitative and Quantitative measures and not just focus on 'hard metrics'. 
  • How to create a continuous quarterly growth process that is predictable and measurable.
  • Go through a TeamHealth retrospective simulation!

This will be an engaging and hands on session where attendees get to color a blank TeamHealth radar using crayons and have a tangible output they can share with their teams. 

 

 

 
6 favorite thumb_down thumb_up 0 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

Timed Agenda:

Here's how I've ran this before:

-3 min - Top challenges with measuring TeamHealth - Brainstorming activity

-3 min - Recap these challenges and talk about why companies adopted Agile in the first place

-5 min - Level set what makes up a good/healthy Agile Team and what enterprise stable teams look like

-5 min - Walk through the 5 measures for team health and the sub measures under each one (visually show the Teamhealth radar while participants review the handout version of it)

- 25 min - TeamHealth Retrospective Assessment - activity

- 10 min - Let's build a growth plan! Show me yours, I'll show you mine ;)

- 10 min - Recap then show how Teamhealth can scale up to many teams and how to roll up their 'organizational' issues

- 10 min - Summary and Questions

Learning Outcome

Learning Objectives: 

  • How do you really measure TeamHealth and what metrics should you look for?
  • Why it's important to look at both Qualitative and Quantitative measures and not just focus on 'hard metrics'. 
  • How to create a continuous quarterly growth process that is predictable and measurable.
  • Go through a TeamHealth retrospective simulation!

Target Audience

Agile Leaders, Directors, Managers, ScrumMasters, Coaches and Team Members

schedule Submitted 2 years ago

Comments Subscribe to Comments

comment Comment on this Proposal

  • Liked Nayan Hajratwala
    keyboard_arrow_down

    Nayan Hajratwala - Refactoring Real Legacy Code (guided by Simple Design)

    45 mins
    Talk
    Beginner

    The many trivial testing and refactoring examples available on the web are difficult for developers to apply to real-world code bases. As a result, many "new to agile" developers don't attempt to apply tests or refactorings to legacy code, reserving these techniques for the ever elusive greenfield project.
    To help developers with this dilemma, this session will walk through a real legacy Java code base, and go through the steps required to bring the code under test & begin to perform useful refactorings. All of this will be done under the guidance of the principles of Simple Design.

  • Liked Ken Furlong
    keyboard_arrow_down

    Ken Furlong - How to Organize Multi-Team Programs

    45 mins
    Talk
    Intermediate

    Why does the Agile community encourage cross-functional teams?  So many large organizations have naturally organized into system-specific teams.  This is a very common and logical approach.  At scale, though, it creates serious impediments to organizational agility and getting things done.  We'll discuss the roots of that phenomenon, one of our key interests in cross-functional teams, patterns for enabling such a team structure, some failure modes, and how to prevent them.  Please join us!

  • Liked Simon Storm
    keyboard_arrow_down

    Simon Storm - Agile Portfolio Management - Taking Agile Up the Corporate Ladder

    45 mins
    Talk
    Intermediate

    While many companies are adopting Agile development practices, it is fascinating how most of the management team in these companies are still starting trying to budget and plan in one year increments. Budget and planning starts in the fall and managers are literally guessing what they will need and what they are going to be working on 12 months down the road. It is inevitable that within the first few months of the plan there is going to a major event that is going make the plan completely irrelevant. It could be a new project that came out of nowhere, an issue with a major application that needs all hands to address, or the simple fact that as the team has completed work throughout the year, what was important at the beginning of the year is no longer important. 

    In this talk we will share the experiences of the IT management team of a small financial services firm that took a conference room and Scrum and found a way to improve throughput, increase visibility, and improve coordination across IT, all while delivering projects, responding to auditors and growing the company's product portfolio. 

     

     

     

  • Liked Wyn Van Devanter
    keyboard_arrow_down

    Wyn Van Devanter - Going Green: Getting and keeping your build pipeline green

    45 mins
    Talk
    Intermediate

    A build pipeline is such an important aspect of a software project.  It saves a ton of manual, error-prone depoyment work, as well as results in higher quality software that can be released more frequently.    

    However, I have been on multiple projects where one of the steps in the continuous integration process was failing (red), often for multiple days or even perpetually.  So much of the benefit a build pipeline provides is lost when this is allowed to happen.  Bugs are not caught by automated tests; additional tests break without being fixed because no one notices; the culture of keeping a green pipeline diminishes and faith in everything from the pipeline itself to automated tests reduces.  Developers learn bad habits.   

    Building the pipeline and getting all steps working (keeping it green!) is no small feat in the first place, and keeping it that way can also be a large undertaking. One way I have tried to combat this is to institute some specific process for the Scrum team, pertaining to monitoring and maintaining the build pipeline.  There is also an aspect of convincing the team and management that it is worth spending the time, and dropping everything to maintain a fully functional pipeline.  

    Join me for a common sense, tactile approach to keep a build pipeline green that has worked on small and larger projects with multiple teams.  

  • Liked Brian Sjoberg
    keyboard_arrow_down

    Brian Sjoberg - Moving at the Speed of Molasses ... This Might Have Something to do with It!

    Brian Sjoberg
    Brian Sjoberg
    Agile Coach
    Excella Consulting
    schedule 2 years ago
    Sold Out!
    45 mins
    Demonstration
    Beginner

    Are you struggling with delivering a potentially releasable working product every iteration? Ever wonder what one of biggest reasons we have difficulty getting things done at the individual, team and organizational level are? Do you keep doing something even though you know it reduces your productivity and lowers quality? We are going to run an exercise that highlights one of the major culprits that you have all experienced and continue to experience. The exercise will likely ignite a fire that will help you, your team and your organization to become more productive and improve product quality. We will discuss ways to improve this at the individual, team and organization levels.

    Knowing this will help anyone to understand the consequences of not prioritizing and increase their desire to. This will lead to producing faster, higher quality products that should lead to delighted customers.

  • Liked Mathias Eifert
    keyboard_arrow_down

    Mathias Eifert - Using Lean Thinking to Increase the Value of Agile

    45 mins
    Talk
    Beginner

    “Agile doesn’t have a brain.” This quote from Bill Scott, ‎VP, Business Engineering and Product Development at PayPal, is provocative for sure, but it highlights the perception that in most organizations Agile is primarily applied as a downstream engineering approach. As such, it isn’t inherently concerned with optimizing product design and user experience, the biggest drivers of customer satisfaction. The feedback cycles that form the basis of Scrum provide verification and validation of stakeholder needs only as they are expressed in the backlog’s user stories. Even if a sufficiently empowered and accessible Product Owner is available, agile methods offer little guidance on how to translate organizational goals and customer needs into the backlog’s content and relative priorities in the first place. As a result, the danger persists that agile teams end up very efficiently building products that implement an incomplete and subjective perception of the wants and needs of both the organization and its customers.

    In this session, we will explore how Lean thinking expands the “inspect and adapt” loops of agile development and helps systematically determine which features and design choices really provide the greatest organizational value. After a brief introduction to Lean concepts, we will discuss how Lean approaches product development as a series of hypotheses about customers’ behavior and value perception and builds on Agile’s rapid iterative delivery of working software to test these assumptions. Finally, we will examine ways to derive testable assumptions from organizational goals, such as the Lean UX Hypothesis Statement template and Gojko Adzic’s Impact Mapping.

  • Liked Satish Thatte
    keyboard_arrow_down

    Satish Thatte - Failing to Plan is Planning to Fail: Succeed with Your Agile Planning Playbook

    45 mins
    Talk
    Intermediate

    Although many people know that agile planning is different from big, up-front detailed planning done for traditional or waterfall projects, there are many misconceptions, or vague or partial understandings.  Some people equate agile planning with minimal planning or just-in-time planning or “fluid” or “adaptive” planning.  “Winging” an agile plan is expensive and doesn’t work well.  If you don’t plan or plan poorly, no amount of execution effort would adequately compensate for poor agile planning.   Agile planning is disciplined and rigorous, and the planning process itself is agile. 

    I will present a customizable Agile Planning Framework based on a core set of agile planning principles and practices, common to all organizations.  The framework consists of four well-aligned agile planning levels, each driven by four steps, covering 16 agile planning practices (hence called “4x4 Agile Planning Framework”).   Each agile planning level guides the next lower level of planning, which elaborates the planning done at the higher level but with a shorter time horizon.  Planning retains its agility with periodic adjustments based on the feedback from the plan execution and changes in environment (market conditions, customer feedback, competitive responses, etc.).

    • Product Vision and Strategy planning, with planning horizon of one to three years, and business initiatives or strategic themes serving as the planning unit taking several months to complete. This is the top level of planning.   
    • Release planning, with planning horizon of 2 to 6 months, and features that fit in a release cycle serving as the planning unit.
    • Sprint planning, with planning horizon of 2 to 4 weeks, and stories that fit in a sprint serving as the planning unit
    • Daily planning and Daily Scrums, with planning horizon of one work day, with tasks that fit a single work day as the planning unit. This is the bottom level of planning

    At each planning level the following four steps are required:

    • Select the planning method appropriate to your needs.
    • Obtain required inputs appropriate for the selected planning method, and do necessary preparation ahead of the planning sessions.
    • Apply the selected planning method and develop the necessary planning artifacts to drive the execution at that level, and guide the planning at the next lower level.
    • Re-plan periodically to improve agility.

    I will explain how to use Red Ocean and Blue Ocean Strategy frameworks, and how to harness the Lean Startup Strategy framework at Level 1 Agile Planning (Product Vision and Strategy).

    VersionOne’s 9th Annual State of Agile Survey has indicated that the consistent process and practices is the top tip for success in agile.   No two organizations are alike.  No cookie-cutter approach to agile planning will work in a vast variety of situations. Context matters greatly.   I will explain how Agile Champions can use the 4x4 Agile Planning Framework to develop customized Agile Planning Playbook appropriate to their organization, and how the resulting Playbook facilitates agile planning done by Agile Planners and plan execution by Agile Team Members in a standard and consistent way across an enterprise or at least across a set of projects or teams in a program or a portfolio.

  • 45 mins
    Talk
    Intermediate

    There has been a lot of talk lately about Software Craftsmanship. Most of this talk has been centered around how to take existing, skilled programmers and turn them into Craftsmen. What about those who are just entering the field? In this talk, we will explore a new approach to fulfilling the entire journey from Apprentice to Master, both from a personal and organizational level. We will also look at how to get such a program started, and how to bring the existing team along.

  • Liked Paul Boos
    keyboard_arrow_down

    Paul Boos - Understanding How Collaboration Improves Productivity

    90 mins
    Workshop
    Intermediate

    We've all heard how we need to collaborate better, but what does this really mean?  What results can I expect to see with better collaboration?  

    This workshop will demonstrate how productivity increases with greater collaboration and how to create better a more collaborative environment.  In the session you will not only have an opportunity to experience this relationship with a relatively simple learning game, but we'll look behind the curtain at the science and how some various behavioral models explain why this relationship exists.  We'll then explore some tactics you can use to help teams collaborate better and close with an exploration of what either helps or hinders collaboration and how you can use this information as well as the game with your teams.

    If you have an interest in improving productivity of your team or the teams you serve, then this is the session for you.

  • Liked Andy Bacon
    keyboard_arrow_down

    Andy Bacon - A Leaner PMO in The Federal Government

    45 mins
    Talk
    Beginner

    Can a federal agency’s PMO support Agile teams that are focused on delivering working software frequently? What about all the needed documentation, reviews, and sign-offs from a myriad of groups including systems engineering, privacy, PRA and cyber security? In this session we’ll look at a federal agency’s PMO processes and the concept of minimum viable bureaucracy. We’ll explore the roles and relationship between the PMO, PM, Product Owner, ScrumMaster, and team. We’ll see how projects get initiated and the decision criteria needed to start or defer a project. We’ll walk through a lightweight gate review process and the activities and deliverables of each phase. We’ll also see how gate reviews can co-exists with a continuous delivery pipeline. We’ll share lessons learned and take a look at the challenges ahead. Come to this session to see how a lean PMO is operating in a Federal Agency.

  • Liked Paul Boos
    keyboard_arrow_down

    Paul Boos - Agile Transformation: Using the Krismap and Appreciative Inquiry

    Paul Boos
    Paul Boos
    IT Executive Coach
    Excella
    schedule 2 years ago
    Sold Out!
    45 mins
    Workshop
    Intermediate

    So you want to transform your organization? How should you get started? Am I throwing everything away?

    Understanding how to co-create your organization's aspirational characteristics creates a great start to your Agile journey.  This allows the people to internalize what agile means to them in their context; doing this will allow greater alignment and commitment during the transformation. We'll explore a technique that allows you to do this invented by some coaching colleagues (Michael Sahota and Olaf Lewitz) and that I've utilized in Federal and commercial clients.  

    After performing this short exercise, we'll discuss next steps of selecting strategies using Appreciative Inquiry to help find and build upon your organization's strengths. Along the way, we'll learn a bit about what Appreciative Inquiry is and how it complements other change management approaches one can take. Don't throw out everything, build on your strengths!

  • Liked Bill Schneider
    keyboard_arrow_down

    Bill Schneider - Functional testing is for everyone! Busting myths about unit vs. functional testing

    45 mins
    Talk
    Intermediate

    I will share how I led a team from believing that end-to-end functional (browser) tests were "other" or "someone else's problem", to engaging the whole team in writing these kinds of tests.  By the end of the transition these tests were on almost equal footing as unit tests.

    Along the way, I had to challenge conventional wisdom and dogma about unit tests - that unit tests are easier than functional tests, that unit tests are less brittle, or that unit tests are unconditionally useful.  

    This talk is more about changing people's mindset than about specific tools, although I found that having the right tools made the mindset shift possible.

  • Liked Tom Friend
    keyboard_arrow_down

    Tom Friend - How to explain Agile, Scrum, and Lean in DoD terms to turn Military Decision Maker skeptics into Agile Change Agents.

    45 mins
    Talk
    Intermediate

    Have you ever been part of a team working to win over a DoD organization to Agile and were blocked with skeptics that assert that Agile is “just the next new fad.”  This session will give you the hard facts and skills to win over these skeptics by showing that Scrum, Agile, and Lean are in fact Military war fighting methods that are battle tested, quite literally. This presentation will walk the audience through how the Agile and Military iterative problem solving methods map to one another. The desired objective in doing this is to provide examples and narratives that can be put into your agile tool box for when they are needed.

    Presentation History

    This presentation has been given via several venues over the last year to include: The AFEI Agile in Government Summit, The DoD CIO Software Assurance COP, Southern Fried Agile 2014, and several Agile meet-up groups.

    About me: https://www.linkedin.com/in/thomasfriend

    Thanks for taking the time to consider my proposal.

    Best regards,

    Tom Friend / Agile Consultant / LtCol USAF (Ret)

    CSP, ACP, AHF, FLEX, CSM, PSM, ATP

    Talk: (980) 939-3477

    Write: Tom.Friend@AgileOnTarget.com

  • Paul Boos
    Paul Boos
    IT Executive Coach
    Excella
    schedule 2 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    In the Agile community, we often talk of Servant Leadership, but this notion often doesn't resonate with leaders that have a history for more command and control based approaches. While Servant Leaders exhibit behaviors preferred for leading and supporting teams, the transition can be difficult to grasp. In order to help leaders understand and take action, I have merged the concepts of Servant Leader with a participatory style to become Facilitative Leadership.  This provides a means for better helping people understand more of what they can take action on.

    This talk will help people understand how anyone can become a facilitative leader with a specific focus on people who need help in transitioning their thinking from typical command and control approaches to those that are more facilitative. So if you have been struggling how to serve your teams better, let's reframe how we think of approaching the actions we can take.

  • Liked Brian Sjoberg
    keyboard_arrow_down

    Brian Sjoberg - Pump Life Back into Your Local User Group

    Brian Sjoberg
    Brian Sjoberg
    Agile Coach
    Excella Consulting
    schedule 2 years ago
    Sold Out!
    45 mins
    Talk
    Beginner

    Do you want to help your local community connect, learn and share from each other as they journey towards agility (or any endeavor)? Do you have a local user group that is struggling and needs a resuscitation? This talk will help you pump life back into your local user group. I have taken the local DC Scrum User Group that was starting to fade and brought it back to life with a fast growing membership base that regularly connects, learns and shares with each other multiple times per month. How did I do this? Come find out as I walk you through the various steps I took to reestablish the user group and engage thought leaders and luminaries to come speak at the user group.

    When I took over, last year, our local DC Scrum User Group was just over 500 members and growing at a pace of about 20 members per month. Since then, we have grown to almost 1300 members and growing at 50-60 new members per month. We typically have multiple meetings a month that are a mix of presentations, workshops and webinars.