Social Project Management

Social Project ManagementEverything small is big again

Leisa ReicheltFlow Interactive

who are we?

a tiny bit about me

what are we talking about?

so... social project management, eh?

why is this interesting?

the ‘social’ revolution

changing the way we do many things

a new way of ‘doing’ projects...

well... not really new...

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

limited planningno documentation

do it yourself (small team)multiple skillsets

small budgetrelease ASAP

what was once a hack, is now an accepted

methodology

project management 2.0?

social project management

[project management]?

what does project management 2.0

look like?

small teams

smart, motivated people

limited planning

a clear vision

minimal scope

small projects

multi-skilled teams

fast pace

rapid release

alpha

beta

feedback

responsiveness

iteration

is this really so new?

but, there are not-so-new

alternatives...

agile

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 toolsWorking software over comprehensive documentationCustomer collaboration over contract negotiationResponding 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

short development cycles,iteration,

end user involvement, multi-disciplinary teams

compare & contrast with‘project management 1.0’

large scale projects

top down

Gantt charts

many stakeholders

escalating requirements

complex dependencies

risk registers

mammoth teams

scary/crazy budgets

horizon & beyond timelines

expected failure.

why do these types of project fail?

firstly. do they fail?

Oracle, PeopleSoft, SAP, Accenture,

IBM Global Services

the 1.0 ‘large scale’, top down project approach

fails spectacularly. All the time.

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

but why?

traditional project management doesn’t

match the way we work.

war story

project management 2.0 projects *also* fail

all the time.

for different reasons...

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

or the implementation was completely wrong

or the audience doesn’t exist yet.

but it doesn’t matter.

because they’re smaller and faster.

there’s less invested.

dust off. take the learning.

move on.

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

new toys

but, will it scale?

creating a composite

a recent war story

old principlesnew principles

the take home lesson

want to share yourthoughts or experience?

thank you :)leisa reichelt

leisa.reichelt@gmail.comblog: disambiguity.com

work: flow-interactive.com

image creditsGantt Chart image:http://www.conceptdraw.com/products/img/ScreenShots/project/gantt_chart_presentation.gif

How waterfall doesn’t fit the way we workimages 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/