Effective Software Delivery - Agility Without the Dogma

This session will explore what "effective" means when it comes to delivering software, regardless of the development method used. The audience will participate by sharing their own experiences and insights in order to examine the similarities and differences between business domains.
 
The goal is to help you to identify what, in your particular context, will smooth out the rough road to a shipped product that meets the needs of the people who consume it, in an indefinitely sustainable manner.
 
 
2 favorite thumb_down thumb_up 0 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

The session will proceed as follows:

  • 5 minutes - Introduction explaining why we're seeking effectiveness vs. following a specific method.
  • 5 minutes - I will explain the session's goal and the mechanics of how the group will work.
  • 15 minutes - The attendees will break into groups of 6-8 people to share their experiences. Specifically, they will be examining projects or products that they would consider successful and that the methods they used to deliver their work were effective in their given work context. They will use sticky notes to record what they felt were practices, actions, etc. that were effective in the context of those projects or product delivery efforts.
  • 10 minutes - Each group will do a "show and tell" to share their key outcomes with all attendees.
  • 15 minutes - The whole group takes their sticky notes and places them with the Agile Principle that is most applicable.  The principles are printed, one per sheet, and placed on a wall in the session area.  If a sticky note doesn't apply to a principle, there is a space for 'Other'.
  • 10 minutes - Questions and wrap-up

Learning Outcome

The overall goal of this session isn't to simply reiterate practices from the standard Agile methods. Instead, the entire group will participate to share their experiences in order to provide the oft-missing context to what has made them more effective in the past.  The final step of associating these experiences with Agile Principles is meant to illustrate how practices and actions that normally may not be considered 'Agile', can in fact be quite effective and do follow Agile Principles.

As a participant, you should come away with concrete actions you can take tomorrow (as well as next week, next month and next year!) to improve the effectiveness of your software delivery efforts.  You may also discover that something you have done in the past was actually quite effective in your particular context!

Target Audience

Managers, Project Managers, ScrumMasters, Product Owners, Testers, Developers

schedule Submitted 3 years ago

Comments Subscribe to Comments

