The Catalpa Handbook
  • The Catalpa Handbook
    • Handbook guidelines
  • 1. ABOUT CATALPA
    • 1.1 About Catalpa
    • 1.2 Vision, Values and Strategic Plan 2022
    • 1.3 Governance at Catalpa
    • 1.4 Organisational structure of Catalpa
    • 1.5 Our projects and key contacts for each
    • 1.6 Our key products
      • Bero
        • Content
          • Exams
          • Targeting Content to Users
            • Resizing images for Bero
        • Design
        • Requirements
        • Theming
      • Gathr
      • Openly
  • 2. OUR PEOPLE AND HOW WE WORK
    • 2.1 How we work and the tools we use
      • Google Drive
      • Trello
      • Github
      • InVision
    • 2.2 Communicating internally
      • All Hands Stand-up (weekly / Mondays)
      • Tutorial Tuesdays
      • Show & Tell
      • Guide to Slack
      • Team meetings
      • Other Events
    • 2.3 Mission Driven Teams
    • 2.4 Recruitment and Onboarding
      • Hiring Guidelines
    • 2.5 How we support our people to thrive
      • Onboarding a new hire
        • Onboarding Trello
        • Onboarding buddy guide
        • 30/60/90 Day Plan
      • Goal Setting
      • Regular work/task based 1X1's
      • Quarterly Catch Up's
      • Feedback
      • Managers - Managing Underperformance
    • 2.6 Offboarding
    • 2.7 Leave and public holidays
      • Leave
      • Public Holidays
    • 2.8 Supporting our Mental Health
    • 2.9 Working from home & remotely
    • 3.0. Learning & Development Allowance
  • Page
  • 3. EXTERNAL COMMUNICATIONS
    • 3.1 Guide to Communication
      • Describing Catalpa
      • Guide to photography
      • Guide to social media
      • Writing: style guide
      • Writing: grammar
    • 3.2 Procedures for the collection, storage and use of stories, photos and video
    • 3.3 External Complaints and Feedback Policy
  • 4. PARTNERSHIP AND GROWTH INCLUDING BUSINESS DEVELOPMENT
    • 4.1 Introduction / overview
    • 4.2 Pre-bid stage including networking and partnering
      • Networking
      • Positioning for priority bids
      • Tracking bid opportunities
      • Partnering
        • Partnership brokering
        • Due diligence of downstream partners /subcontracting agencies
        • Pre-bid agreements
    • 4.3 Go / No Go
      • Go / No Go meetings
      • Selection criteria and guidelines
    • 4.4 Tender planning and preparation
      • Project planning and design pre-submission
      • Key templates and links for bid planning and preparation
      • Bid Writing - full proposal or concept note
        • How to appoint an external bid writer
        • Key templates
        • Commonly required building blocks / required materials for tenders
        • Guides
    • 4.5 After a bid has been submitted
  • 5. PROJECT AND PRODUCT CYCLE MANAGEMENT
    • 5.1 Introduction
    • 5.2 Planning and pre-submission design
      • 5.2.1 Monitoring, Evaluation & Learning
        • Project-level M&E
        • Catalpa's organisational approach to MEL
      • 5.2.2 Risk Management
      • 5.2.3 Cross-cutting issues in projects
        • Gender equality
        • Disability inclusion
    • 5.3 Mobilising a new project
      • Handover from BD team to PM team
      • Program Summary Document
      • Team Kickoff Meeting
      • Team Charter
    • 5.4 Post-contract implementation
      • Stage 1 - Learn: Design and Discovery
        • Human Centred Design
        • Our Tools
        • Creating a product
      • Stage 2: Create and Ideate
        • Our model
        • Agile Project Management
          • Getting started
          • Product design and development phases
            • 0. Contracting
            • 1. Learn
              • 1.1. Prepare
              • 1.2. Discovery
              • 1.3 Empathise
            • 2. Create
              • 2.1 Ideate
              • 2.2 Implement
            • 3. Refine
            • 4. Evaluate
          • Product Roadmap
          • Defining releases
          • Create the solution
          • Make a global plan
          • User Stories
          • Prototyping
          • Incremental development
          • UX & UI
          • Conducting tests
      • Stage 3: Refine and Release
        • Introduction and overview
        • Data privacy on a project basis
        • How-tos
          • Retrospective
        • Scrum methodology
          • Daily standup
          • Sprints
          • Sprint prep
          • Sprint meeting
        • Release
          • Epics
          • Epic selection
          • Epic planning
          • Product Q&A, deployment and implementation
          • Make it available
          • Delivery
      • Stage 4: Evaluate
        • Define the maintenance support plan and team
        • Customer support
        • Ongoing user data collection and analysis
      • Glossary of Terms
    • 5.5 Project close-out
      • Product transition and handover
      • Transition to governmen
      • SMA
      • Licenses / handover documents
      • Migrating to Gov owned data-center or cloud hosting
  • 6. POLICIES AND PROCEDURES
    • 6.1 Register of policies and compliance
    • 6.2 Policy Development Procedure
    • 6.3 Code of Conduct
    • 6.4 Data Privacy & Storage Policy
    • 6.5 Human Resources Policies
      • Breastfeeding and Work Policy
      • Occupational Health and Safety Policy
      • Domestic and Family Violence Policy
      • Gender Equality Policy
      • Disability & Discrimination Policy
      • Use of Catalpa Vehicles Policy - PNG
      • Anti-Bullying, Harassment and Discrimination Policy
    • 6.6 Safeguarding Policies, Templates and Training
      • Child Safeguarding Policy
      • Prevention of Sexual Exploitation, Assault and Harassment Policy (PSEAH)
      • Safeguarding templates
      • Safeguarding training
      • Safeguarding procedure for collecting, storing and using images / stories
    • 6.7 Financial and Asset Management
      • Fraud & Corruption Policy
      • Vehicle Use
    • 6.8 Complaints and Feedback
      • Internal Complaints and Feedback Policy
      • External Complaints and Feedback Policy
      • Whistleblower Policy
    • 6.9 Contract Development Procedure
