Project Management is more than Todo Lists

Transcript

1. Project Management is More than Todo Lists D. Keith Casey, Jr @caseysoftware
2. So.. who are you? • D. Keith Casey, Jr • Chief Stuff Breaker, Blue Parabola • I break stuff with the underlying goal of understanding and making things better • All over the community.. formerly DCPHP, ZendCon, etc, now AustinPHP, Austin NoSQL • Web2project Head Custodian • HubAustin Co-founder
3. What is Proj Mgmt? Making sure things get done*, hopefully: on time, on specifications, and on budget * we're assuming “things” == “what you wanted”
4. Todo List - spelling Todo List ? To Do List? TODO List? Whatever. Stop bikeshedding.
5. Basecamp
6. Task Lists!
7. Gantt Charts!?
8. Tasks and Todo lists are just the most visible & obvious pieces..
9. Projects are made of people
10. Projects are made of people
11. Ditch the spreadsheets Use Psychology
12. Maslow's Hierarchy of Needs Obligatory Wikipedia Link: http://en.wikipedia.org/wiki/Maslow's_hierarchy_of_needs
13. (Not going to touch those) Obligatory Wikipedia Link: http://en.wikipedia.org/wiki/Maslow's_hierarchy_of_needs
14. The important ones Obligatory Wikipedia Link: http://en.wikipedia.org/wiki/Maslow's_hierarchy_of_needs
15. Web2project's principles • Regular and predictable releases are vital to the health of the community, we should have at least two each year; • Bugs and feature requests should be reviewed, evaluated, and prioritized regularly; • Frequently Asked Questions should be considered indicators on where we should simplify or clarify the system; • The community should be open with clear expectations for behavior while encouraging constructive criticism; and • Features and functionality should be driven primarily by input and involvement from the community.
16. Achieve.. Regular and predictable releases are vital to the health of the community, we should have at least two each year
17. Simplify • We have a regular and predictable release cycle – we make a Major Release each year and a Minor Release each quarter • Define the finish line • Be lazy Automate everything
18. Our Releases
19. Research Bugs and feature requests should be reviewed, evaluated, and prioritized regularly
20. Document • Every bug is reviewed, triaged, and categorized according to its own criticality, its dependencies, and the current release • It doesn't count if it's not written down
21. Categorize & Triage - 1
22. Categorize & Triage - 2
23. Categorize & Triage - 3
24. Categorize & Triage - 4
25. Categorize & Triage - 5
26. Feedback • Frequently Asked Questions should be considered indicators on where we should simplify or clarify
27. Communicate • We encourage Code Reviews to get feedback, criticism, and insight that we may not have/discover by ourselves • Only criticize if you can make it better
28. Communicate
29. Participate The community should be open with clear expectations for behavior while encouraging constructive criticism
30. Communicate • We have a formal policy and procedure on how community members are evaluated for possible team membership and the expectations that follow • Set the tone • Our standing offer: beer
31. Membership (Initiation?)
32. Growth Features and functionality should be driven primarily by input and involvement from the community
33. Communicate • Every commit is available in a variety of places – forums, a mailing list, GitHub, and Sourceforge – and most discussions are available to anyone and everyone • Actively solicit feedback – we use RFC's
34. Our Forums
35. Overall.. Eight of eleven key points definitely covered..
36. The Result
37. The Result
38. The Result
39. The Result
40. The Result
41. The Result
42. The Result
43. In Summary.. • Projects have problems • Projects are people • Your people have problems • Project problems are often people problems.. • Change those, change the project
44. Feedback?
45. Contact Info • D. Keith Casey, Jr – keith@blueparabola.com – keith@caseysoftware.com – Skype/Twitter/IRC: • caseysoftware – http://CaseySoftware.com • Projects – http://web2project.net - the best PM app evar! – http://HubAustin – the best South Austin coworking space
46. Resources • Producing Open Source Software – Karl Fogel – http://producingoss.com/ - available under CC • No really, that's it.