comment Comment on this Proposal

  • Liked David W Kane
    keyboard_arrow_down

    David W Kane - The Role of Architecture in Agile Development

    60 mins
    Workshop
    Intermediate

    In large Government and Commercial organizations with many interacting systems, architecture is necessary to collaborate effectively across disparate entities and systems. Traditional command and control approaches to architecture are often ineffective and cause great tension, especially when Agile efforts are part of the portfolio. We will discuss two principles, Vision and Partnering.  These principles provide insight and get results for both architects and Agilists; and present tools and approaches on how to effectively engage architects and architecture.

  • Liked Dave Rooney
    keyboard_arrow_down

    Dave Rooney - Digging to the Roots

    60 mins
    Workshop
    Beginner

    Whether it's a minor typo on a page, a major failure causing a severe outage of a system or anything in between, the software industry is fertile ground for examining problems and their causes. From the problems that plagued HealthCare.gov to defects that allowed some lucky people to purchase airline tickets for almost nothing from United airlines, we hear a constant stream of issues with software systems.

    With our society becoming increasingly dependent on software, we need to "up our game" with respect to tracking down problems with they happen, ensuring that defects are caught before entering the wild, and are prevented from occurring in the first place.

    Root Cause Analysis is a process that enables this form of continuous improvement and uses techniques borrowed from other engineering disciplines. The aviation industry, for example, constantly seeks to improve due to the dire consequences of any failures in that domain.

    This interactive workshop will explain when and how to use Root Cause Analysis (RCA) to investigate problems and determine actions that will ensure that those problems can never happen again. Using real world examples the attendees will explore simple, lightweight RCA practices as well as a more involved example using fault tree analysis.

  • Liked Damon Poole
    keyboard_arrow_down

    Damon Poole - How to Create Small and Valuable User Stories No Matter What

    Damon Poole
    Damon Poole
    Founder
    Nexxle
    schedule 3 years ago
    Sold Out!
    60 mins
    Talk
    Intermediate

    Putting User Stories into business value order is a key tenet of Agile, but that's just the first step. There's much more value to be extracted from your user stories by making them small and valuable. Not only will you create more value by splitting stories, you will also reduce their cost!

    One of the hardest parts about writing small and valuable stories is overcoming problems like having stories that cross teams or architectural layers. Many organizations say “we can’t show value until the end.” Very often, the “stories” being implemented in these situations are really just tasks masquerading as user stories. This session will show you how to overcome these impediments and create stories that are small and valuable no matter what.

    The key to creating small and valuable stories is story splitting. Techniques covered will include: split by "create/read/update/delete", split by acceptance test, cake slicing, split by generated list, split by keyword, split by user, follow the test scenario, and “hard coding.”

  • Liked Stephanie Vineyard
    keyboard_arrow_down

    Stephanie Vineyard - Making Testable Requirements a Reality: Challenges Faced by an Agile Team and How we Overcame Them

    60 mins
    Case Study
    Beginner

    For a team new to Agile practices, writing clear, concise requirements and acceptance criteria can be daunting. Add to that the additional challenge of automatically testing those criteria. Does your team struggle to manage bugs? As a business analyst or product owner, do you find yourself clarifying user stories and acceptance criteria for the team?

     

    Working software is only as good as the requirements are at identifying the end customer’s needs and having code that executes against those requirements.

     

    This talk will be a case study of the challenges faced by a team new to Agile writing testable requirements and how we overcame them. Attendees will leave with strategies to improve their requirements and acceptance criteria for automated testing.

  • Liked Fadi Stephan
    keyboard_arrow_down

    Fadi Stephan - The Art of Storytelling

    60 mins
    Talk
    Beginner

    Agilists employ user stories as a way to capture user requirements and drive the planning process for iterative and incremental delivery of software. Traditionalists with experience in “big requirements up front” often struggle with the brevity of user stories and how to best communicate requirements. In this presentation, Fadi explains the benefits of using user stories to represent customer requirements. After explaining the basic concepts, he quickly progresses to discuss attributes of a good user story along with different techniques for user role modeling. Fadi shows you how to manage risk and dependencies by properly sizing user stories. Learn what size is the right size and how to deal with constraints, assumptions, and non-functional requirements. Understand the different criteria used to decide when to split or merge stories. Discover different boundaries for prioritizing stories. Leave with new insights on how to write effective user stories.

  • Liked Brandon Raines
    keyboard_arrow_down

    Brandon Raines - Team Development Patterns - A Catalog of Team Dynamic Patterns and How to Use Them

    Brandon Raines
    Brandon Raines
    Agile Coach
    Shokunin LLC
    schedule 3 years ago
    Sold Out!
    60 mins
    Talk
    Beginner

    Most software professionals have read and internalized the Gang of Four Book on Design Patterns.  Every team and it's individual members have experienced the cycle of team development described through the Tuckman Model.  This session combines those two concepts by describing typical patterns of behavior during the team development phases of forming, storming, norming and performing.  Moreover, we will describe techniques to help teams overcome the pains of forming and storming and techniques to thrive while norming and performing.

  • Liked Leslie Lowman
    keyboard_arrow_down

    Leslie Lowman - The Art of Being Agile When All About You Are Not

    Leslie Lowman
    Leslie Lowman
    Senior Consultant
    CC Pace
    schedule 3 years ago
    Sold Out!
    30 mins
    Talk
    Beginner

    Ever feel like your team is fighting an uphill battle when it comes to working with support teams, like Dev Ops or Procurement, to complete a project? Has your team ever wanted to just go buy servers for themselves just so it gets done while they are waiting on server delivery from a supporting team? Well, you are not alone!!

    When it comes to working within government agencies, as well as other private organizations, this is the way most Agile teams end up working. It is all about the project team moving toward being Agile while other teams are not. What does that mean for your project and team? Will things get done? Are there other options? 

    This session will take a look at how it feels to work with non-Agile support teams, focusing on working with government agencies, when your team is trying to be Agile.  We will dive into a world of “what-ifs” and “how tos” that will get you thinking about alternative ways to work within the boundaries of what you can control and how to migrate through the things you can’t.

  • Liked Dave Rooney
    keyboard_arrow_down

    Dave Rooney - Spectacular Business Dashboards with Dashing

    3 mins
    Tutorial
    Intermediate

    Automated business dashboards provide instant visibility into the performance of your business.  You can leverage your existing systems and tools as data sources, giving a real-time view of business health, performance against KPIs and opportunities for improvement.

    The Dashing framework is a Ruby and CoffeeScript-based framework that is simple & lightweight with a minimal footprint, and can be easily deployed internally or to external cloud services such as Heroku.

    This hands-on tutorial session explores the creation of a dashboard from zero to deployed in less than an hour!