Agile 3 Hours

8/19/2019 Agile 3 Hours

http://slidepdf.com/reader/full/agile-3-hours 1/4

17‐03‐2016

1

d r r m m 2 s

m a i l . c o m

AgileSpecial reference to

ManufacturingDr. Raj Mohan

[email protected]

d r r m m 2 s

m a i l . c o m

d r r m m 2 s

m a i l . c o m

What is Agile?

‘Agile’ stresses the importanceof being highly responsive to

meet the ‘total needs’ of thecustomer while simultaneously

striving to be leanmanufacturer.

d r r m m 2 s

m a i l . c o m

The Agile Manifesto: Four Values

Individuals and interactions over

processes and tools

Working software over

comprehensive documentation

Customer collaboration over contract

negotiation

Responding to change over following

a plan



17‐03‐2016

2

d r r m m 2 s

m a i l . c o m

Five Values• Commitment —Be willing to commit to a goal. Scrum provides people all the authority they need to meet theircommitments.

• Focus —Do your job. Focus all your efforts and skills ondoing the work that you've committed to doing. Don't worryabout anything else.

• Openness —Scrum keeps everything about a project visibleto everyone.

• Respect —Individuals are shaped by their background andtheir experiences. It is important to respect the different people who make up a team.

• Courage —Have the courage to commit, to act, to be open,and to expect respect.

d r r m m 2 s

m a i l . c o m

12 Agile Principles1. Our highest priority is to satisfy the customer through

early and continuous delivery of valuable software.

2. Welcome changing requirements, even late indevelopment. Agile processes harness change for thecustomer's competitive advantage.

3. Deliver working software frequently, from a couple ofweeks to a couple of months, with a preference to theshorter time scale.

4. Business people and developers must work together dailythroughout the project.

5. Build projects around motivated individuals. Give themthe environment and support they need, and trust them toget the job done.

6. The most efficient and effective method of conveyinginformation to and within a development team is face-to-face conversation.

d r r m m 2 s

m a i l . c o m

12 Agile Principles – Contd…7. Working software is the primary measure of progress.

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

9. Continuous attention to technical excellence and gooddesign enhances agility.

10. Simplicity—the art of maximizing the amount ofwork not done—is essential.

11. The best architectures, requirements, and designsemerge from self-organizing teams.

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

d r r m m 2 s

m a i l . c o m

What is special about Agile?

•Speed to market

•Flexible

•Risk management

•Cost control

•Quality

•Right product

•Transparency



17‐03‐2016

3

d r r m m 2 s

m a i l . c o m

The nine principles for agile management1. Deliver something useful to the client; check what

they value.

2. Cultivate committed stakeholders.

3. Employ a leadership-collaboration style.

4. Build competent, collaborative teams.

5. Enable team decision making.

6. Use short time-boxed iterations to quickly deliver

features.

7. Encourage adaptability.

8. Champion technical excellence.

9. Focus on delivery activities, not process-complianceactivities.

d r r m m 2 s

m a i l . c o m

Product Deployment Flow

d r r m m 2 s

m a i l . c o m

Plan

driven

Value

driven

d r r m m 2 s

m a i l . c o m



17‐03‐2016

4

d r r m m 2 s

m a i l . c o m

Technical

Practices?Project

Initiation?

Release int

Production

Operate inProductionEnterprise

Disciplines?

Project

Selection?

d r r m m 2 s

m a i l . c o m

Of 12 principles, which 3 “lead”?

Enablers#5 Support & trust, #8 Technical excellence, #10 Simplicity

Results

#1 Valuable SW &satisfied customer

#2 Harnesschange for

competitiveadvantage

#9 Constant pace

Methods & tools

#6 Face-to-face

#7 Workingsoftware as primarymeasure of

progress

#11 Self-organizing

teams

Leading principles

#3 Frequentdelivery

#4 Closecommunication

#12 Reflectiveimprovement

d r r m m 2 s

m a i l . c o m

Learning from Manufacturing/Lean

7 wastes for

Manufacturing

7 corresponding

wastes for Software

1. Overproduction

2. Inventory

3. Extra processing

4. Transportation

5. Motion

6. Waiting

7. Defects

1. Extra features

2. Partially done work

3. Relearning

4. Handovers

5. Task switching

6. Delays

7. Defects

d r r m m 2 s

m a i l . c o m

Documents

Agile 3 Hours