Project Management 2.0 an agile approach to manage web projects . Francesco Fullone, Ideato.it ff AT ideato.it

Who am I Francesco Fullone aka Fullo - PHP developer since 1999 - GrUSP President - PHP and Open Source Evangelist - CEO @ - Nerd and geek

Part 1: Where we introduce the Project Managment

Project Management anyone?

Project Management anyone? The two golden rules of a PM.

If something can go wrong it will . -- Murphy's Law

Find good people and set them free to do their job.

The real world is not that easy .

Project management practices are a jungle .

R.U.P. (rational unified process)

AKA: Follow the rules!

Agile.

AKA: Listen to the team.

Lean .

AKA: If you don't need it, remove it.

Kanban .

AKA: What's next?

Total Quality Control .

PERT/CPM.

GTD.

Pomodoro Technique.

...

The best practice doesn't exist.

BUT

You should iterate on some good practices to find the best PM approach for your project!

Part 2: Being Agile , means not...

The Agile Manifesto

It is based on some principles .

Individuals and interactions over processes and tools.

Customer collaboration over contract negotiation.

Working software over comprehensive documentation.

Responding to change over following a plan.

That means ...

Being agile doesn't mean being a juggler . Individuals and interactions over processes and tools.

Good processes are always welcomed !

One tool for one task, don't create noise in your work.

Collaborating with customer means not to be his lover . Customer collaboration over contract negotiation.

Don't be afraid to say NO!

The customer is part of the team don't hide informations and motivate your choices.

Stop asking for story points .

Story points € ----------------- = -------------- ? Time Iteration

NO!

Story points are used to create metrics , after a release, not invoices .

Embrace the changes, not the caos . Embrace the change over following plan

Focus on application business , don't change your mind too often.

But write at least the installation guide! Working software over comprehensive documentation

Part 3: Where actors show themselves.

We intended the PM as the management of different actors with their own tasks .

In a (web) project there are many people .

Developers

UX / AI Designer

Marketing

Product owners

Any 2.0 unpaid job

Anyone has different needs .

All of them have to communicate those needs to other members of the team.

And to fulfill these needs there are also a lot of different tools .

Part 4: Where tools are introduced.

On internet you can find lot of PM verticalized tools.

BaseCamp .

Easy, with a lot of features to communicate , nothing to do the real work .

SourceForge .

Many tools to manage a community , nothing to manage a budget.

Assembla .

Some “ agile nuts and bolts ” but only for SaaS.

Microsoft Project.

Gantt and resources management but nothing to open an issue with a customer.

Choosing the wrong tool should create problems to the team.

Tools have to help any kind of actor to do its jobs with the less effort.

ie. SVN integrated with a Bug Tracker to close automatically issues.

ie. Online documents revision tool to help web writers.

Start your project with easiest (and unobstrusive) tool and then enhance it if needed .

The best tools are you and your team .

?

Francesco Fullone ff AT ideato.it skype: ffullone via Quinto Bucci 205 47023 Cesena (FC) info AT ideato.it www.ideato.it