Agile and Lean Program Management: Collaborating Across the Organization

Workshop Objective: If you’re managing multiple concurrent projects or a series of releases, you’re managing programs. This workshop will help you learn multiple approaches to uniting your projects or keeping your series of releases on track using agile approaches.

Workshop Overview: Program managers make the strategic decisions across the organization for the good of the total product. While program managers might look like they perform similar tasks as the project manager, they take a holistic product and organization perspective.

While agile approaches work very well for projects, it can be more difficult to make them work for a program. We will experience how to make an agile approach to program management work for you. We will discuss and use examples for managing a program throughout its duration and team building and meetings. We will address the particular issues for all levels of planning. This workshop is experiential in nature, so you can practice with the tools and techniques.

Target Audience: Software or Hardware Engineering/R&D/IT Managers of all levels, Project leaders for software or software/hardware projects, individual Contributors.

Prerequisites: Some prior program management helpful. Some prior agile experience where you release a product helpful. If not, we should add an extra day or so and discuss your needs in more depth.

This workshop is based on Johanna’s upcoming book, Agile and Lean Program Management: Collaborating Across the Organization. Consider conducting this workshop in concert with Deliver! Collaborating Across the Organization as a Member of a an Agile Program Team for the core program team.

Workshop Duration: 2 or 3 days.

Workshop Outline

  1. 1. Introduction
    1. Workshop purpose and expectations
    2. A little about how agile changes everything
    3. Program management definition: scope, teams
  2. Organize the program: Which program team(s) do you need?
    1. Core team
    2. Technical program team
    3. Who is where
  3. Principles that work for programs
    1. What is the ideal: small batch size, continuous integration, etc.
    2. Assess where you are
    3. How will you get from where you are to the ideal?
    4. Visualizing interdependencies
    5. Managing team risks
    6. Activity
  4. Release planning
    1. Program charter defines the context
    2. Agile backlogs
    3. Planning together
    4. Planing when people are remote
    5. Using rolling wave planning
    6. Status reports
    7. Multiple Activities
  5. Small-world networks encourage autonomy, collaboration, and exploration
    1. How to scale out, not up
    2. How to encourage teaming and collaboration among teams
    3. Where communities of practice fit
    4. Embedding architects in teams
    5. Feature teams, component teams, service teams
    6. Activities and debriefs
  6. Working across the organization
    1. Delegation checklist for program managers
    2. Feedback
    3. Influence
    4. Common traps for program managers
    5. Communicating across the space-time continuum
    6. Multiple activities
  7. Managing the Software Program
    1. Help teams deliver
    2. How to use architects
    3. What happens when some teams are not really agile
    4. What happens when some teams use backlogs and some use kanban
    5. When this is your first agile project or you are very new to agile
    6. Activity
  8. Measurements, Dashboards, and How to show program progress
    1. Creating a program dashboard
    2. Activity

For in-house workshops, you have a choice of my simulations or your programs. For public workshops, we will simulate a program throughout the workshop.

Contact me for the extended description.

Tags: , , , ,
Previous/Next Posts
« »

Submit a Comment

Your email address will not be published. Required fields are marked *