Hunting plan

Hunting is an activity that requires preparation, coordination, and planning, but also flexibility, missed shots, and the ability to grab opportunities as they appear. That elk you are after (or mushroom, if you dislike the idea of hunting for an animal) may appear in places that you never expected. Your Hunting Plan will therefore be a living document that will develop as your project proceeds.

It is a ‘hunting’ plan for a reason, let´s see the youtube video.

Aim
Create one Hunting Plan that will guide your activities from now until the delivery of the final product.

Deliverables
The complete Hunting Plan in a suitable format of your choice.
First Spring SGM presentation

DL
28- 04 - 2023

When working with uncertainty, the content of milestones and deadlines may change as you discover new things along the way. The trick will be to know when to persistently stick to the plan and instead make reality fit your plans, and when to change your plans because reality will not change. Sometimes it may be necessary not to meet the deadline in order to produce quality, but it will have consequences. A plan will help you foresee the consequences of your delay and make informed choices. If Module A takes one week extra to develop for example, how will you cut development time of Module B or C? Or will you cut Module C from your solution? In addition, when development is done in geographically distributed teams, it is a challenge to keep everyone informed and updated, and make sure you are actually working towards the same vision. From now on, you will therefore end each week by updating your common Hunting Plan.

6.1 The Solution System Vision Format

Find a good format (text, picture, animation, CAD...) to describe the vision towards which you will be working.

It should be:
(1) quick to take in and understand as a whole
(2) easy to update
(3) give the possibility to access further details if necessary.

We will need to understand why the world needs your system, who needs it more particularly, and how we know that is the case.

We will also need to understand the functions your system will have, as well as the forms you will create to achieve them. What requirements will your system have as a whole, what requirements will your system elements and interfaces have, and how will you verify that your solution works? What are the prioritized and necessary parts of your solution and what are things that would be nice to have? We refer to the figure below as the ‘Green Ugly One’, but it should provide an overview of things to consider.

Here is an example from a previous year of what a finished version may look like.

On the buttons below you can find an editable format in Miro that you can use.

Miro PYMES

Miro AGRO

6.2 The master plan

From Mission 6.1 we know ‘what’ we want to achieve. In this mission, we will focus on ‘how’, ‘when’, and ‘who’. By the time you get to EXPE/EXPO, there should be a Prototype, but there should also be a Presentation, a Booth, Documentation, and all sorts of Printed Stuff. Although you know what you want to do, there is a danger to underestimate what it will take to get there. You may also need to prioritize. We, therefore, ask you to create a plan. In your plan, you should define processes when they will start and end, and assign people to be responsible. To create the plan, you need to ask yourselves a bunch of questions.

This is an example of the things that each part of the final phase has, think about it and about the plan to get done!.

Questions about the Deliverables

How will you realize the prototype? What are the pieces that will need to be created? How will they be made? What kind of capabilities and skills do you have in the team? Are there parts that need to be manufactured elsewhere? How long will that take? How much will it cost? What kind of material will you need to buy? How long will it take to have it delivered? If your solution requires software, what are the software elements that will be required? Who is going to produce them? What interface elements? What communications network elements? How will you meet your requirements? What kind of testing will you be doing and when? Will your Core User Testing-Group (see Mission 5) be enough or will you need to extend your group?

How will you present your solution at EXPE? Will you need film clips? How long will it take to produce those? When do you start creating the storyline? What will your Booth look like? What do you need to buy and how much will it cost? What will you need to prepare before you go and what can you produce on location? What kind of story will it be telling and what kind of experience will you offer? What kind of Printed stuff will you need for your booth? How long will it take to produce it? How far in advance do you need to finish it all in order to have time for feedback and revisions? What part of Documentation will you finish continuously and what are parts that have to be prepared at the end? Who will proofread? These are just some of the relevant questions.

Questions about ORGANIZATION

How will you structure your work? How will you make sure you keep an overview without creating information overload? How will you know that pieces and modules will fit together in the end? How will you keep people updated? In what format will you update each other? How will you strategically use the competences that you have and what new competences will you need to develop to make this work? How will you make decisions? Who can make decisions and when? Is there a difference between a ‘decision’ and a ‘choice’? Can for example the creators of a module change requirements if necessary? What does it mean to be ‘responsible’ for a certain part? What happens if you disagree? When is voting a good procedure and when is it a bad one? How often do you need to communicate? What type of communication will be necessary? When you do handovers, what format will they have? How long response time is ok if you send a WhatsApp message? An email? Is it ever ok to call in the middle of the night and expect an answer? How will you give each other feedback and when? What are tasks that are good to do in diverse teams and what are tasks that are better done in homogeneous teams? These are just some of the organizational questions.

-Missions content shared by LIU University-

Page updated

Google Sites

Report abuse