Skip to content

Latest commit

 

History

History
53 lines (40 loc) · 2.57 KB

core_presentation.md

File metadata and controls

53 lines (40 loc) · 2.57 KB
Raw

Core Project Presentations

In order to increase the continuous learning of our team, and provide fodder for our marketing, we encourage Core Project Presentations

At this point, there is no Template for such a presentation, but it should include the following:

NOTE: Total presentation should be between 50 minutes and 90 minutes. Depending on the project, more time may be spent in one section than the other, but each should be considered. The questions/bullets listed below each topic are considered fodder for things to consider in preparing a presentation, not a checklist of everything that needs to be covered.

Quick History and Context (5-10 minutes)

  • What was the motivation for initiating the project?
  • What is the hypothesis we’re trying to prove?
  • What was done before the current phase?
    • If in the Craftsmanship Phase, what was done in the Planning & Exploration Phases
    • If this is a continuation of a previous project, what was done in the previous project and what was done between projects
  • Who have the players been (and who are they currently)?

Customer Value Add (10-20 minutes)

  • What have we delivered to the customer?
    • Demonstration of how it works (or what it looks like in the case of unimplemented design)
    • Other artifacts or summary of things we have done (e.g. usability test with N users) and how it added value
    • If history, what did it look like “iteration 1”, “iteration 2”, …?
  • What is imminent?
  • What is in the near future?
  • What is in the far future?

Technical Value Add (10-20 minutes)

  • Familiar tools
    • Which are working well (and why)?
    • Which are falling short (or we suspected would) and why?
    • How have we improved our use?
  • New(er) tools
    • What problem are we attempting to address with them?
    • Which are working well (and why)?
    • Which are falling short (or we suspected would) and why?
  • What technology challenges are we still facing?
  • What are we doing to overcome these challenges?

Team Value Add (10-20 minutes)

  • What growth were we expecting for each of the team members?
  • What growth have we seen for each of the team members?
  • What have we done to stimulate/nurture that growth?
  • Where did we fall short in stimulating and nurturing that growth?

Q&A (15-30 minutes)

  • Questions you would like to ask the audience to help overcome challenges (2-3)
  • Questions the audience would like to ask you to challenge your assumptions
  • Questions the audience would like to ask you to help apply what you have learned/accomplished to help them continuously improve