Page tree
Skip to end of metadata
Go to start of metadata

Purpose

If you start building your lean offering(s) which has IT components, the IT-Deep-Dive Workshop helps you to plan them in detail. In the first part of this workshop the team should give a recap of the uncertainties and assumptions about the success of their business model. They should focus on all questions and hypotheses which can only be answered / tested by building and launching their lean offering(s). The main part of this workshop defines the minimum set of features of their lean offering(s). Within this session the team collects user stories. A user story is an informal description of a feature: "As a <user>, I want to ..., [because ...]". After the definition and subsequent selection of the feature set of the lean offering(s), the team can start to clarify every feature by scribbling screens as well as the technical architecture of the planned system. Finally the development process, roles and responsibilities will be clarified.

Need support?


Nils JenersWe build your lean offerings and help you defining your must haves.
Contact us: support@orangehills.com.


Duration

1 full day

+ preparation and documentation

Participants

  • Innovation manager
  • Innovation experts
  • IT expert
  • Optional: External experts (like technical staff) temporarily

Preparation

  • Agenda defined
  • Room booked or organized
  • All tools & materials prepared and printed

We usually don't send the agenda to the participants prior to the workshop. We only tell them when we start and end and what preparation is required from their side.

Preconditions

We expect the following output from the Business Design Workshop to be available and elaborated on a detail level:

Documentation

  • All templates (e.g. Lean Offerings, Development Board, Action Plan etc.) are digitized in the Project Workspace; photos of the templates are uploaded to the Project Workspace
  • Tasks for the Design and Validate phase are documented in the Action Plan
  • Collect open questions that have an impact on the development of the lean offerings(s) and cannot be answered by the team on a flip chart. Subsequently the team has to interview customers or partners or do research to answer these questions
  • Optional: The Development Board or Sprint Board can be used to plan the lean offering(s) feature set in sprints and increments

Signs of Success

We consider the IT-Deep-Dive Workshop as a success...

  • ...if we have specified a feature set of our lean offering(s) which can be called minimal on the one hand and on the other hand helps to answer all open hypotheses and questions.
  • ...if we have clarified what can be seen on every relevant screen and scribbled them briefly, such that an IT expert can start the implementation.
  • ...if the team is proud of the level of concreteness of the output.
  • ...if the project team cannot wait to show their lean offering(s) to the sponsor.

Q & A

  • What if we have a feature set that is too big for our lean offering(s)? The two axes (ease of implementation and DNA fit) of the Lean Offerings template help you to prioritize your user stories. Be honest to yourself!
  • What is technically the difference between building lean offerings compared to building a final product? The focus and therefore the trade-offs are different. For the final product you are building to scale (low uncertainty), for your lean offering you are building to learn (high uncertainty). 

  • What about features which users don't see but which are necessary for my system to work (e.g. admin area to manage users)? Don't develop any features which you can do manually too. For example: You don't need to have an user management backend system when you can easily enter the users manually into the database. Most of the time, a good database management tool is enough and no backend system is needed.

Example Agenda

TimeActivitiesFormat*Stakeholders
08:30 - 09:00Arrival and "Good Morning Coffee"BAll
09:00 - 10:00

Pitch of the business model & status quo of the project (focussed on the technical system)

PProject manager
10:00 - 10:30Quick recap and refinement of hypotheses to be tested by launching lean offeringsD / TAll
10:30 - 12:00

Refinement of Lean Offerings template  
1. Detailing and extending
2. Prioritizing

  • Functional requirements
  • Non-functional requirements
TAll
12:00 - 13:00Lunch breakBAll
13:00 - 16:00

Scribbles and prototyping of the minimal set of user stories

TAll
16:00 - 17:00

Definition of the software architecture, technical components, and interfaces
(clarifying responsibilities) 

DIT expert
17:00 - 17:30

Task and sprint management as well as the initial setup of the Development Board

DIT expert
17:30 - 18:00

Wrap-up

  • Today's (personal) highlights
  • Reflection of teamwork
  • Short summary of output
  • Outlook
DIT expert

* P = Presentation | D = Discussion | B = Break | T = Teamwork

Tools & Materials


  • No labels