Anders Ödman

RUP experiences from the TOP-OM project

Anders ÖdmanProject Support Office

Anders Ödman

What is TOP?

TOP stands for Truck Order Process, but covers all activities from the first contact between a Salesman and his Customer until the truck has been delivered to the Customer.

Contact prospect

Delivery

Send order

Create Order

Presentquotation

Preparequote

Plannedactivities

Define customer

needsValuate trade in

Set salesstrategy

Order change

Pricing

Follow updelivery

This is described as the Sales to Order and the Order to Delivery processes.

TOP contains a number of system-modules that supports these processes, all presented to the user through one common Web-interface.

No deal

Anders Ödman

The OM project…

History…

Organisation…

Pre-study…

Customer…

Iterative work and RUP…

Anders Ödman

Iterative work and RUP

We started with an extensive method support- which did not work!

the timing was all wrongthe project group was not preparedthe method support model was not designed for this type of task

We made a tailored Development Case (with method support)- which was very good and has been used since then focused the team on the correct artifacts and their content

We made en extensive RO modelling-which was extremly helpful

form the basis for the Project Schedule and the Iteration Plans

Anders Ödman

We had to re-work the Use cases (to much design issues included/structure wrong)-this was maybe a good thing?

Caused a lot of uproar in the team (among analysts)Took huge resource from team and customerAnalysis (with designers was not performed in conjunction with Req. work)We lost info for analysis & designShowed that RUP was not deeply grounded in the teamClean nice (but huge) Use Cases

We used an Acceptance Board by the customer to ”freeze” the requirements-this was a nice idea!

Put focus on demands Forced the customer to decisions (sometimes) Did not clarified the requirements deeply enough Sometimes affected the Schedule Sometimes opened up for “blame on the others”

Anders Ödman

Project PlanTOP-OM1/11 15/12 15/2 -02 1/4 15/5 30/6

DeliveryA

DeliveryB

Req.

A&D

Impl.

Test

Depl.

BMReq.

A&D

Impl.

Test

Depl.

Inception/Elaboration

G2 G3 G4

PMEnv.SuppConf&CM

G1 G2 G3 G4

Iteration 4 Iteration 5 Iteration 6 Iteration 7 Iteration 8

Elab

Const

Trans

Anders Ödman

We worked strictly with Iterations (6 weeks, now 10 iterations)- worked out well

We tried to put to much into each iteration

Was more schedule driven than content driven

Problems finding the correct scope for each iteration (what is main flow?)

The Use Cases was to large “to fit”

No common understanding of what an iteration is and how it works

The customer and Program manager expected an externally executable release? out from each iteration

Still the only way to success!

Anders Ödman

Harder and much more planning work!ongoing planningdynamic planningreplanning

Easier and more correctProgressiveRisk basedshort termajustablemore visible

Develop the Iteration Plans

1/ Determine the iteration scope2/ Define evaluation criteria3/ Define iteration activities4/ Assign responsibilities

Use the Development Case asreference list for activities

Anders Ödman

Lessons learned

RUP works as a common languageThe project team needs good education and an understandingProject Management must understand the fundamentals behind.

RUP is a supporting tool/method – not a quick way to success!Project Management must use it wiselyIt will take a lot of extra effort (the first time) for managementBut it is worth it for the team

RUP is ”Six best practises” – must be tailored

RUP changes its face during the various phases of the projectIn Construction RUP is very much Iterative work

RUP could not be left to the methodologist! – you must take in on by yourself

Anders Ödman

Thank you!