Scenario: A request for proposal drops. Your company has one week to respond. The scope of the project requires varying experts from several departments across the country to respond. How do you proceed?

Creating a document with many authors is often wasteful and frustrating.  Authors are often unclear on what they are to write and what the overall document should convey. As a result, authors are subject to rework, frustration, lost time, lower morale and lack for overall document flow.

The presentation focuses on how agile can be used to create new documents using Scrum and Kanban approaches. The outcome is an incremental document that is potentially shippable or demonstrable.

 
11 favorite thumb_down thumb_up 2 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

Align Teams

  • What do document delivery and value teams look like?
  • Establish working agreements and cadence

Iterate an Outline

  • Develop document vision through themes.
  • Build enough document structure to begin incrementing.

Slice the Document

  • Discover document user stories, epics and themes with value based mind maps.

Color outside the Silo

  • Write a slice of text and graphics for each user story. (No silo authorship)
  • Scrum and Kanban run parallel.

Continuous Publishing

  • Document Owner provides immediate feedback as stories are completed.

Questions

Learning Outcome

Eliminate waste in distributed document authorship.

Apply value focused approach to writing documents.

Early inspection and adaption with incremental document delivery.

Increase document impact and relevancy.

Keep authors engaged in meaningful contribution.

Target Audience

Technical Writers, Business Developers, Engineers, Program / Project Managers

