The Dark Side: Using Dark Stories to Help Product Owners Prioritize Mundane Maintenance

Delivery teams know from experience the importance of maintenance such as applying patches, upgrading, and conforming to the latest security and accessibility regulations. Product Owners, other value team members, and system stakeholders are focused on functionality and end user satisfaction. Maintenance isn’t sexy and can sink in priority until it fails to be included in releases.

 

The Security community has been using Dark/Abuser/Evil Stories using the persona of a Black Hat Hacker to uncover vulnerabilities. In this workshop participants will assume the role of Delivery Team members and use the power of personas to write “Dark Stories” that bring to life the full impact of failing to perform necessary maintenance.  The intent is to give Product Owners a complete understanding of the importance of maintenance so they can appropriately prioritize maintenance and keep their systems strong.

 
 

Outline/structure of the Session

  1. Introductions and What are dark stories and why would we use them (5 minutes)
    • Example of a Dark Story for discovering Cyber Security vulnerabilities
    • Example of a Dark Story for Maintenance
    • The Power of Personas
  2. Workshop participants are given sticky notes and markers to write down maintenance topics that would normally go into a backlog as boring technical stories but could be written into Dark Stories. They post their sticky notes at the front of the room. (5 minutes)
  3. Participants are given dot stickers to vote up the topics that they think would make the best Dark Stories. Participants will be seated at the tables and each table will become a small team. Each small team will choose one person to take one the roll of Product Owner. The presenter will organize the topics in order of the most votes. The topics that the group has found the most interesting will be assigned to the teams. (5 minutes)
  4. The small groups proceed to create a persona (get creative!) for the Dark Story,  write a compelling Dark Story, and put it on the flip chart. (10 minutes)
  5. Each small group presents the persona and Dark Story they created and the presenter facilitates a discussion of the story. Participants will be asked about why they made the choices they did. (15 minutes)
  6. The Product Owners will use dot stickers to vote up the Dark Stories they find the most compelling and appropriate. The attributes of the story receiving the most Product Owner votes will be discussed. (5 minutes)
  7. Closing statements and opportunities for participants to discuss their insights on the use of Dark Stories, as time permits.

Learning Outcome

  • Attendees will be introduced to the utility of Dark Stories
  • Attendees will have the opportunity to practice writing Dark Stories and to gain the insights of the other workshop participants
  • Attendees will learn how personas and story writing can be used to help Product Owners prioritize important maintenance

Target Audience

Scrum Masters/Agile Facilitators, Delivery Team Members, and all other Agile Practitioners who have an interest in ensuring systems are well maintained

Requirements

Small group tables for working sessions and conversation

Flip charts, sticky notes, dot stickers, and markers for each table

