Many agile initiatives suffer from a feeble launch.  As Aristotle once stated “Well begun is half done”.  Performing the activities associated with developing a sound charter can help increase the likelihood of success for a team or organization .  

Beginning with the end in mind, we use retrospective techniques to develop consensus around objectives, vision, and mission.  In this workshop we introduce the components of a good charter and how those components help focus the teammates toward a common goal.  In addition, the development of the recommended charter components ensures that key questions are succinctly answered during the kickoff of a team.

Participants will learn the various types of charters and their recommended content.  During the workshop activity teams will develop a complete charter based  team of their choice or a provided case study.

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

Outline/structure of the Session

Presentation to include introduction to charters, types of charters, components, development process for approximately 15 mins.  

Presenters provide more detailed treatment of component then facilitate each group developing that component: 

  • Groups determine target team/organization to develop charter for (case studies provided if needed) - 5
  • Presentation: vision & mission with tests, deciding on values and principals - 10 min
    • Group Activity: develop vision, mission, values & principals with tests - 10 mins
  • Presentation: identifying core team, developing working agreements, boundaries, and interaction  - 5 mins
    • Group Activity: identify core team and establishing working agreements boundaries, and interactions - 10 mins
  • Each group shares their charter - 5 mins

Learning Outcome

Participants will gain a fundamental understanding of how to create a team charter to more effectively define their purpose and set goals and objectives.

Learning outcomes include:

  • understanding the difference between a team and project charter
  • leverage the charter to effectively launch teams and organizations
  • components of a useful charter
  • understand the value of a charter
  • takeaway templates for various types of charter
  • practice developing a team charter

Target Audience

Project Managers, ScrumMasters, and anyone who is a member of a team.