schedule Submitted 1 year ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • George Dinwiddie
    By George Dinwiddie  ~  1 year ago
    reply Reply

    Steven,

    The outline doesn't give the reviewers enough information to visualize your session.

    - George

    • Steven Sanchez
      By Steven Sanchez  ~  1 year ago
      reply Reply

      Thanks for the feedback George!  I hope the new outline helps reviewers  :-)


  • Liked Manjit Singh
    keyboard_arrow_down

    Agile Business Development? Yes, For Real...

    Manjit Singh
    Manjit Singh
    schedule 1 year ago
    Sold Out!
    45 mins
    Talk
    Advanced

    The presentation is a case study of how Agile (Scrum/Kanban) can be applied to business development (BD).

    Business Development is about managing increasing amounts of investment or determining where to invest. Agile business development is about learning, failing and succeeding quickly in this process. This talk presents a case study from the presenter's personal experience in coaching, training and mentoring 6 BD teams how to apply Agile to their work. 

    The case study will cover how the following challenges of applying Agile to BD activities were addressed:

    • How do you define a Release?
    • How to do release planning?
    • How to define Sprint goals?
    • Do we write User Stories? 
    • Do we size the stories?
    • Do we calculate velocity?
    • How do you do Sprint planning?
    • Do we need a Scrum Master? Who should play this role?
    • What is the right duration of a Sprint?
  • Camille Bell
    Camille Bell
    schedule 1 year ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    You probably started your Agile journey with Scrum, which helped. But regression testing still takes forever. New feature tests aren't what they could be and are hard to complete within the Sprint.

    If you have active product owners, the POs helped to improve your product, but there is still a disconnect, between the user story and the tests.  And how do you test "as a, I want, so that"?

    Now you hear you need Agile technical practices to keep improving and you find you need to automate. What are you going to do with your testers?  They really, really know your business, but they don't code.

    If you are a manager, a tester or a product owner, come hear Camille as she shares her experience successfully teaching manual testers Automated Test Driven Development and showing product owners how to write great Acceptance Criteria that are easy to automate.

    In this session you will learn:

    • How to get your product owners, testers and developers to understand each other
    • How to make your business scenarios unambiguous and testable
    • How to avoid brittle tests that need frequent rewriting
    • Which tools and languages are better for testers to learn and why
    • Strategies and techniques for testers to learn test automation
    • Where to find inexpensive and free resources to get started
  • Liked Raj Indugula
    keyboard_arrow_down

    Dare to Explore: Discover ET!

    Raj Indugula
    Raj Indugula
    John Hughes
    John Hughes
    schedule 1 year ago
    Sold Out!
    45 mins
    Talk
    Beginner

    Ever solve a jigsaw puzzle?  Do you typically design and document all your pieces before assembling the puzzle or know anything about the kind of picture formed by the puzzle?  Hardly.  Usually, the specifics of the puzzle, as they emerge through the process of solving that puzzle, affect our tactics for solving it.  

    This analogy is at the heart of Exploratory Testing (ET) - a fun, focused and powerful approach to testing that has been gaining in popularity in recent years.  While not a new idea, it is often misconstrued as being a random, flailing at the keyboard approach to uncovering problems.  Not quite.  ET is a disciplined practice that involves simultaneously learning about the software under test while designing and executing tests, using feedback from the last test to design the next.  It leverages traditional test design analysis techniques and heuristics, but design and execution become a single inseparable activity.  Within the agile context, there is a need for agile teams to augment their scripted automated tests with a manual testing practice that is adaptable, and ET provides the right fit.

    In this session oriented towards beginning explorers, we will gain a deeper understanding of what ET is, what it isn't, and discuss the essential elements of the practice with practical tips and techniques for: learning the system under test and capturing our understanding to design tests; designing tests on the fly using heuristics; executing tests and observing results; and finally, integrating ET into the cadence of an agile process.

  • Liked Marsha Acker
    keyboard_arrow_down

    Diagnosing and Changing Stuck Patterns in Teams

    Marsha Acker
    Marsha Acker
    schedule 1 year ago
    Sold Out!
    120 mins
    Workshop
    Advanced

    Do you want to be able to “trust the wisdom of the group” but find it difficult? Do you ever feel like you’re having the same conversation over and over again with no real progress? Do you ever feel like you are stuck in a disagreement and not sure how to move forward?

    If any of these issues are standing in the way of your work with groups and teams ‐ ‘how’ you are having (or not having) the conversation is likely contributing to your challenges. Research consistently demonstrates that team effectiveness is highly dependent upon the quality of the communication between team members. Yet it’s easy to get into the flow of daily work and be really focused on the ‘what’ in our conversations without much attention to the quality of ‘how’ we’re communicating.

    As an agile coach one of the most important ways you can serve your team is to help them unlock the wisdom that exists within the team itself and have the conversations they need to have. We’ll explore a framework for learning to ‘read the room’ using four elements for all face-to-face communication. We’ll do some live practice to apply the framework to a conversation and then identify some typical patterns of “stuck” communications that can lead to “breakdowns” in teams.

    This will be an interactive session with people actively engaged in both large group and small group discussions.

  • Darren Hoevel
    Darren Hoevel
    schedule 1 year ago
    Sold Out!
    45 mins
    Talk
    Intermediate
    Abstract:

    This presentation was initial created for an executive leadership team being pressure into the practices of Agile. The Organization soon found their to be a huge gap in the understanding of organizational agility, of not only agile, but the conceptual models needed to drive speed, innovation, and creativity. This session will provide a view into an integral view to change. In 45 minutes I will not be able to cover all of the details in every model, however I plan to present these models in such a way that they the audience will understand what resources are at their disposal to leverage when needed and expand their perspective.

  • Tommie Adams Jr.
    Tommie Adams Jr.
    schedule 1 year ago
    Sold Out!
    45 mins
    Talk
    Beginner

    The Zombie Retrospective - presented by Tommie Adams 

    So they say the retrospective is one of the strongest and most powerful tools in the agile scrum methodology tool kit, and is often overlooked or skipped. So how does a scrum master find ways to creatively explain and express the importance of this agile scrum ceremony, or even the basics of agile scrum in general. How does the scrum master explain the importance of banding together as a team in this brave new agile scrum world.  In many organizations, nowadays, the teams are even made up of outside vendors as well as in house associates. So how do you even start to pique the interest and the importance of team collaboration to a bunch of folks who are strangers to one another on a agile scrum team?  Even more specifically, how do you explain how the retrospective ceremony will help improve the way they work with one another over time?

    My answer: ZOMBIES!!!  Everyone loves zombies, right?  So come, take a bite!

    Tommie works for Marriott International in Bethesda MD. His background is in theater and communication which he studied at Grinnell College in Iowa. He has worked for Marriott International for 26 years with jobs ranging from reservation sales associate, to group sales manager, to functional IT tester to his current position as scrum master for the Marriott Rewards Agile Scrum Team. A native of Omaha, Nebraska, his hobbies include photography, cello and learning the ukulele, (you know, in case you were curious.) 

  • Liked Christy Hermansen
    keyboard_arrow_down

    Inside the GSA – a Case Study of user-centered Agile in a high-profile government agency

    Christy Hermansen
    Christy Hermansen
    schedule 1 year ago
    Sold Out!
    45 mins
    Case Study
    Intermediate

    This unique journey will transport you deep inside the world of the General Services Administration (GSA) Integrated Award Environment (IAE).  You will see how user-centered Agile is transforming the way software applications are engineered, how users' voices have been integrated with large-scale Agile development, and what issues we encountered along the way.

    When Eric Schmidt, former CEO of Google, predicted, "Everything in the future online is going to look like a multiplayer game," perhaps he was envisioning a user community such as ours.  The IAE family of software applications have more than a million users representing federal, state, local, and tribal government organizations; congressional staff; large and small businesses; universities, schools, and hospitals; non-profit organizations; foreign entities; private citizens and others.  Our greatest challenge is the diversity of our user base, resembling a massive multiplayer game in many ways. 

    This case study looks inside a major reengineering effort to migrate 10 legacy applications into an integrated environment while at the same time transitioning from Waterfall to Agile development.  It tells the story of how IAE users have shaped our transformation thus far.  

     

     

  • Liked Jason Hall
    keyboard_arrow_down

    Expanding Beyond Agile. Unlearning Old Lessons on our Journey to Teal

    Jason Hall
    Jason Hall
    schedule 1 year ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    Teal is a natural extension of the Agile mindset, but who would have thought flattening the hierarchy could be this difficult! If Agile removes impediments and empowers teams to deliver more frequently and more valuable offerings, teal removes organizational impediments (hierarchy built on lack of trust ) and fosters empowerment by localizing decision making, re-centering activities around an evolutionary purpose, and aligning the personal with the organizational (wholeness). But what actually happens when you put rubber to road and empower teams to recruit, hire, fire, and determine each other’s bonuses? Well, things get a little messy. If you’re patient, set aside short-term outcomes, and look to long-term gain, it can prove deeply rewarding. I’ll take you on our own evolutionary journey from green to teal and share with you lessons learned along the way.

    If you’re curious about alternative management styles or interested in the next extension of Agile, then come sit, chat, and reflect.

  • Liked Dave Nicolette
    keyboard_arrow_down

    Shit Agile Coaches Say

    Dave Nicolette
    Dave Nicolette
    schedule 2 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    "Language does not just describe reality. Language creates the reality it describes." - Desmond Tutu

    The agile community has evolved into a group of highly enthusiastic proponents who bring a high level of excitement to everything they say and do. Agilists speak a strange sort of insider jargon in which plain English words have very unusual, and often counterintuitive meanings.

    They may describe your multi-billion-dollar enterprise as "dysfunctional" and on the verge of "failure." They may suggest your teams "sprint" to get work done, and yet do so at a "sustainable pace." They may tell your management that agile helps teams "go faster" while assuring your teams that agile isn't about "going faster." They may insist that agile is more about culture and mindset than about practices, and then measure your progress in terms of how faithfully you follow a prescribed set of practices.

    There are many more examples of this odd insider jargon, starting with the seminal buzzword itself, "agile." Over the years, the way agilists speak has confused and turned off many who might otherwise have benefited from applying agile values and principles. The presenter will share several stories of the unintended effects of agile-speak, and will invite you to share your own tales of woe and amusement.

     

  • 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. 

     

  • 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.

  • 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.

  • 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 John Hughes
    keyboard_arrow_down

    Waterfall comfort in an agile world: Give Federal Executives the answers they "used to get" before going agile

    John Hughes
    John Hughes
    schedule 1 year ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    Your effective agile program can go downhill fast even in the most progressive Federal organization if executive leadership begins to think that the answers they used to get in the "Waterfall world" are no longer available to them in an agile world. Federal Executives have elevated reporting responsibilities and need to answer to the public, sometimes even to Congress itself, therefore pressures are high for proper communication flow. Don’t let your program get to the point where “agile just doesn’t work for us.”

    Requirements such as the OMB Exhibit 300 which updates the Federal IT Dashboard and Earned Value Management which is required for larger IT efforts put pressure on Federal executives. They understood how to request the information they needed before going agile, and their teams knew how to get it to them. Agile teams typically no longer create fully resourced project schedules, Gantt charts, and comprehensive requirements documents. Leadership gets frustrated when they can’t get a “straight answer” to questions they are used to having answered such as “what is the project schedule’s critical path showing,” or “are we staffed properly to complete all the remaining requirements by the end of the contract.”

    The answers are still there and the information is still available but the tools and methods by which we produce this information are now different. We need to be able to translate the questions being asked and help Federal executives understand how to better ask the questions to get what they are really looking for. Learn how to extract the necessary information from our agile toolset (Roadmaps, Story Maps, Backlogs, Velocity/Cycle Time, Burn charts, Journey Lines, User Stories, etc.) to give our Federal executives what they need to be successful meeting the myriad requirements applied to Federal IT programs.

    The goal for this session is to provide you the tools you need to continue giving your Federal executives what they need to manage and report on their programs effectively. You will gain insight into what is required of Federal IT programs and therefore what is really being asked, and to help your leadership better ask the questions “in an agile way” so that you may deliver impactful answers derived from our agile tools. You will understand how our agile tools are used and combined to provide the same answers the "Waterfall tools" used to provide Federal organizations. You will return, able to save your agile project from potential doom in the hands of executives under pressure to report against practices they no longer understand.

  • Liked Shawn Presson, CSM, PMP, CMMI, SAFe
    keyboard_arrow_down

    The King is Dead, Long Live…. ”I’m Not Dead Yet!”

    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.