here's the presentation I gave at Enterprise 2.0 this morning. The slides are a little sparse. I'll write up some notes on my blog (disambiguity,com) as soon as I get a spare moment.

1. Social Project
Management
Everything small is big again
Leisa Reichelt
Flow Interactive

2. who are we?

3. a tiny bit about me

4. what are we talking about?

5. so... social project
management, eh?

6. why is this interesting?

7. the ‘social’ revolution

8. changing the way we do
many things

9. a new way of
‘doing’ projects...

10. well... not really new...

11. ...it’s just that they’re
being taken a lot more
seriously these days.

12. limited planning
no documentation
do it yourself (small team)
multiple skillsets
small budget
release ASAP

13. what was once a hack,
is now an accepted
methodology

14. project management 2.0?

15. social project management

16. [project management]?

17. what does
project management 2.0
look like?

18. small teams

19. smart, motivated people

20. limited planning

21. a clear vision

22. minimal scope

23. small projects

24. multi-skilled teams

25. fast pace

26. rapid release

27. alpha

28. beta

29. feedback

30. responsiveness

31. iteration

32. is this really so new?

33. but, there are
not-so-new
alternatives...

34. agile

35. Manifesto for Agile Software Development
We are uncovering better ways of developing software by
doing it and helping others do it. Through this work we have
come to value:
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
That is, while there is value in the items on the right, we
value the items on the left more.
www.agilemanifesto.org

36. short development cycles,
iteration,
end user involvement,
multi-disciplinary teams

37. compare & contrast with
‘project management 1.0’

38. large scale projects

39. top down

40. Gantt charts

42. many stakeholders

43. escalating requirements

44. complex dependencies

45. risk registers

46. mammoth teams

47. scary/crazy budgets

48. horizon & beyond
timelines

49. expected failure.

50. why do these types of
project fail?

51. firstly. do they fail?

52. Oracle, PeopleSoft,
SAP, Accenture,
IBM Global Services

53. the 1.0 ‘large scale’, top
down project approach
fails spectacularly.
All the time.

54. except, they don’t
*officially* fail. Because
we update the Gantt
chart as we go. We
move the goal posts

55. but why?

58. traditional project
management doesn’t
match the way we work.

59. war story

60. project management 2.0
projects *also* fail
all the time.

61. for different reasons...

62. usually because it just
wasn’t such a great idea.

63. or the implementation
was completely wrong

64. or the audience doesn’t
exist yet.

65. but it doesn’t matter.

66. because they’re
smaller and faster.
there’s less invested.

67. dust off.
take the learning.
move on.

68. ok.
so what’s all this social
stuff got to do with it?

71. new toys

74. but, will it scale?

75. creating a composite

76. a recent war story

77. old principles
new principles

78. the take home lesson

79. want to share your
thoughts or experience?
thank you :)
leisa reichelt
leisa.reichelt@gmail.com
blog: disambiguity.com
work: flow-interactive.com

80. image credits
Gantt Chart image:
http://www.conceptdraw.com/products/img/ScreenShots/project/gantt_chart_presentation.gif
How waterfall doesn’t fit the way we work
images taken my me, of Johnnie Moore’s presentation at Reboot 9.0 (johnniemoore.com)
Org. chart:
http://www.pipingdesigners.com/Tips/org%20chart.JPG
Happy Project Team:
http://flickr.com/photos/grazi/204789193/