larus 10th - enrico de benetti

Larus Business Automation s.r.l.

METHODOLOGYAgile, we mean!

METHODOLOGY: Agile, we mean!TYPICAL PROBLEMS WE MEET DURING

THE MANAGEMENT OF A PROJECT

34,4%

45,6%

20,0%

“The CHAOS Chronicles”, The Standish Group



THEY CONSIDERED UNSUCCESSFUL BECAUSE OF :

● Budget overrun of 189 %

● Overshooting the planned work 220 %

● Only 61% of the features is released





● Objectives unarticulated and not very feasible

● Incorrect estimates of resources needed

● System requirements are poorly defined

● Little information on the status of the project

● Risks unmanaged

● Poor communication between customers, developers and users




● Using technologies unevolved

● Inability to deal with the complexity of the project

● Development practices inadequate

● Low capacity in project management

● Policy adopted by the stakeholders involved in the project

● Commercial pressures



MOST PROJECT HAS ONE SCOPE TOO BROAD


METHODOLOGY: Agile, we mean!THE BUSINESS VALUE

REDUCING WASTE IS THE ONLY AND BIGGEST OPPORTUNITYTO REDUCE COSTS

METHODOLOGY: Agile, we mean!THE BUSINESS VALUE

THE BUSINESS VALUE REDUCING WASTE IS THE ONLY AND BIGGEST OPPORTUNITY

TO REDUCE COSTS

METHODOLOGY: Agile, we mean!

THE BUSINESS VALUE REDUCING WASTE IS THE ONLY AND BIGGEST OPPORTUNITY

TO REDUCE COSTS

“People rarely have time to make the use casesformal, complete, and pretty. They usually only havetime to make them 'sufficient'. Sufficient is fine. It is

all that is necessary.”

ALISTAIR COCKBURN


PRESCRIPTIVE: the waterfall method attaches a requirement and you decide the number of resources to be used and the time available for fulfill this requirement.

ADAPTIVE: the agile method ( not a prescriptive method ) reverses this concept : you tighten the resources and time and decide how many and which implement functionality for the customer , dividing possibly in smaller modules.

METHODOLOGY: Agile, we mean!WHAT APPROACH TO ADOPT

WHAT APPROACH TO ADOPT METHODOLOGY: Agile, we mean!

METHODOLOGY: Agile, we mean!SUCCESS FACTORS FOR PROJECTS


CLEARBUSINESSOBJECTIVES

SUCCESS FACTORS FOR PROJECTS

EXECUTIVESUPPORT




EXECUTIVESUPPORT

USERINVOLVEMENT




MANIFESTO FOR AGILE SOFTWARE DEVELOPMENT

individuals and interactions over processes and tools

working software over comprehensive documentation

customer 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


http://www.agilemanifesto.org/

1) Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.

2) Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.

3) Deliver working so ftware frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.

4) Business people and developers must work together daily throughout the project.

5) Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.

6) The most eficient and efective method of conveying information to and within a development team is face-to-face conversation.

7) Working software is the primary measure of progress.

8) Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.

9) Continuous attention to technical excellence and good design enhances agility.

10) Simplicity -- the art of maximizing the amount of work not done -- is essential.

11) The best architectures, requirements, and designs emerge from self-organizing teams.

12) At regular intervals, the team reflects on how to become more efective, then tunes and adjusts its behavior accordingly.

METHODOLOGY: Agile, we mean!MANIFESTO FOR AGILE SOFTWARE DEVELOPMENT

TRANSPARENCY INSPECTION


ADAPTION

EMPIRICAL PROCESS CONTROL

2 Backlogs4 MeetingsDefinition of DoneSprint3 Roles

METHODOLOGY: Agile, we mean!ANATOMY OF AN AGILE PROJECT

TEAM

● Fully committed members● Cross-functional● 3-9 members● Self organizing

● Estimates and does all the work● Demos work results

METHODOLOGY: Agile, we mean!SUCCESS FACTORS FOR PROJECTS

- Since 2007 we have begun to learn about the world agile.

- At the beginning of 2011 we made our first project in AGILE

METHODOLOGY: Agile, we mean!AGILE LARUS

- Discover customer process- Pain point- Identify candidate project

METHODOLOGY: Agile, we mean!DISCOVERY

- What is a inception - How it works - Who participates - Rough Budget - Build a Vision - Hopes & Concerns - Product Box - Not List - Elevator Pitch - Pain Points - Trade-Ofs

METHODOLOGY: Agile, we mean!INCEPTION

METHODOLOGY: Agile, we mean!EXAMPLE TELECOM con (AM)

METHODOLOGY: Agile, we mean!EXAMPLE TDP

DISCUSS PER TABLE:

● Why would your organization change towards Agile?

● How should your organization change?

● What are the (actionable) steps to take?

METHODOLOGY: Agile, we mean!AGILE ADOPTION IN YOUR COMPANY

METHODOLOGY: Agile, we mean!HOW TO START

THANKS TO


For helping us to achieve the scrum certification and for the material proposed in this presentation

larus 10th - enrico de benetti

Technology