1.
Project Management As a series of questions

2.
Obviously this isn't full project management.. we only have a few minutes! <ul><li> </li></ul><ul><li> </li></ul><ul><li> </li></ul><ul><li> </li></ul><ul><li>&quot;Project management is too by the book&quot; </li></ul><ul><li>&quot;Our projects are too simple&quot; </li></ul><ul><li> </li></ul>

3.
Use a PM mindset anyway! <ul><li>PM can be as simple as the task </li></ul><ul><li> </li></ul><ul><li> </li></ul><ul><li> </li></ul><ul><li>You'll get more done </li></ul><ul><li> </li></ul><ul><li>The product will be more useful, and you'll be able to prove it. </li></ul>

4.
Purpose and Outcomes <ul><li>Touchstone has been trained as a culture to not hold a meeting without Purpose and Outcomes, ... even our emails. </li></ul><ul><li>But our projects DON'T !!!! </li></ul><ul><li>( Do our meetings anymore ?) </li></ul>

5.
Get in the habit of asking these questions <ul><li> </li></ul><ul><li>FIRST AND FOREMOST </li></ul><ul><li> </li></ul><ul><li> </li></ul><ul><li>Everything should be for a reason </li></ul><ul><li>That reason should be written down somewhere , e.g., scope requirements </li></ul><ul><li>Each step explains the one that follows. </li></ul>

6.
Problem Definition Phase - or now <ul><li>What's the problem? </li></ul><ul><li>(not world hunger, but the problem you plan to address) </li></ul>

7.
Vision, Scope phase - or now <ul><li>What's the solution? </li></ul><ul><li> </li></ul><ul><li>Is that description narrow enough so we can actually work on something? </li></ul><ul><li> </li></ul><ul><li>Is creating this solution the best way WE can tackle the problem? </li></ul><ul><li> </li></ul><ul><li>(Is it our sweetspot?) </li></ul>

8.
Vision, Scope phase - or now <ul><li> </li></ul><ul><li>What's out there NOW? </li></ul><ul><li>How is this better? </li></ul><ul><li> </li></ul>

9.
Vision, Scope phase for documents <ul><li> </li></ul><ul><li>Problem and solution apply here as well </li></ul><ul><li> </li></ul><ul><li>Who is the audience? </li></ul><ul><li> </li></ul><ul><li>Is that a narrow enough description to really help create the document and make editorial decisions? </li></ul><ul><li> </li></ul><ul><li>What will they do with this? </li></ul><ul><li> </li></ul><ul><li>Should we deliver two or three documents.. a web page, an email? </li></ul>

10.
Case study <ul><li>P25? </li></ul><ul><li> </li></ul><ul><li>Document was as long as 35 pages of technical information for the layperson and as short as a trifold.... months of work by 3-4 people full time. Think of the cost. </li></ul>

11.
When listening to the description of the solution.... <ul><li> </li></ul><ul><li>&quot;Why?&quot; </li></ul><ul><li>Is the relationship between the solution and the problem obvious? This is the heart of your business case... your elevator pitch </li></ul><ul><li> </li></ul>

12.
Requirements phase - or now <ul><li>What's the check list that tells us we've finished the solution? </li></ul><ul><li>...That the solution will address the problem and not other problems? </li></ul><ul><li>And drive this list with the client.... </li></ul><ul><li>&quot;So if it, [or I, or the document] checks each of these, you will be happy?&quot; </li></ul>

13.
When building the requirements <ul><li> </li></ul><ul><li>&quot;So that...?&quot; </li></ul><ul><li>They will pile on. Resist with your scope. </li></ul><ul><li> </li></ul><ul><li> </li></ul><ul><li> </li></ul><ul><li> </li></ul>

14.
Work breakdown <ul><li>What are the project parts , milestones, intermediate deliverables like outlines? </li></ul><ul><li>Are these fine enough so you don't need to discuss parts at a deeper level? </li></ul><ul><li>Are these frequent enough so the parties will know they're on the same page? </li></ul>

15.
Day to Day <ul><li>What are you working on? </li></ul><ul><li> </li></ul><ul><li>Does what your working on fill a requirement? </li></ul><ul><li>Do you have even a simple wall chart, roadmap, or do you have to decide every day? </li></ul>

16.
Day to Day <ul><li>Do we have too many status meetings? </li></ul><ul><li> If a lot of information is being revealed, then the project isn't well planned or managed. </li></ul>

17.
Day to Day <ul><li>New ideas, interruptions, come up..... Do you want to change the schedule, requirements, scope, milestone? </li></ul>

18.
Finally... are you done? Delivery, Pilot <ul><li>Does what we're delivering meet the requirements? </li></ul><ul><li> </li></ul><ul><li>Is it in scope? </li></ul><ul><li> </li></ul><ul><li>Does it address the problem? </li></ul>

19.
Repeat <ul><li> </li></ul>