Agile way vs Traditional Way

Post on 13-Jan-2017

39 views 3 download

Transcript of Agile way vs Traditional Way

Agile Adoption ServicesMONA SHOKROFMONA RADWAN

2

Mona RadwanAgile Coach & TrainerFounder of Agile Arena

Agile Coach & Trainer Co-Founder at Agile Arena

Mona Shokrof

Introduce your self What is your name?

What is your role?

What are you expecting ?

Common Story

Challenges Technology became involved in all business fields which introduced complexity to our work

Technologies change rapidly and evolve to be in the hands on any one

Challenges Market competition became harder with a large number of competitors and rapid market changes

Need to Grow & Evolve Organizations need to adapt to change effectively otherwise they will lose markets

Organizations need to learn a lot of skills without losing focus of their market and needs and with harmony with the existing functions

ProblemDoes our mindset and culture help us to do so ?

Does our mindset and culture help us to do so ?

30 - 40% of systems projects fail prior to completion

Half of all systems projects overrun their budgets and schedules by 200% or more

From:

B.P. Lientz and K.P. Rea, Breakthrough Technology Project Management

Standish Group Study Report, 2002

Problems in traditional mindset Less flexibility to adapt to market changes

Late Revenue

Reduced performanceLocked in wasteIncreased time to marketDecreased likelihood of meeting the business or market needs

Includes a lot of risk due to uncertainty and change

Project challengesHaving an unvalidated vision, thus building the wrong thing

Lack of information in the beginning of the project

Inaccurate estimates and plans

Unplanned changes

Risk mitigation in traditional way

Buffering

Huge Upfront cash

Excess planning activities

Focus on idle workers not idle work (increase work in process WIP)

Result Big and Long investment

Less flexible to adapt to changes

Less accurate to meet client needs

Wasteful risk mitigation

Increased probability of failure

Better way - Working Agile Focus on working effectively in small chunks which allows the organization to provide value early and get revenue early

Help to validate assumptions early and manage uncertainty by learning from feedback .

Focus on having a mature process and team through project lifetime which eliminates waste and reduce risk

Resulting in increased ROI for the project

How ? Value driven approach Finish the most valuable work early ? 80% of value in 20% of work done Get value early , so income early

How ? Work in chunks

Buffering

Huge Upfront cash

Excess planning activities

Focus on idle workers not idle work (increase work in process WIP)

How ? Inspect and AdaptBuild a mature process which suits your teams by frequent inspecting for problems and challenges and adapting to solve them .

Build a self organizing teams through continuous learning and improvement and effective communication.

Validate your assumptions early and often through valuable output and reliable feedback process

Increase ROI Waste Reduction Get Value early , get income early

Get Value with less effort and time , so less cost

Value and expenses with the same present value

Ability to invest in high value features more with less cost of changing plans

Traditional

Agile

Income

Expenses

Management FlexibilityReal Value measurement

Fail Fast or stop early

Create options

Rapid course correction

Decide to stop on invest more in certain projects

Traditional vs. Agile Approach

• Big and Long • Less Accurate • Less Flexible • Increases risk of failure • Less management control • Wasteful

• Small and short • More predictable • Iterate every 2-4 weeks • Increases probability of success • Active management control and influence

• Eliminate overhead and unnecessary features

Thank You mona.radwan@agilearena.net mona.shokrof@agilearena.net

Agile Adoption ServicesTraining Coaching Assessment

www.agilearena.net