schedule Submitted 3 years ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • George Dinwiddie
    By George Dinwiddie  ~  3 years ago
    reply Reply

    Oops! The session slots were supposed to be 30 & 60 minutes, not 60 & 90. Is there any way this could be shortened to 60? I realize that might be tough, and perhaps we can come up with another solution.


    • Liked Doug Depew
      keyboard_arrow_down

      Doug Depew - Coaching Clinic – Ask the Coach

      60 mins
      Workshop
      Intermediate

      Do you have a pressing issue that you would like to run by a seasoned Agile Coach?  Or just interested in hearing what others issues are and how an experienced coach would address it?  Then this session is for you.  As you come into the room, write your question or situation on a sticky and post it on the board.  A coach from SolutionsIQ will timebox and address as many of these as possible with the larger audience.

    • Liked Richard Cheng
      keyboard_arrow_down

      Richard Cheng - Agile at the Office of Personnel Management: The USAJOBS Product Owner's Perspective

      Richard Cheng
      Richard Cheng
      Principal
      Excella Consulting
      schedule 3 years ago
      Sold Out!
      60 mins
      Talk
      Beginner

      The USAJOBS program was a highly visible, time sensitive program, with potentially high government dollar value. To effectively execute the project, the USAJOBS program decided on an Agile approach and in this approach, government program managers were identified to be Agile Product Owners. This session features the experiences, thoughts, and challenges facing the Agile Product Owners on USAJOBS. Key thoughts from this session include:

       

      1. The differences between Project Management and Product Management 

      2. Shifting from big up front planning to responsible up front planning combined with just in time planning 

      3. Managing Product Owner bandwidth expectations 

      4. The impact of Agile from a Product Owners view

       

      The session is hosted by the former USAJOBS Product Owner along with an Agile Coach.  The session will explore Product Ownership and Agility on Federal Programs.

      Bios:

      Alesia Booth grew up in Federal human resources - her first job was with the National Institutes of Health payroll office at 16 years old. Since then, she's managed websites, document libraries, corporate recruitment programs, staffing systems and hiring reform process change management activities. Which is she ended up at USAJOBS. Since then, Alesia moved to Department of the Treasury to be the program manager of the HR Line of Business CareerConnector product for classification and staffing. At Treasury, she continues concentrate on solving multiple agency recruitment challenges to bring the best and brightest talent into the Federal workforce. Additionally, she worked with Treasury Enterprise Business Solutions as a champion of Agile development and recruitment data standardization Government-wide. Alesia is now back at OPM leading OPM's USAStaffing efforts.

       

      Richard Cheng, Principal Consultant at Excella Consulting, provides consulting services to commercial and federal clients in the Washington, DC area. Richard coaches, mentors, and trains clients on understanding and implementing Agile and Scrum. He also leads Excella’s Agile Center of Excellence.  A graduate of Virginia Tech, Richard has authored several publications on project management, presented at Agile and PMI sponsored industry events, is a member of Mensa, and holds certifications including Certified Scrum Training (CST), Certified Scrum Master (CSM), Certified Scrum Product Owner (CSPO), Certified Scrum Professional (CSP), PMI Agile Certified Practitioner (PMI-ACP) and Project Management Professional (PMP).  Richard is a founder and on the executive committee of the Agile Defense Adoption Proponents Team (ADAPT).

    • 60 mins
      Workshop
      Intermediate

      Trying to figure out Agile Release Planning?  We've done it and we've done it well.  Twelve teams - done! Twenty teams - done! Forty teams - done!  If your organiztion needs to tackle the enterprise release planning beast, you should attend this session.  Whether you are struggling with planning a large agile release planning event or simply trying to figure out how to improve your current agile release planning events, this session will provide nuggets of learning from planning teams with hundreds of people spread around the globe.  Many organizations have tried to conduct enterprise agile release planning and gave up because they could not overcome some of the basic obstacles like who to invite, where to hold the event, and how to keep everyone engaged.  

      If you are trying to figure out how to coordinate two teams or dozens of teams, this session will provide insights into what works and what doesn't.  You will gain expereince by practicing actual agile release planning exercises to help you prepare for your orgainzations next agile RP event.  The learning expereince starts with a presentation on the key steps to consider as you launch a large agile program.

    • Andrea
      Andrea
      Agile Coach
      Santeon
      schedule 3 years ago
      Sold Out!
      60 mins
      Workshop
      Beginner

      Project success =  f (listening, feedback, intentionality, practices) 

      To make your agile practices and processes come to fruition, you need to cultivate an environment that promotes listening, learning, inquisitiveness, intentionality and top notch feedback that everyone is comfortable with. 

      Agile projects succeed when there are frequent high-quality reinforcing feedback loops. I will share communication models based on Clean Language questions of David Grove and the Systemic Modelling techniques of Caitlin Walker that can greatly increase clarity, sense of purpose and listening skills within your team and collaborative endeavors.  These include: Clean Questions, Clean Feedback, and Clean Setup.

      This is a hands-on, try it out, concrete practice session.

    • Liked Wyn Van Devanter
      keyboard_arrow_down

      Wyn Van Devanter - A Thin Automation Framework for Managable Automated Acceptance Testing

      60 mins
      Demonstration
      Intermediate
      Automated Acceptance Tests (AAT) can provide huge value, and can automate time-consuming tasks like regression testing, but aren't easy to scale.  Have you tried implementing them only to abandon them later?  Are they fragile?  Do they give a lot of false positives?  Do they take more time to write than the value you're getting out of them?  These are common problems with automated acceptance testing, but there are ways to mitigate these issues.  One great way is to create a very thin automation framework that helps you write the tests faster while reducing the fragility.  Wyn will walk through writing a thin automation framework, illustrating a test-driven approach that yields a framework appropriate for the software being tested.  The resulting tests are very clean and readable, and they become faster and faster to write as the framework evolves.  He will use C# and Selenium but the concepts are applicable to other languages and browser automation frameworks.  He will also illustrate simple approaches that reduce the fragility and maintenance costs of the tests.  Participants will come away knowing how to get started on an automation framework that will be easy to understand and maintain, and that should scale as much as needed.  
    • Liked Shawn Faunce
      keyboard_arrow_down

      Shawn Faunce - Engaging a Product Owner on a Government Contract: Challenges and Solutions

      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.

    • Liked John Sextro
      keyboard_arrow_down

      John Sextro - Coaching Affinity Estimation

      John Sextro
      John Sextro
      Agile Coach
      9 Principles
      schedule 3 years ago
      Sold Out!
      60 mins
      Demonstration
      Intermediate

      Spend Less Time on Your Estimates

      Most teams would rather work to deliver value to customers than spend time estimating stories.  In order to spend less time estimating and more time delivering value to the customer, many teams have adopted “Affinity Estimation”.  Using “Affinity Estimation” many teams have significantly reduced the time required to estimate and I have personally been involved in sessions that used to take 60 minutes and are now taking 15 minutes.  By using “Affinity Estimation” to compare new stories to real stories that were recently completed, teams are able to quickly and confidently provide an estimate without lengthy discussions and worries of the unknown. 

      What to Expect

      The session will begin with a brief presentation highlighting everyday problems that coaches deal with when estimating stories.  Then, using volunteers from the audience, we will work through a series of exercises/games demonstrating the value of "Affinity Estimation" while teaching the audience and the volunteers how to coach these exercises for their own teams.

      All Teams are Not Created Equally

      This session will provide you with exercises that you can use for existing teams, as well as, new teams. 

    • Liked Katy Saulpaugh
      keyboard_arrow_down

      Katy Saulpaugh - Agile Pushback: Change is hard. Changing to Agile is Harder.

      30 mins
      Talk
      Beginner

      Adopting Agile enables an organization or team to fundamentally change their operating ethos, empower team members and improve project outcomes - and yet those advocating that organization change to Agile are repeatedly confronted with “Agile pushback,” because it “will be too hard,” or say, because “it has always been done this way.”

      How can you use Change Management to help organizations embrace change and make successful Agile adoption?  The key to overcoming the Agile pushback and successfully adopting Agile is the intentional engagement of the 4Cs of Change management – Coaching, Commitment Culture and Communication.

      • COACHING: Using change management as a tool to deepen relationships that help you and the organization leads understand the steeped organizational concerns. This will simultaneously address the core concerns and pushback and while formulating Agile champions.
      • COMMITMENT: Engaging the team will increase commitment to the shift to Agile through a clearly defined mutual understanding of the opportunity of Agile.
      • CULTURE: Aversion to organization change of any size is often rooted in individual concern -- using change management to provide the organization that the change will not be easy but the outcomes will benefit reduce the self-concern and helping the culture understand the4 Agile will empower the culture
      • COMMUNICATION: Agile implementation, like Change Management, is based on intentional communication that clearly articulates roles and expectations – eliminating waste and inefficiency.

       

      Katy Saulpaugh shares her experience, successes and challenges when helping government and nongovernment organizations eliminate Agile pushback and increase Agile adoption. Katy will share case studies from both the public and private sector providing attendees with concepts, methods and change management tools that defeat Agile pushback and easily transfer to a current project or a future Agile adoption.

    • 30 mins
      Talk
      Beginner

      Agile methodologies originated with and gained recognition from software development projects. With an enviable track record of success, more and more organizations are adopting Agile as the standard approach to managing all types of projects.

      You rarely hear about the enviable track record of success managing Business Intelligence projects so you may find yourself thinking about using Agile on your next BI project. Once you decide to try Agile, it can be tough to know where to start. In this presentation, we will focus on the first major step in getting started: Assess the Current State.

      Before you embark on implementing Agile, a crucial path to success starts with knowing where you are today and where you want Agile to take you. The group will identify what we think are the biggest BI challenges. We will go through a provisional maturity model to determine what questions to ask and will discuss how those challenges may or may not be addressed by taking steps to increase your organization's Agile BI maturity.

    • Liked Philip Rogers
      keyboard_arrow_down

      Philip Rogers - Lean Coffee: Creative Uses of this Technique to Rapidly Surface Ideas and Encourage Team Collaboration

      Philip Rogers
      Philip Rogers
      Scrum Master
      NPR
      schedule 3 years ago
      Sold Out!
      30 mins
      Workshop
      Intermediate

      Lean Coffee is frequently used in meetup and conference settings. The beauty of Lean Coffee is its simplicity, and it is this very simplicity which makes it an appealing choice in various Agile team contexts. Specifically, Lean Coffee is particularly good for ad hoc training sessions and for retrospectives. The focus of this workshop will be on the use of Lean Coffee in these two types of settings, where we will split up into small groups and practice using Lean Coffee to cover ad hoc training topics and to do a mini-retrospective.

       

    • Liked Valerie B Santillo
      keyboard_arrow_down

      Valerie B Santillo - The Role of a Leader in an Agile Organization

      Valerie B Santillo
      Valerie B Santillo
      Agile Coach
      Blue Agility
      schedule 3 years ago
      Sold Out!
      60 mins
      Talk
      Beginner

      We hear a lot about leaders who don't "get" Agile and the impact they have on Agile adoption but, what is the role of a leader in an Agile Organization? Agile requires a great deal of change in the way we approach, manage and execute delivery. And, while a great deal has been put in place to educate and support team members, Scrum Masters and Product Owners, there isn’t a great deal available to those outside of teams – especially leaders.  This discussion will present a description of an Agile leader for consideration and the results from two organizations:  One who applied the learning, and one who did not.

    • Liked Shannon Ewan
      keyboard_arrow_down

      Shannon Ewan - The Art of Facilitating Agility

      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 Joshua Seckel
      keyboard_arrow_down

      Joshua Seckel - No defects in a government setting? What does that really mean?

      60 mins
      Talk
      Intermediate

      We have heard a lot about no defects or zero defects, but is that reasonable or achievable in the government context?  How else can each sprint be deployable? Or how can you get to true flow with each story deployed to production?

       This session will explore how to get to a no defects posture across all of the tests required in a government setting. 

      We will look at the various types of testing:

      Unit, Functional, Integration, Security, 508, System, User Acceptance, etc 

      We will look at what defects mean and how (or if) they should be tracked

      We will look at what potential impediments from government organziations may exist in reaching a no defect state of software delivery

      We will look at what tools and techniques can be used successfully in the government setting to address the impediments and achieve no defects in released software

    • Liked Roland Cuellar
      keyboard_arrow_down

      Roland Cuellar - IV&V for Federal Agile Programs: A Customer Experience Report

      60 mins
      Talk
      Intermediate
      1. Many federal government organizations have a requirement to perform independent verification and validation (IV&V) of software development projects for purposes of risk identification and compliance
      2. As more federal agencies move towards agile, they will need to devise agile-appropriate methods for evaulating agile teams and contractors for process performance and project risk identification
      3. Traditional approaches to IV&V are heavily biased towards waterfall, gate reviews, and traditional SDLC artifacts and hence, do not work well within an agile envrionment
      4. Agile programs have their own process-specific risks and issues that need to be evaluated uniquely.  The document-centric approach that has traditionally been used is innapropriate and ineffective for agile teams as it does not find the right risks and does not find them early enough in the development process.
      5. We at DHS/CIS have developed a unique, agile-appropriate IV&V model for a large agile transformation effort within DHS
      6. The model is used to discover process risks, design risks, code risks, and testing risks in real-time for agile teams
      7. The model serves as actionable and real-time feedback to teams, contractors, and federal managers that can be used for process improvement, vendor evaluation, and as a means to find and elevate delivery risks on agile projects
      8. Positive results, challenges, and recommendations related to the development, roll-out, and execution of this agile-appropriate IV&V model will  be shared
    • Liked Richard Cheng
      keyboard_arrow_down

      Richard Cheng - A Roadmap for (Agile) Engineering Best Practices – What Every Non-Technical Person Needs to Know

      Richard Cheng
      Richard Cheng
      Principal
      Excella Consulting
      schedule 3 years ago
      Sold Out!
      60 mins
      Talk
      Beginner

      Summary: Presenting a roadmap explaining engineering best practices, why it’s needed, supporting tools, level of effort to implement, and sequence for implementing.

      21st Century IT development requires building quality into our development practices yet many software teams fail to implement technical practices that are necessary for long term success. Practices like automated builds, automated tests, automated deployments, continuous integration, and continuous delivery are now considered essential for the success of any software development project. Without these practices, the quality of software goes downhill and teams can no longer sustain their initial high levels of productivity.

       

      However, understanding and implementing the practices can seem daunting.  This session presents an easy to understand roadmap for implementing engineering best practices.  The roadmap explains what the practices are, the tools that support the practices, a recommended sequence to implement, and effort to implement.

       

      Though this topic is about engineering best practices, attendees do not have to be technical to get value from this session.  The session gives a non-technical look at a technical concept and is great for any person in the organization managing, working with, or working on IT teams/programs.

       

       

    • Liked Mark Hammer
      keyboard_arrow_down

      Mark Hammer - “Want to be Agile Across the Extended Development Team? Collaborate!”

      60 mins
      Talk
      Intermediate

      How can development organizations ensure building reliable systems, yet responsive to change? This is a fundamental question plaguing Agile organizations. The key is collaboration. Mark Hammer explores process changes and tools your organization can use to ensure high quality software, while maintaining the flexibility to respond to change. He highlights examples from large and small companies showing how simple changes can improve team performance, increase employee satisfaction and save the company money in expensive software fixes.

       The session highlights several key findings:

       1. PROCESS. Best practices for collaboration, focusing on what a collaborative culture looks like. How can managers foster collaboration? How can developers, testers and product managers work together to solve problems previously managed by just one of these groups?

      2. TOOLS. What tools can foster collaboration across these teams? And how can these tools be used to help teams adapt to new customer findings? I review several categories of collaboration tools, with special emphasis on tools that have impacted the ability of specific companies to collaborate and improve quality metrics and results.

      3. MEASUREMENT. Ways other companies have tried to measure collaboration and its impact on team performance, highlighting specific examples including companies that have put in place process and tools then measured their ROI against them.

       

    • Liked Doguhan Uluca
      keyboard_arrow_down

      Doguhan Uluca - Agile done right: Streamlined JavaScript and Node.JS

      60 mins
      Talk
      Intermediate

      Agile development is difficult. Teams can often miss their delivery goals; the unsustainable pace of development can result in fatigue; and technological bottlenecks can make it impossible to deliver a high quality end product. When done right Agile can enable your team to deliver a sustainable and consistent forward flow of features. To achieve this goal you must use technologies that discourages skill silos, are easy to work with and allow for the straightforward application of Agile Engineering Best Practices. JavaScript and Node.JS are the perfect set of technologies that can organically grow within your organization and existing code base utilizing a RESTful architecture. The web is the OS of this decade, and JavaScript is its native language. Creating a technology strategy that effectively utilizes JavaScript is essential to unlocking the full potential of your team and allowing for greater flexibility and reduced risk.

    • Liked Scott Schnier
      keyboard_arrow_down

      Scott Schnier - Shu Ha Ri and Self Organizing Teams

      Scott Schnier
      Scott Schnier
      Agile Coach
      CGIFederal
      schedule 3 years ago
      Sold Out!
      30 mins
      Talk
      Advanced

      Join Scott as he discusses valuable lessons he has learned as an Agile Coach working with new agile teams on government projects. After several years on agile projects in the private sector the shift to agile in the public sector was quite a shock. Scott will discuss how the Japanese martial arts concept of ShuHaRi (roughly translated, it means first learn, next detach, then transcend) has helped him become a better coach when working on Agile transformations on government projects. Explore when the maxim “Let the team decide” is not appropriate and the technique of rationing tools and process to encourage engagement. Engage in thoughtful discussion about the stages of learning and come away with valuable guidance for managing the seeming paradox of self-organization and disciplined learning. This discussion provides a powerful message for agile coaches and scrum masters for teams just beginning an agile journey or just stuck in hybrid mode.

       

    • Liked bchaplin1
      keyboard_arrow_down

      bchaplin1 - Minimizing Technical Debt Via Agile Metrics and Techniques

      bchaplin1
      bchaplin1
      Metrics Architect
      Chaplin Solutions
      schedule 3 years ago
      Sold Out!
      60 mins
      Talk
      Intermediate

      Automate and mine those code quality statistics from Sonar and use Agile techniques to transform your team and codebase!

      Studies show that poor code quality can cut your velocity in half as early as the second release.  But there's hope.  Yes, you can make your deadlines and still have little or no technical debt.  

      Using proper metrics 50% of the 100 committing developers had no tech debt and 100% test coverage for all their code submitted in 2013.  

      Use key code quality metrics to manage your team's quality and ensure your second release is just as productive as the first.    

    • Liked Howard Deiner
      keyboard_arrow_down

      Howard Deiner - Lean Thinking and What It Mean to the Agile Mindset

      60 mins
      Talk
      Intermediate

      Long before the Agile revolution for software development began, industry had learned that efficient production of goods required intense attention to quality, teamwork, and continuous improvement. These themes of Lean Manufacturing (which was further refined into the Toyota Production System) were never part of the original formulation of the Agile Manifesto, and are rarely mentioned as part of the traditional Agile/Scrum recipe for teams transforming to the new “Agile” mindset.

      The reality is that the traditional Agile/Scrum recipe is actually a “dumbed down” version of the Toyota Production System, and makes it easier for organisations to grasp and start from. However, if organizations really want to achieve the goal of producing the software they need in a fashion that leads to High Performance Teams and Sustainable Engineering, they will need to understand the principles of Lean so they can incorporate them into their unique process. This session teaches the basics of Lean, and demonstrates how they apply to Agile development.