Managing Projects Through Metamorphosis
•
1 like•721 views
These are very low-fi slides that accompanied my talk for Head 2008. The aim of my session was to get folks thinking and discussing; I've noticed that on the subject of project/team management, everyone has stories from the trenches, and true to the nature of the problem, there is not one solution. Most of the meat of the talk was during the session and within the session chatroom. Alas, the recording didn't work well, a re-recording hasn't been scheduled. So this is all I have for now!
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Similar to Managing Projects Through Metamorphosis
Similar to Managing Projects Through Metamorphosis (20)
Recently uploaded
Recently uploaded (20)
Managing Projects Through Metamorphosis
- 1. Managing the metamorphosis Stephanie Troeth <head> web conference Saturday, 25th June 2008 London, UK.
- 2. Best web practices: how well do we really do it?
- 3. We know: we can’t just make best practices fit in a project; needs to be part of the game plan and team philosophy.
- 4. But what happens when projects don’t go according to plan?
- 5. It feels a bit like this.
- 6. A project going off the rails
- 7. A project going off the rails amount of work is more than first thought
- 8. A project going off the rails amount of work is more than first thought ... rushing to completion
- 9. A project going off the rails amount of work is more than first thought ... rushing to completion ... compromise of quality
- 10. A project going off the rails amount of work is more than first thought ... rushing to completion ... compromise of quality ... high stress levels
- 11. A project going off the rails amount of work is more than first thought ... rushing to completion ... compromise of quality ... high stress levels ... conflict, lack of team coherence
- 12. A project going off the rails amount of work is more than first thought ... rushing to completion ... compromise of quality ... high stress levels ... conflict, lack of team coherence ... mediocre product.
- 13. Perhaps ...
- 14. Perhaps ... Before we look at incorporating best web practices, we need to first understand how to do web projects well.
- 15. Perhaps ... Before we look at incorporating best web practices, we need to first understand how to do web projects well.
- 16. How do we end up with these problems?
- 17. Key Aspects 1. Process & methodology 2. Project planning 3. Team dynamics
- 18. How should we work? Process & methodology
- 19. Process may not reflect project needs, and is not in fact the saviour.
- 20. The team may or may not have wholly bought into the methodology.
- 21. Not enough time to planned for planning, not enough budget.
- 22. No margin for error.
- 23. What, when and how much? Planning & estimation
- 24. Estimates made based on previous projects. (which were probably wrong)
- 25. Estimates are “set in stone”.
- 26. Inaccurate assumptions made on how complex something actually is to build.
- 27. Optimism: how much time it should take vs how much time it really does.
- 28. No prior resourcing as to who may be available to do the job.
- 29. Too much love for Gantt charts.
- 30. Too much love for software.
- 31. Where’s the love for the people?
- 33. Talking to one another without prejudice.
- 34. Ditching the cogwheel mentality.
- 35. Being proud of what we do Quality as a measure of satisfaction
- 36. Define a vision for quality. Create a thirst for doing good stuff.
- 37. Allowing your team to drive. Passion is fuel.
- 39. Identify how best to achieve team members’ individual accountability.
- 40. Establish a “local” methodology.
- 41. Give your team a sense of pride.
- 42. Thank you :)
- 43. Questions?