Inception

What is an Inception? In many ways an inception is similar to a scoping, however, this time around you should have a clearly defined problem and solution. This is the time when we get together as a team and ensure there is a shared understanding on the approach, hypothesis, and metrics. When do you have an inception? This happens after a Discovery and Framing. What do you need to run an inception? Who: Entire development team, designer, PM for the product, stakeholder, and an inception facilitator with a Scribe (someone who takes notes) How Long: <8 hours Goal: Go over the hypothesis for the product, and the potential solution you are going to test technically and how you will measure failure/success in a highly interactive meeting. TIP: Having someone who has done an inception before is highly suggested, you want to make sure that those with the loudest voice are not the only ones heard. Have a facilitator that ensure each person have a chance to speak and share their perspective and understanding. Approach: See agenda below Antigoal: Time to come up with a solution* *This should have been discussed and agreed upon during Discovery and Framing

Note: Facilitating an inception takes a ton of practice, and please ensure that the facilitator is completely unbiased towards anyone involved in the inception. This is where the most mistakes can be made and can actually make all progress made be pointless. A LOT MORE TO BE FILLED IN HERE IN THE FUTURE, if you have questions please reach out to [e-mail]

TIP: Having someone who has done an Inception before is highly suggested, you want to make sure that those with the loudest voice are not the only ones heard. Have a facilitator who will ensure, each person gets a chance to speak and share their perspective and understanding. Agenda: Individual Introductions (3 mins) What is an inception? (5 mins) - What are we hoping to accomplish today - What steps has this product gone through (Scoping, Discovery and Framing) Inception goals and expectations: Go over Discovery and Framing Results (30 minutes) Goals, Elevator Pitch, and Anti-Goals - (45 mins) Risks of delivery and create action items (1 hour) Roles and Personas (1 hour) Hypothesis, Metrics (30 minutes) PLEASE NOTE: It is at this point that stakeholders and those who are not a part of the balanced team can usually be excused. If anyone is excused, please ensure they do a retro for feedback of the meeting. Story Mapping (1-2 hours) Retro (15 minutes) Product Manager and Lead Developer head over to backlog tool and fill in stories