1. Project debriefing Hoorcollege 25 November 2010

2. What is a debriefing? A written summary of the briefing from the client Purpose – A check to ensure you understood the project request from the client – You can use it to check your understanding with the client Send it to the teamcoach and ask for feedback – This prevents too much time being wasted on misunderstandings – It is a document to inform your team what the client is looking for They may not have been at the briefing! – Writing the document will focus you on the key areas that need to be considered in the project

3. Debriefing process

4. Orientation phase Market orientation – Client – Partners – Suppliers – Intermediaries – Competitors – Other stakeholders – Customers Target group Clarification / questions – Never assume, if in doubt ask! But not always the customer, first the teamcoach!

5. Some commercial questions I have asked What is the purpose of the product? What is wrong with the current situation? What results would have to be achieved for the product to be seen as a success What are the start and end points?

6. Questions about creative requirements I have asked What are product values the product should support? Are there any competitor sites that need to be considered? Does the client have any interactive media (websites, etc.) they like or dislike? What are the rules for the look and feel of the product? What is the tone of voice of the product?

7. Some technical requirements questions I have asked What infrastructure do they use? – Database version Where is the site hosted? – What type of server? Are there security considerations? Who will maintain the product? What sort of machine does the user have?

8. Debriefing Contents – Inleiding – Doelstelling – Opdracht – Succesindicatoren – Kansen –Concurrenten / Partners –Taakverdeling –Teamidentiteit: Huisstijl en visitekaartje – Contactpersoon

9. Inleiding A short explanation of the document – What is it? – What is the purpose of the document – The structure (only for longer documents)

10. Doelstellingen The project objectives (or goals) – What problem is it trying to solve – What should the project try to achieve? 1.Clearly state the problem – How can...? 2.Clarify the objectives – These will be in the briefing but not always clearly stated

11. Stating the problem A bit of research is good at this point This is important as it will guide you to a solution – The wrong problem = the wrong solution! Keep it neutral and open – Don’t suggest the solution in the problem Keep it short Make sure it is a problem – How can…?

12. Clarify the objecIves What does the client want to achieve? – Not always clear in the briefing – MUST be clear in the debriefing! Keep them neutral – Do not suggest the solution Keep them SMART

13. SMART (SMURT) objectives S pecific (Specifiek) M easurable (Meetbaar) A chievable (Uitvoerbaar?) R elevant (Relevant) T ime-based (Tijdverbonden)

14. Every single objective must be SMART Example: We will develop an interactive application by end of April 2010 that allows the chosen target group to access the museum’s archive from any location in The Netherlands – This is SMART

15. Not one objective per letter of SMART S – We will build a game for client x M – It will have 10000 visitors per month A – We will have satisfied customers R – The client will be happy T – It will be ready by 08/4/11

16. Opdracht A short summary in your own words of what the client has asked you to do. – Aim for 2 or 3 sentences Good to clarify in your own mind Good to help communicate with other about the project

17. Succesindicatoren What has to happen for the client and you to feel the project has been a success? – Linked to your SMART objectives Make sure you have your own vision as a team as to what will be a success Over-deliver never over-promise!

18. Kansen What are the opportunities that you see for this project? – For the client – For you as a team Think about things like: – Innovation, learning, new contacts, etc., etc.

19. Debriefing process