Powered by GitBook
On this page
  • Establish the ground rules of how your team will work together
  • Purpose
  • Documents
  • Timeline
  • Milestones
  • Roles
  • Responsibilities Matrix
  • Team Charter review and update

Was this helpful?

  1. 5. PROJECT AND PRODUCT CYCLE MANAGEMENT
  2. 5.3 Mobilising a new project

Team Charter

A team charter can help bring everyone together to create a shared understanding of who is doing what and how you will work together.

PreviousTeam Kickoff MeetingNext5.4 Post-contract implementation

Last updated 8 months ago

Was this helpful?

A team charter is a process and document thay help a team understand a team’s focus, direction, and establish some clear princinples of how you will all work together. It reduces confusion.

This process should be informal, fun and engaging. Get to know the folks you will be working with, and set up an open, honest relationship. You are trying to build empathy, set a shared vision and create a team that is enjoyable to work with, and has a clear purpose and defined roles and expectations.

Establish the ground rules of how your team will work together

Empathy and communication are integral parts of a strong team. With a team charter you'll outline the essential elements of your team's communication and define a set of concepts and skills that focus and guide your team.

The document's structure includes the following sections:

Purpose

Short paragraph describing the context of the current challenge, who is involved, and the expected goals to achieve.

Documents

Links to relevant documents such as grant proposal briefs, work plans, etc. that will help newcomers understand the context.

Timeline

Information such as program duration and expected start date.

Milestones

Known reporting dates, presentations, and other events.

Roles

A list defining the existing roles and responsibilities within the team.

Responsibilities Matrix

  • Responsible — The individual or individuals who will complete the task. Depending on the size and scale of the project, there may be multiple parties “Responsible” for the task. In many cases, this group or individual is also Accountable for the task.

  • Accountable — This individual ensures that the work is performed; they are the true owner of a task. This may be the project manager or the manager that the team member. The decision maker within the team. Only one person should be accountable for a task.

  • Consulted — Generally subject matter experts, these are people who provide advice before, during, and sometimes after a task is completed. They do not work on tasks directly. If the person Responsible or Accountable does not have enough expertise on the subject or if the task is complicated, another party will be Consulted.

  • Informed — These are the people who should be kept up-to-date about the project but are not expected to give immediate feedback. If feedback is expected then they are being Consulted. In many cases, being Informed may only happen when a task is completed.

Team Charter review and update

When should this document be reviewed?

  • Whenever new team members join or existing members leave

The purpose of this matrix is to clarify who is doing what and how we are collaborating within this team together. Hopefully it brings clarity to our work and helps remind us of each other's involvement. It follows the pattern which defines 4 responsibilities for each task:

Notable examples can be found

Monthly and whenever there's a team

Check the template on Catalpa's Drive
RACI
here
retrospective