Social Project Management

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

Slide 2: who are we?

Slide 3: a tiny bit about me

Slide 4: what are we talking about?

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

Slide 6: why is this interesting?

Slide 7: the ‘social’ revolution

Slide 8: changing the way we do many things

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

Slide 10: well... not really new...

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

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

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

Slide 14: project management 2.0?

Slide 15: social project management

Slide 16: [project management]?

Slide 17: what does project management 2.0 look like?

Slide 18: small teams

Slide 19: smart, motivated people

Slide 20: limited planning

Slide 21: a clear vision

Slide 22: minimal scope

Slide 23: small projects

Slide 24: multi-skilled teams

Slide 25: fast pace

Slide 26: rapid release

Slide 27: alpha

Slide 28: beta

Slide 29: feedback

Slide 30: responsiveness

Slide 31: iteration

Slide 32: is this really so new?

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

Slide 34: agile

Slide 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

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

Slide 37: compare & contrast with ‘project management 1.0’

Slide 38: large scale projects

Slide 39: top down

Slide 40: Gantt charts

Slide 42: many stakeholders

Slide 43: escalating requirements

Slide 44: complex dependencies

Slide 45: risk registers

Slide 46: mammoth teams

Slide 47: scary/crazy budgets

Slide 48: horizon & beyond timelines

Slide 49: expected failure.

Slide 50: why do these types of project fail?

Slide 51: firstly. do they fail?

Slide 52: Oracle, PeopleSoft, SAP, Accenture, IBM Global Services

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

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

Slide 55: but why?

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

Slide 59: war story

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

Slide 61: for different reasons...

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

Slide 63: or the implementation was completely wrong

Slide 64: or the audience doesn’t exist yet.

Slide 65: but it doesn’t matter.

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

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

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

Slide 71: new toys

Slide 74: but, will it scale?

Slide 75: creating a composite

Slide 76: a recent war story

Slide 77: old principles new principles

Slide 78: the take home lesson

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

Slide 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/