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
  • Catalpa design thinking
  • An introduction to participatory design
  • An introduction to human-centred design (HCD)
  • An introduction to agile methodology
  • How we work within a project or program

Was this helpful?

  1. 5. PROJECT AND PRODUCT CYCLE MANAGEMENT
  2. 5.4 Post-contract implementation
  3. Stage 2: Create and Ideate

Our model

PreviousStage 2: Create and IdeateNextAgile Project Management

Last updated 11 months ago

Was this helpful?

There are many approaches for product development. At Catalpa, we use a mix of methodologies and tools that we have been testing and adjusting to meet the specific needs of the context and nature of our work.At Catalpa, we approach any problem or challenge using that focuses on: Learn, Create, Refine and Evaluate. We use as well as tools. In product development we take our own approach to .

Catalpa design thinking

Learn (prepare, discover and empathise)

Designing meaningful and innovative products begins with understanding peoples’ pains, needs, goals and behaviours.

Create (ideate and implement)

Prototyping a product or service helps us think realistically about how people would interact with it.

Refine (build, release and test)

Through feedback and usability testing, we iterate to make products and features more effective for people.

Evaluate and iterate (measure results, maintain the product)

Ongoing evaluation and iteration on product development means we can enhance our products and scale our impact.

An introduction to participatory design

We create products using co-design and participatory processes. We engage customers, users, beneficiaries and specialists through several mechanisms to ensure the product:

1) is working for the target audience,

2) is delivering functionalities in an inclusive and context responsive manner,

3) has buy-in from users and customers, and

4) is sustainable.

An introduction to human-centred design (HCD)

What is human-centred design?

Human-centred design workshops and exercises help us empathise and deeply understand users and their context. They also provide users and partners with an opportunity to provide input and create a sense of ownership of the design. What distinguishes HCD from other problem-solving approaches is its obsessive focus on understanding the perspective of the person who experiences a problem, their needs, and whether the solution that has been designed for them is truly meeting their requirements. At its most effective, the people who experience a problem the most are a constant part of the design process and, when possible, become part of the design team itself.While the HCD process has many forms, the model we will use for this work is divided into four key phases - Learn, Create, Refine, and Evaluate, with a key focus on regular feedback, incremental approach, and review cycles.

An introduction to agile methodology

How we work within a project or program

There are - at this point - 3 types of products used in our programs:

  • Core products (e.g. Bero, Openly)

  • Bespoke products (e.g. Alfela, Eskola)

  • Off-the-shelf products (we won’t cover this path for now)

Core products - product directions and roadmap are owned and controlled by Catalpa. There is an independent team (product team) working on product development. That team supports project teams but is not embedded within a project. Project teams inform the product roadmap but ultimately the decisions are made by the product lead with the product team.

Bespoke products - we embed a Product Lead and a product team within the project team. The product is developed within the project. It responds to the specific programmatic needs and functional requirements of the project and is fully managed and directed by the project.

Catalpa utilises an iterative and adaptive project management and software development approach called “agile”. Agile approaches help teams deliver value faster and with fewer headaches. Instead of betting everything on a "big bang" launch, an agile team delivers work in small, but consumable, increments. Project requirements, plans, and results are evaluated continuously and teams have a working rhythm that accommodates when there is a need to change or adapt quickly.An iterative and adaptive approach will allow us to test solutions and integrate feedback into the application and program. This methodology takes an incremental approach, very different from traditional project management approaches, such as the “waterfall” approach where requirements are defined at the start of the project with little room for flexibility and adaptation. These ways of working allow our teams to learn, explore solutions, iterate and improve as we progress throughout development. It also ensures the program can adequately respond to risk in a challenging context.For our agile framework we use mainly tools. We use SCRUM in a flexible way to meet our product needs and respond to our project and team constraints. We are flexible, as we understand that the tool or the methodology is not the most important, it is only a tool, a way to achieve development outcomes. You can learn more about SCRUM in this interesting article by .

SCRUM
Atlassian
our design model
participatory design principles
human-centred design
agile methodologies