schedule Submitted 1 year ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • John Hughes
    By John Hughes  ~  1 year ago
    reply Reply

    Maintenance is often forgotten and the value of security and maintenance usually is not seen by the business side, at least in comparison to their business features. I can see Dark Stories as a great way to communicate the value of addressing this work with the limited capacity a team shares with business side features. 


  • Liked Timothy Kwan
    keyboard_arrow_down

    Improvement and Coaching Kata: Fostering a culture of learning and experimentation

    Timothy Kwan
    Timothy Kwan
    schedule 1 year ago
    Sold Out!
    45 mins
    Workshop
    Intermediate

    Many large organizations try to get real innovation with lots of time and resources, but many end up failing and complaining when their innovation never arrives.  What we see in these organizations is that there are individual and organizational habits that cause innovation efforts to fail.  These organization rewards acts of heroism rather than acts of learning and punishes those that makes failures.  As the individual level, it encourages maximizing completing project work over learning and minimizing taking risks.

    What this all means is that these organizations have a culture that inhibits learning and creativity.  These organizations wonder why innovation never comes.

    True innovation in the IT world is only possible by leveraging creativity, which requires a mindset of learning and being able to accept failure.

    Improvement and Coaching Kata also known as Toyota Kata, is a model and technique that can help incrementally move IT organizations towards a culture learning and experimentation.  Its practices involves everyone in the organization working collaboratively towards the vision of the organization.  By understanding where the organization wants to be in the far distance future, we analyzes what is the current state and value streams of the organization, and what experiments could be run to learn more on improving the various processes.  All continuous improvement efforts are executed with systematic experiments with the vision in mind.  The primary outcome of these experiments is learning. It does not matter if experiments succeed or fail(to a certain degree), only if we apply its valuable learning to the process or new experiments.  

    By doing Improvement and Coaching Kata on a high frequency cadence(daily), new habits form that encourage learning and experimentation. 

     

     

  • Liked Timothy Kwan
    keyboard_arrow_down

    The Art of "being" rather than "doing" DevOps

    45 mins
    Workshop
    Beginner

    When organizations start to adopt the DevOps methodology, many groups tend to react in similar ways.  The business and PMO office will see it as "something" to buy, implement and deliver product faster, while the techies will think of the many cloud infrastructure tools enabling continuous integration, continuous delivery, monitoring, and automation.  As human beings, we tend to focus on what the practices are("the doing"), and we lose sight of what is really important("the being").  For DevOps adoption, we need to ask ourselves,  What is the mindset behind DevOps? its values? its principles?  

    Let's get away from the chatter of "doing" DevOps and move more towards "being" DevOps.

     

    Instead of listening to the great stories on adopting DevOps and its technical complexities, we'll experience through an agile game

    • What does DevOps look and feel like end to end?
    • What is the mindset behind DevOps?
    • What does DevOps culture look like?
    • Your own self-realized outcome!
  • Liked PHILLIP MANKETO
    keyboard_arrow_down

    Unlock the Power of Agile in Your Organization

    PHILLIP MANKETO
    PHILLIP MANKETO
    schedule 1 year ago
    Sold Out!
    45 mins
    Talk
    Beginner

    “More and more organizations are realizing the benefits of running projects using Scrum, XP, and/or Kanban at the individual team level. Unfortunately, the typically means that in a 12-24 business idea to production time-frame, the “Agile” part may only be a 1-3 month “construction” phase with rigid controls in place that all but eliminate most of the benefit of Agile.  The root cause of this issue is that the whole organization is purpose-built to support and reinforce traditional methodologies while unintentionally impeding and discouraging the use of Agile methodologies. This is reflected in the organizational structure, physical location of people, the physical workplace, policies, procedures, governance, SDLC, contracts, vendors, belief systems, compensation, software tools, funding model, metrics, and more. A common belief is that all of these are set in stone and that Agile will need to fit in to this existing framework. As a result, many Agile adoptions eventually regress as the effort of working around the existing framework overwhelms the enthusiasm of the Agile evangelists. Unlocking the full power of Agile requires an understanding that changing the status quo is a long-term, organization-wide, major initiative that will take significant resources to accomplish. Such an initiative will only be undertaken if the rewards are significantly greater than the cost. In this session, you will learn about the true barriers to Agile adoption; the surprising and significant financial benefits of organization-wide Agile transformation; and the Kotter Change Model, an approach for implementing major change management efforts.”

     

  • Maria Fafard
    Maria Fafard
    schedule 1 year ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    Are you ready to take control of your career in Agile space? Then this session is for you! Learn to build your personal brand, establish your career goals and reach them using an Agile mindset. The session is equally relevant for beginning and experienced Agilists, for people in the midst of an active job hunt and these who have already secured their dream position but are not sure how to take their career to the next level.

    Learn how to job hunt like a pro and how to attract recruiters and hiring managers instead of relying on job applications; how to seek and secure a promotion; how to insure your Agile career; and how to network in a powerful and focused way.

    Find out how to leverage the power of social media in your brand building efforts, including the ultimate brand building and career management tool, LinkedIn: develop and maintain a strong LinkedIn profile that includes an Agile work portfolio, a powerful Summary, and a results oriented Experience section; develop an ongoing engagement with Agile LinkedIn community using status updates, LinkedIn publishing platform and Agile groups and grow and nurture your network. Bonus: you will learn about making the first steps towards thought leadership.

  • Liked Richard Cheng
    keyboard_arrow_down

    Let's all agree to agree - The importance of a Team Charter

    Richard Cheng
    Richard Cheng
    schedule 1 year ago
    Sold Out!
    45 mins
    Workshop
    Intermediate

    We've all see Project Charters.  Project Charters usually state the vision, mission, roadmaps, and is hand top down to the teams.  However, how many of us have Team Charters in place.  Team Charters are one of the most powerful tools a team has when it comes to being able to work effectively together.

    This workshop explores the dynamics of creating a team charter, the definition of ready, and the definition of done and how all this works together to create software that is ready for review, to potentially shippable, to released into production.

     

  • Liked Richard Cheng
    keyboard_arrow_down

    Situational Retrospectives – One size does not fit all

    Richard Cheng
    Richard Cheng
    schedule 1 year ago
    Sold Out!
    45 mins
    Workshop
    Intermediate

     

    Situation A: Your team is great. You’ve met all your sprint goals and your Product Owner is pleased with the results to date. Yeah!

     

    Situation B: Your team sucked. Zero story points completed last sprint. Team members are complaining and blaming each other for the failures.

     

    These two situations demand two very different retrospectives. The right retrospective can make a good team great and turn a bad situation into a learning opportunity. A bad retrospective can set a team back and create a non-safe working environment.

     

    In this session, attendees will explorer retrospectives techniques and examine the pros and cons of the techniques. The workshop will then explore scenarios and examine how to effectively run retrospectives across a variety of scenarios.

     

    Coming out of this sessions, attendees will have an understanding of applying the right retrospectives based on the state and needs of the team and projects.

     

  • Liked Chris Li
    keyboard_arrow_down

    The Tadpole Technique - Breaking things down in a new, interactive way

    Chris Li
    Chris Li
    schedule 1 year ago
    Sold Out!
    45 mins
    Workshop
    Beginner

    The Tadpole Technique is an approach that teams can use to break a larger idea into smaller pieces in an interactive and visual way.  This facilitated session is a way to get team members to participate in some chatter as well as as generate a few takeaways from the session.  This technique is useful in meetings where a group of approximately ten individuals and a facilitator go through a series of discussions following a brief writing activity.  The result is a visual representation of the teams thoughts and discussion, and can be used to further expand later talks or to create some takeaways.

    This talk will explain the mechanics of this technique, what teams will need, and explain how to facilitate the session.  Participants will then engage in an exercise where they get to experience the technique as a group, enhancing their ability to facilitate future sessions of their own. 

  • Liked Darrin London
    keyboard_arrow_down

    Stop! Coordinate and Listen: Bring Standups back with a brand-new convention!

    Darrin London
    Darrin London
    Tim Meyers
    Tim Meyers
    schedule 1 year ago
    Sold Out!
    45 mins
    Talk
    Beginner

    According to the VersionOne State of Agile survey, the most widely practiced agile technique is still the daily standup (80%).  Everyone knows its a critical part of agile and we all can recite the three questions by heart.  But why do many agile teams say their standup just isn't working?  Even though the stand up can be done very easily on an agile project (setup a 15 minute meeting every day and your done!), it takes some work to get the true value out of it. Everyone has probably been in that stand up where the energy level is very low and there just seems to be a group of people going through the motions.  Or maybe there is dissention among the team and nobody wants to go anymore.  In this workshop, we’ll discuss why stand ups are a critical practice for agile teams and how you, as an agile coach or Scrum Master, can support your teams in pursuing a useful, valuable stand-up and get out of the standup blues.

  • Liked Brian Sjoberg
    keyboard_arrow_down

    Pump Life Back into Your Local User Group

    Brian Sjoberg
    Brian Sjoberg
    schedule 1 year 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.

  • Liked Luke Lackrone
    keyboard_arrow_down

    Your Sprint out the door! A Sprint planning simulation.

    Luke Lackrone
    Luke Lackrone
    Tim Meyers
    Tim Meyers
    schedule 1 year ago
    Sold Out!
    45 mins
    Workshop
    Intermediate

    Sprint Planning is a frequent, important part of the rhythm of many agile teams. And yet, we find that many coaches and Scrum Masters struggle to make the meeting relevant, valuable, and creative. We will work through a simple, relatable simulation that we use to teach effective planning to teams and facilitators that brings energy, creativity, and problem-solving to the Sprint Planning experience. 

     

  • Tim Meyers
    Tim Meyers
    Darrin London
    Darrin London
    schedule 1 year ago
    Sold Out!
    45 mins
    Talk
    Beginner

    Retrospectives are often one of the first team ceremonies to get dumped for time, or to fall flat as we repeat the same boring patterns. Yet, many voices tell us they are the single most important practice our teams could be doing!

    We agree, and we will show you how to put some zip back into your retrospectives. Learn how to use a retrospective as the first-engagement with a new team; how to use the form to begin building trust and understanding in the team; and get your colleagues on the path to continuous self-improvement!

    This session will take you beyond the Plus-Minus-Delta, By-The-Book format for a retrospective, explore the Derby-Larsen framework through activity demonstrations, and provide an opportunity for attendees to put this new knowledge into practice as they design a deeper, groovier retrospective to take back to their teams.

  • Liked David Horowitz
    keyboard_arrow_down

    Distributed Agile -- The Dark Ages or Enlightenment?

    David Horowitz
    David Horowitz
    schedule 1 year ago
    Sold Out!
    45 mins
    Talk
    Beginner

    Agile works best when the entire team is sitting together in the same office. Or does it?

    The reality of today's working world is that more and more teams have people working remotely. As agile practitioners, we must "inspect and adapt" to this new world. What strategies should we use to make agile work better in a distributed world? How important is picking the right tools vs. setting a positive culture? What practices should team leaders and Scrum Masters of distributed teams implement to make distributed life easier and more effective?

     

    presented by David Horowitz

    David is a co-founder and CEO of Retrium. Retrium makes distributed retrospectives easy and effective through the use of a real-time facilitated web app that enables private ideation, dot voting, prioritized discussion, and the creation of action plans. In a prior life, David was a software developer for The World Bank for 9 years.

  • Liked Theron Todd Kelso
    keyboard_arrow_down

    Agile for Good: Creating an Agile community and toolbox for Not for Profits

    Theron Todd Kelso
    Theron Todd Kelso
    Sanjiv Augustine
    Sanjiv Augustine
    schedule 1 year ago
    Sold Out!
    45 mins
    Workshop
    Intermediate

    All Not for Profits aspire to be effective, nimble, and fun all while changing the world. Agile mindsets and practices can help all nonprofit organizations use technology agile concepts skillfully and confidently to meet community needs and fulfill their missions.

     

    Successfully implementing and fully adopting agile can be seen as unnecessary overhead.  Creating an Agile community and toolbox for Not for Profits would greatly reduce the organization change costs and allow not for profits to benefit faster.  This community would facilitate the exchange of knowledge and information within the agile community and within the Not for Profit sector. It would connect members to each other, provide professional development opportunities, educate our constituency on issues of technology use in nonprofits, and spearhead groundbreaking research, advocacy, and education on technology issues affecting our entire community.

  • Liked toddcharron
    keyboard_arrow_down

    Improv Your Agile or Scrum Stand-up

    toddcharron
    toddcharron
    schedule 1 year ago
    Sold Out!
    45 mins
    Workshop
    Beginner

    Your Agile Stand-up Meeting Sucks!

     

    Most Agile and Scrum stand-up meetings I see are boring, lifeless, status meetings that don't provide any real value.

     

    In this session you'll learn:

     

    The REAL purpose of the daily stand-up

    The most common bad habits and how to correct them

    The habits good stand-up meetings have

    How you can use Improv to invigorate your daily stand-up

    A whole bunch of Improv exercises you can start using with your team right now!

  • Pradeepa Narayanaswamy
    Pradeepa Narayanaswamy
    schedule 1 year ago
    Sold Out!
    45 mins
    Workshop
    Intermediate

    In agile teams, it’s inevitable that team members are expected to be more cross-functional and produce high quality product for their customers. How can agile team members become more cross-functional and take ownership of quality? Often times there seems to be a scarcity of testing talents in agile teams. How can agile teams attain highest quality product when working with very few or no testing talents? 

    For agile team members to take ownership of quality, Pradeepa Narayanaswamy exposes the power of “Pair Testing” that greatly supports providing faster feedback and producing high quality product all along as a team. For the scarce testing talents and an effective way to become more cross-functional, one approach is for team members to pair up on various (unit, integration, exploratory and several other) testing efforts that ensures the shared eye on quality and learning. Pradeepa talks about several pairing options and opportunities between various specialties in an agile team. She also talks about some “non-typical” pairing opportunities with DevOps, Operations, Sales, Marketing and Support members to name a few. 

    As a new or an experienced agile team member, learn how to spearhead this technique in your team at various levels and spread the buzz to other teams. As a tester, learn how to get the non-testing talents excited and experience the value of pair testing.

  • David Fogel
    David Fogel
    schedule 1 year ago
    Sold Out!
    45 mins
    Talk
    Beginner

    Yoda said: “Ready are you? What know you of ready?”

    Yoda also said: “You must unlearn what you have learned. “

    Product Owners want everything – NOW! As process ninjas, coaches, and general Agilists, we help product owners appreciate the value of prioritizing. With Agile, the PO will iteratively and incrementally get a great product. Sometimes, we Agilists want our teams to have ALL the best practices – NOW! Maybe we could work iteratively and incrementally get a great team – but how to prioritize?

    In this talk we will discuss (A) the problem in terms of the Satir Change Process Model; (B) the Shu Ha Ri method of prioritizing change; (C) Mike Cottemeyer’s “Three Things” to prioritize change; and (D) a mini-workshop in which we take a look at several teams and what might be the “process” for them to achieve good process! Also, we may have accidental fun.

  • Liked Matt Phillips
    keyboard_arrow_down

    Avoiding the 2-week waterfall: Common Scrum pitfalls and how to tackle them

    Matt Phillips
    Matt Phillips
    schedule 1 year ago
    Sold Out!
    45 mins
    Talk
    Beginner

    Often when organizations go through an Agile transformation, there are some concepts that are challenging to address or adopt. We have a tendency to avoid the ‘crucial conversation’ so as not to hinder progress. Eventually these fundamentals can get overlooked or "put on the back burner". At this point transformations stall, and we find that our process is operating more like a 2 week waterfall than an Product-Increment-Producing-Machine-of-Wonder. I believe this behavior is one of the drivers for the ‘scrum-but’ concept.

    This session will delve into anti-patterns, bad smells, and other pitfalls which are keeping organizations from reaching the next level of Agile adoption. We’ll examine common warning signs and identify strong signals that indicate that a sprint time box is not being optimized. Once we’ve identified the challenges, we’ll explore best-practices, tweaks, and courageous actions to get teams collaborating in a first-class manner. 

    In short:  Step 1: Understand what is hindering our Scrum practice. Step 2: Surface actionable remedies that we can apply tomorrow.

  • Liked Luke Lackrone
    keyboard_arrow_down

    #awkward - Coaching a New Team

    Luke Lackrone
    Luke Lackrone
    schedule 1 year ago
    Sold Out!
    45 mins
    Talk
    Beginner

    When we have our most successful coaching moments, they often come from a deep groove: where we seem to anticipate the team's needs; know when the breakthroughs are coming; know how to dance between mentoring the team and letting them innovate (or struggle) on their own. But, it rarely starts that way. Coaching new teams can be awkward -- and especially so if you're new to coaching. I will show you some ways of approaching these coaching engagements that can break down the awkwardness, reveal things about the team, and get on a track of improvement and discovery.


    I will share some attitudes I think can benefit coaches who find these situations awkward, as well as practical tools and tips you can exercise tomorrow to get teams talking and making progress. We will also engage as small groups, for further practice on these tools and to create space for coaching one-another.

  • Awais Sheikh
    Awais Sheikh
    schedule 1 year ago
    Sold Out!
    45 mins
    Workshop
    Intermediate

    As we see Agile evolving through the years, particularly into the government space, a lot of terminology is used that seems foreign to many who first used agile with their individual teams.  "Hybrid Scrum"..."Delegate Product Owner"...even "Scaled Agile".  Are these simply extensions of the agile values and principles in the manifesto to fit a different and more complex environment, or do they represent a diluting of those same values and principles?  Explore in a facilitated workshop with your peers whether such terms are appropriate (maybe even necessary) to adopt agile in the complicated enterprise, or whether they represent (oxy)moronic agile and a step backward.

  • Shawn Presson, CSM, PMP, CMMI, SAFe
    Shawn Presson, CSM, PMP, CMMI, SAFe
    schedule 1 year ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    Subtitle:  The CMMI Is Still Among Us – How To Cope

    (This is an update to a presentation given at STC 2003 entitled “The Agile Non-Debate.”)

    Agile methods have spread worldwide, and have helped bring tremendous improvements in system development.  And yet, they are not 100% successful.  When I entered into discussions about using agile, IEEE, CMMI, ISO, and other standards, a common position was that CMMI et al suck innately, while agile efforts failed because people were “doing it wrong.”  This polarizing position was a distraction. 

    Now, such polarization can be damaging.   Despite Agile’s increasing toehold in the public sector, the CMMI is far from dead; organizations are letting contracts based on agile requirements with one hand, and others based on CMMI and other certification-based models with the other hand.  Treating the two as mutually exclusive is just too hard, and its unnecessary.  Worse, it clouds the reality of how the two approaches actually differ and how they can be harmonized.  While a SCAMPI-like appraisal method for Agile has not gained wide traction, such a monster could arise, and understanding Agile CMMI interpretations could help organizations survive such a monster, and perhaps help Industry nip it in the egg.

    In this session we will discuss briefly how the CMMI world got to be such as mess, how Agile has helped cut through a lot of that, and how to prevent some of the same ills from infecting the Agile world.  The core of this discussion, however, will be about juggling agile performance and CMMI compliance simultaneously.