Search Results

Baseline Technical SpecificationsWhere an existing solution is already in place, analyse its implementation, assess the strengths and weaknesses of the implementation, and decide if any parts can be reused. Do this from a technical and user-oriented perspectiv...

❓What is it Card sorting is a user-centred design technique used to explore how users group and categorize information, helping designers create or refine the information architecture of websites, apps, and other systems. This technique is particularly val...

SPM and PM in nutshell Product Manager: Strategic and Broad Product Manager: Tactical and Focused SPM and PM Shared Responsibilities This list of responsibilities for SPM and PM (PO) has been specifically tailored for WCC’s needs and ...

At the back end of discovery we should ask the following questions to increase confidence in the business case. These questions should be part of a collaborative conversation in thee amigos style. Validation with Technical Architect Have you discusse...

❓What is it Source control, also known as version control or source code management (SCM), refers to the practice of tracking and managing changes to codebase over time. It allows multiple developers to work on a project simultaneously, helps in tracking ch...

❓What is it Hypothesis thinking ensures that decisions are objective, deliberate, data-driven, and focused on continuous learning and improvement. This practice enables a team to turn assumptions into a testable format - a hypothesis. Its fundamental premi...

❓What is it It is used to help quickly prioritize a backlog of work associated to a service or product based on relative prioritisation. Each of the items are assessed against two criteria: the value that is realised from delivering it, and the effort requi...

- let's cook! -   

A  Topic Description Agile Agile methodology is an iterative Product Development approach and philosophy that emphasizes customer value and continuous improvement.The agile methodology encourages frequent feedback and the ability ...

~ 1 to 2 weeks We have lots of insight from multiple sources we think might be worth exploring. ➡ Input Customer insights Market Landscape Technology Landscape Business Objectives/ Strategy Service performance insight Idea capture form ...

~2 - 4 weeks We have prioritised ideas we want to explore in more detail so we can confirm it solves a real problem for the customer ➡ Input Problems to Solve   or   Ideation output Ideas backlog Draft vision statement Agreed sponsor C...

~ 2 to 4 weeks We want to find a solution that demonstrably solves a valuable customer problem ➡ Input Prioritised experiments (test and learn cards) Defined Problem Statement User Segmentation Hypothesis Supporting research Key unknowns ...

Optimal velocity target is ~2 weeks We prioritise our backlog of committed work to maximise delivery of value to our customers as early as possible ➡ Input Prioritised Backlog Acceptance Criteria Test Scenarios Release Plan / Road Map Refe...

and improve through measuring and learning ongoing We measure metrics that matter,  continually capture customer feedback and proactively identify new opportunities to improve the product experience ➡ Input Service analytics Customer feedbac...

Scoping, Resourcing & Planning Discovery Pre-Discovery Planning Everything that needs to be in done by R&D before Discovery Starts Identify key Stakeholders Identify Key Services Involved. Plan & Schedule Primary Research Kick-off brief session with Co...

A cheat-sheet to help drive effective outcomes and facilitate inter-departmental communication. Technology What's our current tech stack and why was it chosen? How do we stay updated with the latest technology trends? What are the biggest tech-debts we...

Objective A hands-on game where you'll learn Product Ways of Working by building a cubed box with an integrated lid from a single sheet of A4 paper. Experience the thrill of teamwork, creativity, and competition, all while mastering the fundamentals of Agile....

Introduction (5 minutes) Briefly explain the objective of the game and the rules. Divide participants into teams of 6-8 people. We nominate a Scrum Master for each team. Scrum Master keeps time and helps remove any obstacles. Gets a print out of the timbo...