How to REALLY use the Agile values and principles!!

schedule Sep 23rd 03:15 - 04:00 PM place Room 4 people 8 Interested
Your organization is doing Agile, which great, but what does that really mean? Perhaps they are implementing Scrum, or Kanban, or one of the other Agile methods, but are they really being Agile? Does it feel like you are you are doing Scrum, but you’re team isn’t really Agile? There's difference between doing Agile and being Agile and this session explores that concept.

In this session, we’ll understand what Agile really means and how that relates to the way we implement our Agile methods within our organizations. We'll identify how we effectively use the Manifesto value points so that we can maximize the value of our products while still ensuring that we have quality and governance built into our process. This session will also explore the use of Agile principles to guide our strategic and day to day decisions.

This sessions is great not only for beginners, but for anyone who wants to get past simply implementing Scrum or Kanban by the book, but really understand how to use Agile values and principles to build better products and organizations.
 
 

Outline/Structure of the Workshop/Game

  1. We start off with the Agile Manifesto. In triads, we have a discussion around how these Manifesto value points have helped your organization and also how your organization may be struggling with some of the value points.
  2. We debrief on these discussion and discuss what the left side and the right side of the Agile Manifesto really means and how to effectively deal with both in our organizations
  3. We then do an exercise where we look at a series of scenarios where a decision has been made to do something. For each scenario, the table groups have to identify if the decision made aligns or conflicts with Agile principles. If the decision align with Agile principles, which principle does it most align with. If it conflicts, which one does it most conflict with.
  4. We then debrief the scenarios to determine how Agile principles help shape the decisions in each scenario
  5. We conclude by discussing the differences between Scrum practices, Kanban concepts, and the Agile mindset and how all that relates

Learning Outcome

A deep dive into Agile manifesto value points and principles

A understanding of how to use the value points and principles to help make decisions in terms of your organization's practices

A understanding of how Scrum and Kanban represent practices but how we need to leverage Agile values and principles to put meaning into these practices

Target Audience

ScrumMasters, Dev Team Members, Product Owners, Everyone

Prerequisites for Attendees

No prerequisites needed.

schedule Submitted 3 months ago

Public Feedback

