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

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.

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

Outline/structure of the Session

 

  • What is a Pattern?
  • What is the Tuckman Model?
  • Describe patterns found while Forming
    • Describe techniques used to succeed in forming.  Getting the right people on the bus
  • Describe patterns found while Storming
    • Describe techniques used to overcome storming. 
  • Describe patterns found while Norming
    • Describe techniques to encourage and heighten norming
  • Describe patterns found while Performing
    • Describe techniques on how to get to performing and stay there

Note: With each pattern/technique we will solicit examples, suggestions from the audience to add to the list of patterns/techniques

Learning Outcome

Participants should leave this session with:

- Understanding of how to identify a pattern in any state of team development

- Techniques to coach through each stage of team development

Target Audience

Developers, Coaches, Executives, Project Managers, Team Member

schedule Submitted 2 years ago

Comments Subscribe to Comments

comment Comment on this Proposal

  • Liked Shawn Faunce
    keyboard_arrow_down

    Engaging a Product Owner on a Government Contract: Challenges and Solutions

    Shawn Faunce
    Shawn Faunce
    schedule 2 years ago
    Sold Out!
    30 mins
    Talk
    Beginner

    Great systems require active, capable Product Owners.  Functional innovation is not possible without their commitment and involvement in the project.  Too often in government contracting, the Product Owner is an Absentee Owner.  Agile Development teams often seek out tools and techniques to create great systems, however too frequently what is holding them back is the lack of an engaged Product Owner. Teams in this situation must face the elephant in the room if they desire to build a system that brings positive change in efficiency, productivity, quality, usefulness, and adoption.  This talk shares solutions I have used for challenges I see again and again on government contracts.

    The talk begins with some introductory material on the problem, its causes, what I mean by functional innovation, and why this is required to build great systems.  I describe four challenges with Product Owner engagement that are not unique to government contracting, but that I see recurring on projects: committing staff, procurement practices, role ambiguity, and absentee ownership.

  • John Hughes
    John Hughes
    schedule 2 years ago
    Sold Out!
    60 mins
    Workshop
    Intermediate

    Testing sprints? Hardening sprints? Why do so many of us have these and other ways to get around completing all our required testing inside our defined timeboxes? Isn’t our goal to produce deployable features at the end of every Sprint?

    During our session, we will examine why it’s so hard to accomplish all necessary testing inside the iteration and show how to complete these tests within your timebox. Through interactive discussion and real world examples, we will provide insights on foreseeing, overcoming, and avoiding your hurdles and send you home with both long term methods and short term actions that will yield tangible results in achieving your goal.

    Our session will:
    • Illustrate the value of completing all of your testing inside your timebox
    • Identify the challenges in completing all these tests in such as seemingly short period of time
    • Discuss ideas and options to successfully overcome these challenges
    • Explore how to enable your organization and environment for efficient, rapid testing
    • Discuss real world examples of enablement and how we navigated the pain points of enabling testing processes that allow complete testing within an iteration
    • Explore DevOpsSec and how achieving testing within your timebox is a precursor to DevOpsSec
    • Provide short term tactics and actions to immediately improve your ability to complete your testing
    • Allow you to voice your concerns and challenges and discuss potential solutions to these impediments

    Most of us implement agile to reduce the time to deliver valuable working software and to increase the frequency of delivery with high quality through increased and earlier collaboration, shorter feedback loops, and reduced risk. While you can show improvement over Waterfall by performing typical agile methods, you cannot really live the dream without optimizing your agile execution.

    You will leave this session armed with the right knowledge to improve delivery on your current project or start your new projects properly so that you or your clients can reap the benefits of efficient process and high-quality software capable of achieving continuous deployment of fully-tested code at the end of each iteration.

  • Liked Dan Neumann
    keyboard_arrow_down

    Principle-Centered Agility: Your Path to Better Options

    Dan Neumann
    Dan Neumann
    schedule 2 years ago
    Sold Out!
    60 mins
    Workshop
    Beginner

    Do you want to have a high functioning Agile team? If so, this session is for you! We're going beyond the rules of agile frameworks and learning to apply those principles to improve our teams and companies! The 12 principles of the Agile Manifesto capture the reasons we are able to deliver better software. This is the "why" for some of the rules behind Scrum and Kanban. The principles ought guide our decisions about practices, scaling, and solving tricky problems!

    In this session, we will use the 12 Principles of the Agile Manifesto as our foundation. Then, we will  apply techniques such as Force Field Analysis to apply the principles to your challenges at work. Lastly, we will use principles of change management to make the change more likely to stick.

    The outline for the session is:

    1. Explore the principles; which ones are present or absent in your environment?
    2. Introduce Force Field Analysis
    3. Use Force Field Analysis to explore what drives a specific behavior
    4. Use the Agile Principles to generate new options for tackling your team's challenges
    5. Explore effective change management techniques

    With these five activities, you will leave with a framework for change to apply when you return to work and continue on your agile journey.

  • Liked Shannon Ewan
    keyboard_arrow_down

    The Art of Facilitating Agility

    Shannon Ewan
    Shannon Ewan
    schedule 2 years ago
    Sold Out!
    60 mins
    Workshop
    Intermediate

    From an agile implementation perspective, emphasizing the art of facilitation is an incredibly powerful tool for creating a culture of collaboration, and then leveraging that culture as a springboard to organizational transformation.  With strong facilitators at the gateway between business and IT, within IT delivery teams, and at key intersection points within an organization, the challenges to achieving organizational agility diminish. Strong facilitators bring forth the wisdom of teams and provide a container for self-organization. Facilitation is the cornerstone of servant leadership. 

  • Liked Alexei Zheglov
    keyboard_arrow_down

    Five Very Important Numbers And How They Can Help Improve Your Knowledge-Work Organization

    Alexei Zheglov
    Alexei Zheglov
    schedule 2 years ago
    Sold Out!
    60 mins
    Tutorial
    Intermediate

    This session will be about five numerical characteristics of a process.  (Call them "metrics", but beware we will be discussing only those that are difficult to game.)  I chose five of them that are not often discussed,  rarely measured, and even less frequently used in making decisions.

    This happens partly because of inertia.  In the better-studied world of manufacturing physical products and services, for example, one of these quantities approaches 100%, another one is almost always (ideally) zero, and yet another one is a single number rather than a statistical distribution.  You don't even have to think about them.  But when the customer value is created in the brains of intellectual workers rather than on the assembly line, the five quantities we will be discussing reveal non-trivial insights.

    We will discuss what you can do to measure them when you return to your office on Wednesday.  We will also discuss how you can practially use the new knowledge, starting on Thursday, to find new leverage for improvement, find time for work that is important, but not urgent, balance capabilities of your organization with the demand placed upon it, deal with uncertainty, and forecast the delivery of your projects and other commitments.

     

  • Liked shentonfreude
    keyboard_arrow_down

    Making a Better Salad: Behavior-Driven Development with Lettuce

    shentonfreude
    shentonfreude
    Paul Boos
    Paul Boos
    schedule 2 years ago
    Sold Out!
    30 mins
    Tutorial
    Intermediate

    Is your organization still using brittle GUI driven-tools to ensure applications can be tested? Do you find these difficult to map to the user stories that describe product owner/business needs? One of the current Agile practices to doing this is Behavior-Driven Development (aka Acceptance Test-Driven Development) and writing user stories and acceptance criteria in a Specifications by Example format.  This has real power in that business people can understand the tests and the delivery team can ensure the code meets the tests, thus they serve as an example.

     

    This tutorial will give a short background on Specs by Example/BDD and the show you how to write such tests in Lettuce.  You will gain a deeper understanding of how you can apply this to writing your applications.

     

  • Liked Daniel Gullo
    keyboard_arrow_down

    WANTED: Agile Coach, Scrum Master, CEO, whatever... (How to make your Agile transformation successful.)

    Daniel Gullo
    Daniel Gullo
    schedule 2 years ago
    Sold Out!
    60 mins
    Talk
    Intermediate

    The term “coach” has become an overloaded and almost meaningless term in much the same way that “agile” has.  Many individuals are calling themselves coaches who have little or no practical experience with Agile in large enterprise organizations.  Organizations are similarly confused about who they really need to bring success to their Agile transformation, and thus, are advertising for the wrong skills.

  • Paul Boos
    Paul Boos
    schedule 2 years ago
    Sold Out!
    3 mins
    Talk
    Intermediate

    Creating an approach for change is difficult. There is a fine line between imposing an Agile adoption and creating a Transformation where people are collaboratively working together for the change. Based on my experience and in large US Federal Government organizations where imposed adoptions seem the norm, I’ve been working on combining many concepts into a transformation model that can work for large organizations that have ingrained cultures. This starts by helping the organization’s people take ownership and personalize what Agile means to them. Believe it or not, this can work.

    Intended for senior executives and their immediate staff (and the coaches that help them), the Taking Flight approach presents the importance of culture and how creating an organizational aspiration will help guide people. For large organizations, culture has been built up over decades and changing this is of the utmost importance to have an Agile Adoption stick. There are 3 main points I’ll address:
    - how to get people ‘onboard’ with a cohesive direction that they accept by collaboratively building their aspiration
    - how to develop and select strategies for incremental improvement towards the aspiration
    - how to realize changing from old routines into new ones aligned with the aspiration

    To help establish cohesive direction, I use an Aspirational model (your Guiding Star) to help organizations develop the direction they want to go. I show how the differences between an Aspirational model and an End-State. I explain that aspirations are inspiring and allow for a mindset change by not expressing the final state in terms of structure our expected metrics. From there, I discuss different techniques for assessing the current state of the organization and its people and developing strategies and actions for the necessary change management to move towards the organizational Aspiration; this is where the concrete steps come into play. Throughout this portion, I have the group try out various techniques for building an aspirational model and how to build the backlog of work to undertake the transformation. I introduce the Power of Habit as a means to help the organization undergo the necessary behavior changes. I close with a discussion to help the audience think around limiting change-in-progress and how to grow capacity to become more responsive to change.

    In this, you’ll get exposed to a few of many hands-on techniques that can be used to develop your Aspiration and execute on it. These are:

    • KrisMap
    • Business Model Canvas
    • Habit Loops
  • Liked David Kane
    keyboard_arrow_down

    The Role of Architecture in Agile Development

    David Kane
    David Kane
    Dave Dikel
    Dave Dikel
    schedule 2 years ago
    Sold Out!
    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 Brandon Raines
    keyboard_arrow_down

    No Way! Agile in the Federal Government

    Brandon Raines
    Brandon Raines
    Judy Neher
    Judy Neher
    schedule 2 years ago
    Sold Out!
    60 mins
    Experience Report
    Intermediate

    There are so many challenges that organizations face. Healthy organizations continuously tool and re-tool themselves to go from good to great. This session will describe the road taken to transform a major government organization using Agile, Lean and Scrum principles, practices and techniques. From the contracting process to initiating, executing and closing projects, to redesigning the physical workspaces, and moving from a matrix to a team centric structure, this organization completely re-tooled how it did business, for the better.

  • Liked Kerri Sutey
    keyboard_arrow_down

    Implementing Scrum Successfully on a Non-Software Development Project

    Kerri Sutey
    Kerri Sutey
    schedule 2 years ago
    Sold Out!
    30 mins
    Talk
    Beginner

    A common misconception of Agile Scrum is that it can only be applied to software development projects.  This case study examines a DOD Modeling & Simulation project set in a Scrum environment and focuses on the roles, interactions and "rules of engagement" for all relevant stakeholders. Some of the key aspects that will be described are the critical importance of the team, customer involvement, frequent communication, and lessons learned. Executed properly, Scrum can transform the responsiveness, productivity, and quality of products and organizations. This work serves as proof that Agile can be successfully implemented in non-software development projects.

  • Liked Dave Rooney
    keyboard_arrow_down

    Effective Software Delivery - Agility Without the Dogma

    Dave Rooney
    Dave Rooney
    schedule 2 years ago
    Sold Out!
    60 mins
    Workshop
    Beginner
    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.
     
  • Liked Damon Poole
    keyboard_arrow_down

    How to Create Small and Valuable User Stories No Matter What

    Damon Poole
    Damon Poole
    schedule 2 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

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

    Stephanie Vineyard
    Stephanie Vineyard
    schedule 2 years ago
    Sold Out!
    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

    The Art of Storytelling

    Fadi Stephan
    Fadi Stephan
    schedule 2 years ago
    Sold Out!
    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.

  • Leslie Lowman
    Leslie Lowman
    schedule 2 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.