100330 Scrum Lord Of The Rings Print

2010 Proyectalis Gestión de Proyectos S.L. Imágenes © 2001–2003 New Line Productions

Scrum & Agile Development Santiago, March 2010


Ángel Medinilla Telco Guy - cable, radio & ISP /

portals 13 years in IT, 11 as a Project

Manager Entrepreneur, blogger Aikido, Motorbikes, WoW,

books, cooking, wines, music, travel, comics,movies…

Certified Scrum Master - Scrum Alliance Member, Agile Spain co-founder, PMI member

[email protected] http://twitter.com/angel_m

http://es.linkedin.com/in/angelm



ICT Project Management Consulting

Our Mission Statement is: improve your project results!


Our Business is to create

differences…


…and improve your competitive advantage


Some references


Enough about us…


An introduction to Scrum and Agile Development

(Wilkins, stop passing notes…)


Introducing…


The Lord I want it yesterday

Those 20 changes were agreed as free

That’s not what I wanted

This was supposed to be included

Dunno’ what I need, just send me a proposal


The poor guys

That sucks!


The things

¡Grunt!

Me compatible IE6!

Me only talk cobol

Me want bunch two dot zero


Fill you time sheets The

project manager

Client wants it yesterday

Client wants 20 free changes

I need a performance report

Try harder!

It won’t take more than two days… This is not what

client wanted

This was wupposed to be included


We need to end the tyranny of process

The Wizard

We need to build quality into the process

We have to end technical debt

We must learn new technologies

We must improve team’s life


¡Ooops! Probable Copyright Infringement…

Cool down guys, it’s for a good reason

Peew, thanks Mr. Jackson


In the beginnings Coders are indisciplined and disorganized. I will create One Methodology to bind them all in the Darkness


In the beginning…

Maybe we’ll drop one more just to cause some confusion.

Prince2:


In the beginning…

Mmm… Just a bit more…

PMBOK


In the beginning…

Eeeh… Just a bit more…

CMMI-ITIL:


In the beggining… Ok, serious, we’ll drop one more just in case… Can’t have enough control, can you?

MétricaV3


For eons…

Software projects are filled with chaos, BWAA-HAHAHAH!

Exceeded schedules

Overbudget

Angry clients

Unwanted functionality


Revolution! Something has to change. We must end the Tyranny of Waterfall and the belief in "everyone does it" and "you must comply, try harder"

We must analyze the problem we face and propose realistic solutions

We must find the sustainable pace and be better than our competitors so we can defend our models


First problem

After six months of coding you bring me something that’s not what I wanted!!!


First problem

Although the document wasn't quite specific in some points...

We did what the document said

We had to guess

Maybe there were some little misunderstandings

Client was not available to clarify


Wrong strategy

We need more documents ¡OMG!


Solution Developers and business people must work together side by side througout the project

Let’s make small increments and show our product to the client so we can detect deviations

Client will explain himself better over a working product than over a written document


Agile Manifesto


Second problem:

I want everything and I want it NOW!!!!

Live


Second problem

We are switching context all of the time

We can’t do two things at the same time

We don’t even know were to start

Priorities are always changing


Solution One person can only do one thing at the time. Let's concentrate on doing the most important part right as fast as possible, THEN, change to the next most important thing.


Solución In other words: Everyone to Helm’s Deep!


Third problem:

I want to make some changes


Third Problem:

It will damage our architecture

Changes are bad, are bad, are bad, are bad, are bad, are bad, mumblemumble…

Client doesn’t know what he wants

Changes are expensive and delay the project


Wrong strategy

No problem, we have Change Management

Use the form A-21 about changes suggestions to allow our analist to determine the impact, generating the report E-37. Once is approved it will generate the design form F-56 and additional budget with code Hobbiton-Elrond-Rohan. It will be sent to the client for a validation of the budget deviation, included on the analytic accountantability of the project and in the list of deviations on the base line, as well as on the lessons learned registry and in the risk databases…


Wrong strategy:

????????????


Solution Any part of the project that hasn't been initiated can still be changed for one of similar complexity.


Solution Our development will be ITERATIVE and INCREMENTAL

1 2 3

1 2 3


Solution But I can’t wait for next iteration, I need my changes and I need them NOW!!!!

Massteeer wants nooow, my preciousssssss…


Solution If we interrupt the team during an iteration, we break the pace and concentration, lose productivity, generate technical debt…WAIT until the next iteration.If needed, we can make shorter iterations

Defend the team!


Fourth Problem

Yep, but there’s never enough time

We could be better. We could learn, research, make new tools, refactor...

Not enough time, not enough time, not enough time,, mumblemumblemumble…

We always come to the same mistakes

“Someone should” make some things…


Solution CONTINUOUS IMPROVEMENT is vital. At regular intervals, the team should think about how to be more effective and productive.This is good both for the team and for the client


Fifth Problem

I need my reports!

How wll I assign costs to the project?

How will I know if something is going wrong?

What do I tell the client during iteration?


Fifth Problem

In fact I guess them up on friday afternoons…

We are sick of making reports and filling project time sheets

Should we code or make reports?

We spend our lives on meetings…


Solution This has to work for everyone or it will be eliminated. We will report daily to the Project Manager, in a daily sinchronization meeting

Yesterday I found the One Ring, and today I'll bring it to Mordor. My main impediment is an army of Orcs...


Solution To avoid reporting constantly, we'll keep SIMPLE tools of visual management. That way, in a single look we can get the global state of the project.

Jeff Sutherland @ Google!


In other words…

SCRUM


In other words…

Retrospective


Some guys doing Scrum out there


What do Agile enterprises use?

2nd Annual ”State of Agilee Development”

Survey Jun-Jul 2007

3rd Annual ”State of Agile Development” Survey Jun-Jul 2008


Ten Commandments of Scrum 1. People 2. No silver bullet 3. Retrospectives, retrospectives, retropectives 4. Daily Scum, daily management 5. Progress = functional product (measure what’s left, not what

we’ve done) 6. Self management of the team, abandon command & control 7. Iterative & Incremental developmen 8. Only team manages Sprint Backloj, Only product owner

manages product backlog 9. Fixed duration for sprints 10. Define “done, done”


Pending Dev. Test Done Story Project:

Team: Scrum, Demo:

Burn-down::

Release Plan:

Impediments:


And in our next speech…


Questions?

[email protected]


Thank you!

[email protected]

100330 Scrum Lord Of The Rings Print

Business

jackson imgenes

notes imgenes

cominangelm imgenes

morepmbok imgenes

differences imgenes

references imgenes

darkness imgenes

mtricav3 imgenes