comment Suggest improvements to the Speaker

  • 45 Mins
    Talk
    Beginner

    Have you tidied up your personal life with Marie Kondo and are now wondering how to achieve the same effect in your work life? Do you have the feeling that the most valuable product backlog items (PBIs) are getting lost under a mountain of old stories, bugs, and tasks? Maybe you know a change is needed, but feel completely overwhelmed about where to start? If so, join us to learn how to make your product better through the life changing magic of tidying up your backlog.

    We’ll start by exploring the costs of a large, cluttered product backlog and share a short quiz you can use to gauge the current state of your own backlog. Next, we’ll cover how we’ve adapted the KonMari method and introduce five easy steps you can take to get started in your tidying process. We'll share real-life examples along the way, calling out potential pitfalls to avoid (don’t become a storage expert!), and illustrating how story mapping may be the magical backlog equivalent to Kondo’s “vertical folding” technique. By the end of the session, you’ll know the specific next steps to take so that you too can realize the many benefits of a tidied-up product backlog: improved visibility, increased self-organization, and easier decision-making.

  • Liked Mark Grove
    keyboard_arrow_down

    Mark Grove / Julie Wyman - What’s REALLY Going On? An Observational Skills Workshop

    45 Mins
    Workshop/Game
    Beginner

    Imagine you are asked to sit in on a team’s sprint review and retrospective. The team has been having difficulty forming and the Scrum Master has asked you to observe the team dynamics during these two sessions. Are you simply going to watch what’s going on or is there more you can do? Perhaps you are seeing interactions and team dynamics at play without truly realizing what you are observing. And when you do observe, are you injecting your own biases into those observations? Observation is a powerful tool, but one which we may not take advantage of to its true potential. After all, what exactly should we be observing, anyway?

    By learning how to expand our observational skills in a non-biased and non-judgmental manner, we can gain a deeper understanding of team dynamics and interactions allowing us to offer more meaningful and impactful support, coaching, and empathy. Because there are many observational aspects that pass us by, the best way to become more observant is through deliberate practice. So, let’s practice together with a group exercise in a fun and safe setting!

    In this highly interactive workshop, we’ll start by sharing tools and tips to make you a better observer. Then we’ll ask for a small group of volunteers (“builders”) to be observed performing a brief task. The remaining attendees will practice applying the observation techniques, and, after the builders finish, will share their observations in small groups. We’ll conclude with a full-group debrief and discussion of the key takeaways and opportunities to improve our effectiveness and observations.

    If you’re looking for new ways to connect with your team, to enhance your agilist toolkit, or simply participate in an informative and interactive workshop, this session is for you!

  • Liked Mathias Eifert
    keyboard_arrow_down

    Mathias Eifert - Complexity is the Enemy! How Agile Practices Allow Us to Operate in a VUCA World

    45 Mins
    Talk
    Intermediate

    One of the key advantages of Agile over plan-driven approaches is that an Agile mindset acknowledges our ever-diminishing ability to usefully predict the future and focuses our efforts on managing change instead of trying to suppress it. This “new reality” has become pervasive enough to drive its own buzz word – VUCA, which stands for Volatility, Uncertainty, Complexity, Ambiguity. But beyond the hype lies a truth that Agile leaders need to understand and embrace – that certain problems really do respond differently to our attempts to manage and solve them. Why does this matter? Because problem contexts that defy straightforward cause-and-effect expectations significantly impact productivity while simultaneously presenting much higher risks to success. Even worse, applying leadership approaches that aren’t matched to the problem context dramatically increases the danger of catastrophic failure.

    In this session, we’ll examine how the Cynefin framework helps us make sense of what kinds of problems we’re dealing with and how we should approach them. We will then look at ten ways in which Agile frameworks, approaches and technical practices help us manage or even reduce complexity and one where they fall short. You will walk away with a deeper understanding of how - and why - the things we do as agilists increase stability and reduce risks for our teams.

  • Liked Mark Koenig
    keyboard_arrow_down

    Mark Koenig - Continuous Modernization

    Mark Koenig
    Mark Koenig
    Scrum Master
    Excella
    schedule 3 months ago
    Sold Out!
    45 Mins
    Talk
    Intermediate

    Rather than engaging in an intense modernization effort followed by years of minimal maintenance, a better alternative often is modernizing a system continuously, balancing operations, maintenance, and renovation. Ideally you can improve, update, and upgrade the software system one piece at a time while it continues to operate, avoiding feature freezes and scary cut-overs.

    There are always trade-offs to be made, but some approaches better fit IT systems with long-lived missions. At a certain point, a whole-sale rewrite is the best option for replacing stale, decaying software before it leads to major headaches and eventual catastrophe. Big rewrites have big risks and big failures, however. Because of the stability and enduring mandates of some software systems, long-term investments in IT systems pay off and give room for smart maintenance strategies.

  • Liked Adam Parker
    keyboard_arrow_down

    Adam Parker - NoEstimates at Scale in the Federal Government

    Adam Parker
    Adam Parker
    Agile Coach
    Excella
    schedule 3 months ago
    Sold Out!
    45 Mins
    Experience Report
    Advanced

    Come learn how our 3 teams, operating in a LeSS-style scaled model, experimented with a NoEstimates approach to development work and then adopted that as our way of working for a year in the Federal government. Included in our story is a switch to Kanban, returning to Scrum, and eventually returning to pointing work. It has been a remarkable journey that I'm excited to share!

  • Liked Donald Patti
    keyboard_arrow_down

    Donald Patti / David Bulkin - Scaling: Getting Big is NOT the Answer!

    45 Mins
    Talk
    Beginner

    Ask someone why they want to scale and their response is often, "So we can continue practicing agile as we grow bigger." While the pursuit of agility is a noble one, most often the pursuit of "bigness" is not. But what is?

    In this talk, David Bulkin and Donald Patti will introduce attendees to three of the most popular scaling frameworks -- Scrum@Scale, LeSS and SAFe -- comparing the qualities of each. In addition, they'll explain what organizations looking to scale SHOULD pursue as they scale.

  • Liked Nicole Spence-Goon
    keyboard_arrow_down

    Nicole Spence-Goon - Peaks or Valleys? The power of Scaling Agility in the alphabet soup of Government agencies

    Nicole Spence-Goon
    Nicole Spence-Goon
    Agile Coach
    Excella
    schedule 3 months ago
    Sold Out!
    45 Mins
    Experience Report
    Beginner

    Do you feel like Agile Scaling has become a goal rather than the means to an end for your organization? To determine where you stand on the Scaling spectrum, ask yourself a few soul-searching questions: Why do we need to scale? Is this the right time for us to scale? If you’ve checked these boxes, you may wonder “where do I go from here?”

    This talk will focus on 3 areas that emerged as common themes throughout my experience working on government Agile Scaling projects and ultimately influenced the trajectory of each agency's scaling journey:

    • Communicate vision consistently
    • Focus on your people genuinely
    • Create your own path intentionally

    I've seen successes and some struggles with Agile Scaling efforts in government agencies. Regardless of the agency acronym or the frameworks used, these key elements shaped their scaling outcomes.

  • Liked David Fogel
    keyboard_arrow_down

    David Fogel / David Bujard - Nine levels of Agile Hell... and how to get out!

    45 Mins
    Talk
    Beginner

    Government Agile transformations can feel like overwhelming efforts – but do not abandon hope! This interactive, audience-driven presentation reviews how government and large organizations ESCAPE common Agile adoption challenges.
    You - the audience - will prioritize your pain points; we’ll focus on the five Agile hells most highly prioritized. We will discuss real examples of “escaping” out of each Agile hell, with pro tips and success patterns you can apply.
    The Agile hells we've escaped include:

    • No Transformation hell - A federal program or department wants to change but can’t start or can’t finish
    • Too Fast hell - Newly Agile federal programs sometimes respond TOO rapidly, too often changing priorities.
    • Technical hell - Programs can become bogged down in technical debt and manual processes.
    • No Trust hell - Government delivery can be slowed by lack of trust between contractors and feds, between business and IT, or between compliance and delivery groups.
    • Product Owners hell - Government Product Owners can be unavailable, think they are managers, aren’t empowered to provide vision, or struggle with prioritization
    • Too Big hell- A frequent pattern in federal Agile! Large batches produce slow progress, low visibility and high complexity, seen in big programs, big deployments, and big contracts.
    • Collaboration hell - Government teams can struggle with collaboration within the same organization across roles and across the fed-contractor divide.
    • Stove-piped hell - Government organizations can struggle to collaborate across contractual or organizational boundaries within the same enterprise
    • Leadership hell - An organization can only be as agile as its leadership. In the government, how can you work with leaders who aren't ready to be agile?

    For each Agile hell, we focus on successful techniques to escape from these common dynamics. Unlike other presentations, we won't be doing a deep dive, but we will cover the most important challenges our audience face.

  • 45 Mins
    Talk
    Beginner

    On average Agile transformations get into trouble at about 14 months from the time they start. Have you ever wondered why?

    Is it because you started from 'the bottom up?" Or is it because you spend time, money, resources and people creating great teams and didn't pay attention to having a professional, empowered Product Owner organization?

    Agile transformations that target department level and not the organization have a very low success rate and you end up with an agile department enveloped by a traditional organization. That leads to dark work, decision delay and dysfunction.

    So, what can you do?

    Come and learn some of what I learned the "hard way" over 7 transformations.

  • Liked Dane Weber
    keyboard_arrow_down

    Dane Weber - Undercover Scrum Master

    Dane Weber
    Dane Weber
    Lead Consultant
    Excella
    schedule 3 months ago
    Sold Out!
    45 Mins
    Experience Report
    Intermediate

    After three years as a Scrum Master and Agile coach, I hit a wall coaching a team that did not want to try popular Agile engineering techniques such as TDD and pair programming. I had become a Scrum Master after four years working on the business analysis and account ownership side of things and could not speak from personal experience about engineering practices. In order to get some first-hand experience and to gain a new perspective, I chose to spend a year or two as a software developer on a Scrum team.

    The experience has been eye-opening. I experienced a tremendous cognitive load working with a wide array of technologies; this pulled my attention away from many of the collaborative and process-oriented activities I cared about as a Scrum Master. I was surprised to feel strong pressure to complete work quickly, cutting corners, even when the Product Owner and Scrum Master were not asking me to. When this pressure was explicit, it usually came from my fellow developers. On the other hand, there is real joy in writing code and seeing a system do something worthwhile that it wasn't doing before. My outlook has changed tremendously and is something I want to share with anyone who works with development teams, especially Scrum Masters and other coaches. I am still enjoying my time as a developer, but I'm looking forward to returning to coaching and incorporating this experience into my approach.

  • Liked Mark Grove
    keyboard_arrow_down

    Mark Grove - Authority and Trust: Finding the Scrum Master Balance

    Mark Grove
    Mark Grove
    Excella Consulting
    schedule 3 months ago
    Sold Out!
    45 Mins
    Talk
    Beginner

    Have you ever seen the term “process authority” used to describe the role of a Scrum Master? You don’t have to look too hard to find this description. In my experience, it has caused a lot of confusion and misunderstanding on project teams. So why is it even used? And should it?

    I worked on a new Scrum project where management informed the project teams that the Scrum Master role was given process authority over the team. There was a lot of confusion and unease about this. Questions started popping up such as “I already have a manager – is the Scrum Master now my boss,” “What does process authority mean,” and “Do we really have to do what she says?” As a result, the teams were becoming hostile to the Scrum Master role, untrusting of the Scrum Master’s responsibility, and concerned Scrum Masters had authority to tell the teams what to do. I was the project’s agile coach and needed to diffuse the confusion and better the working environment as quickly as possible. This did not happen overnight, but our journey started with this interactive discussion which we used as a foundation for the project moving forward.

    In this interactive presentation, we explore the concept of “process authority” and consider the various directions it takes us. To do that, this discussion goes far beyond a typical “the role of a Scrum Master” presentation; It explores…

    • What it should (and should not) mean when/if “process authority” is used to describe the Scrum Master role
    • How the responsibility and expectations of a Scrum Master are different than that of team members
    • How different leadership styles play into understanding the role of the Scrum Master
    • The importance of trust in a Scrum Master/team relationship

    The presentation uses real-time audience feedback to further explore these topics. Audience members will provide answers to questions given throughout the presentation, so we can explore members’ thoughts, opinions, and experiences they have had with the Scrum Master role.

  • Liked Dr. Patrick McConnell
    keyboard_arrow_down

    Dr. Patrick McConnell - The Velocity Trap: Learning to Value Enterprise Outcomes over Team Output

    45 Mins
    Tutorial
    Beginner

    Behind the creation of every Agile Framework was the intention to improve the Return on Investment for creative work, primarily through faster and richer feedback. But as team-level frameworks like Scrum are internalized by large organizations, that message gets mistranslated. Instead of, “Get better outcomes, sooner,” the drive instead becomes, “Just do more, faster.”

    A common expression of this problem is the confusion of Velocity for Value, where teams are directly managed based on their Output, but the connection between Output and Outcome is lost or ignored. This plays out in all kinds of ways that distract from achieving tangible results, and often incentivizes internal competition over collaboration. This problem can be especially tenacious in organizations with significant institutional ‘status-ing’ behaviors, where leadership struggles to translate common Agile methods like Relative Estimating into existing artifacts like Executive Dashboards or Earned-Value Management.

    In this tutorial, participants will explore the 'Velocity Trap', and will be shown how to setup a results-driven framework that prioritizes 'Maximizing Outcomes while Minimizing Output.'

  • Liked Donald Patti
    keyboard_arrow_down

    Donald Patti / David Bulkin - Plays over Plans: Using Transformation Plays to Coach Enterprise Change

    45 Mins
    Talk
    Intermediate

    Unlike agile at the team level, enterprise agility requires cultural change throughout the organization to be successful. But, cultural change is far from easy. Much like the roots of a tree, culture runs deep, so it takes persistence and the right approach to achieve success.

    In this talk, Donald Patti and David Bulkin will describe multiple successful plays, or approaches, to enterprise agile transformation, providing attendees with a number of practical ways to understand and change an organization's culture.

  • Liked Melinda Solomon
    keyboard_arrow_down

    Melinda Solomon / Ken Moser - IV&V Just Looks Like a Four-Letter Word

    45 Mins
    Experience Report
    Intermediate

    The job of an IT Project Manager is a difficult one and traditional approaches to governance tended to make it even more difficult. In the best of times, these approaches employ Independent Verification and Validation (IV&V) as an impediment to project teams; in the worst of times, they set IV&V up as judge, jury, and executioner for projects.


    But just because that’s the way things are often done doesn’t make it right. Oversight entities can be healthy enablers instead of adversarial obstacles.

    Traditionally, the role of a governance framework is to enumerate statutory requirements, promote best practices, and reduce risk. The purpose of an IV&V team within this world is to ensure that appropriate elements of the framework are followed so as to mitigate risk. Larger projects typically present greater risks and require more controls; smaller projects less so.

    The big challenge has always been in defining what is required for a given project.

    Project sponsors want working solutions. The CFO wants tight budgets and lower costs. Project teams want happy sponsors. These stakeholders often oppose IV&V because the cost/benefit case for everything it promotes can be difficult to justify in comparison to business needs. Also, when these stakeholders do not pay directly for development costs they can have a very high tolerance for risk – but that’s an issue for another day.

    What if we re-frame IV&V from risk mitigation to added value?

    • What if, instead of requiring reams of documentation, IV&V identifies information it needs in the tools and processes already in use?
    • What if, instead of forcing teams to follow so-called best practices in cookie-cutter fashion, IV&V provided the metrics and data they need to take specific action when it is most effective?
    • What if, instead of reciting regulations to teams, IV&V worked hand-in-hand help teams meet them in the most efficient ways possible?
    • What if, instead of looking for defects, IV&V asked teams how it could help and then provided the specific support they need, where and when they need it most?
    • What if IV&V helped to onboard new teams and train them in specific skills and resources they will need to succeed?
    • What if IV&V assessed team needs as they worked together and then developed training courses to address those needs?
    • What if IV&V built project dashboards to present useful information from development tools that helped teams surface problems quickly?
    • What if these and other steps help project teams deliver value while meeting regulations, reducing risk, trimming costs, and increasing quality all around?

    What if? There is no what if. This works. It really does.

    These are just some of the innovative governance strategies that our IV&V team at USCIS has employed and it has made all the difference.

    Let us tell you more about them…

  • Liked Scott Swanson
    keyboard_arrow_down

    Scott Swanson - Drive to the Cloud: DOT’s Agile Cloud Transformation

    Scott Swanson
    Scott Swanson
    VP, Cloud Services
    Enquizit. Inc.
    schedule 3 months ago
    Sold Out!
    45 Mins
    Case Study
    Beginner

    Moving to the cloud is perhaps the most popular trend in technology since going agile and arguably just as difficult. What happens when you combine the two?

    The US Department of Transportation (DOT) and Enquizit, an Amazon Web Services Premier partner that specializes in cloud transformation services for education, government and not-for-profits, have done just that. Though cloud transformations often take organizations one or more years, cost millions of dollars and involve a series of failures before success, The DOT’s application of agile to their cloud transitions has shaved that time down to less than 6 months.

    In this talk, presented by Arnel Rivera (DOT,) and Scott Swanson (Enquizit), you’ll learn how the DOT and Enquizit applied agile to moving to the cloud, including what they’ve changed, how they’ve done it and who’s benefited. You’ll also learn some fundamentals about agile cloud transformations that can help you to do the same.

  • Liked Paul Boos
    keyboard_arrow_down

    Paul Boos - Overcoming Your Biases: Putting the GROW and Satir Interaction Models to Work

    Paul Boos
    Paul Boos
    IT Executive Coach
    Excella
    schedule 3 months ago
    Sold Out!
    45 Mins
    Workshop/Game
    Intermediate

    If you hold any form of leadership position, whether as a manager, scrum master, or coach, you will find that you will be at times offering guidance or advice. What unfortunately happens though is that your observation of the need and conversation to help fill that need can get tangled with your biases. Want to improve your coaching conversations? Then this workshop is for you.

    To help you work through the arc of your conversation and understand how these biases come into play, we're going to discuss the GROW conversation model and the Satir interaction model. This workshop will open with an anchoring activity. We'll then use an exercise and focused discussion to review each model and see how these played into the coaching received.

  • Liked Paul Boos
    keyboard_arrow_down

    Paul Boos / George Paci - DevOps Your Organizational Change

    45 Mins
    Workshop/Game
    Intermediate

    DevOps has become all the rage from a technical change perspective; it really has changed the game. And while it provides numerous benefits, only after you also embrace the human side of change within the organization, can you really get to full Agility.

    What if we could take advantage of a continuous delivery of change just like we do in our development pipelines? As executives, managers, Scrum masters, coaches, or anyone else in a leadership role, we should desire to make each change focused, easy, and small to contain risk. Once this is done, changes can mimic a development pipeline that delivers towards a business outcome. This workshop will help you learn how to keep the number and size of changes in check and consider how to manage the risks of deploying change.

  • Liked Dr. Patrick McConnell
    keyboard_arrow_down

    Dr. Patrick McConnell - How do we know when stuff will be done? Let's Play the Release Planning Game.

    45 Mins
    Workshop/Game
    Beginner

    Product Roadmapping, Release Planning, and Release Management are often difficult skills to learn for the Product Owners and Product Managers that support Agile Teams. If the estimates are fuzzy, and don't translate exactly to a linear measure like time, "How do we know when anything will be done?"

    Participants in this workshop will get hands-on experience planning and managing a product Release, and deal with the same dynamics that real Product Owners experience collaborating with Agile Development Teams. Working in Teams, participants will play The Release Planning Game, a tabletop board game created by the facilitator for use in Certified Scrum Product Owner classes.

  • Liked Lava Kumar Chaturvedula
    keyboard_arrow_down

    Lava Kumar Chaturvedula - Are we Agile enough?

    10 Mins
    Lightning Talk
    Beginner

    If the response is between an emphatic ‘No’ to a hesitant ‘Yes’, it is critical to learn what it takes for enterprise to take Agility to the next level.

    In a recent survey, CIOs acknowledged that while many of the execution of processes are followed at the team level by practicing scrum, Kanban, or other agile methodologies, their business processes, mindsets and the rest of enterprise strategy, structure and operations are not truly agile.

    Enterprises and their leaders need to look at ‘Agility’ from a different angle to build it as a capability to not only survive but thrive in a competitive landscape that is constantly being disrupted. Enterprises need to iteratively transform all aspects of how they are structured and operate, to gain incremental agility that is both ‘Strategic’ and ‘Operational’ to gain true and sustainable benefits from agility. Leaders and change agents pay a critical role in leading an end to end transformation that is ground in lean and agile principles rather than practices to better respond and adapt to evolving customer needs.

    Continuous innovation, collaboration, and customer focus are vital in achieving improved productivity, faster time to market, long term customer value, and most importantly - a motivated workforce with an agile mindset.