Steven Sim

Idea is

here

Solution

is here

The State Of Development Today

Source: 1. Dave West, Forrester Research

An Acceptable Rate of Failure?

Average Cost overrun: 45%

Average Time overrun: 63%

Functionality delivered on average: 67%

Extreme Chaos, The Standish Group International, Inc. – 2009

Can we continue to support this level of Success?

2. Extreme Chaos, The Standish Group International, Inc - 2009

The State Of Development Today

Considering that software development

accounts for 25% of software spend and

growing, identifying and addressing the

root causes of software development

failure makes business sense.

Features

Time Budget

Quality

− Today that Triangle has become a square; − With quality being the 4th dimension

− It is commonly accepted that you can only achieve 2 of the 3

− Do we call that Success?

− Are you willing to settle for 2 out of 4?

Features

Time Budget

Pick Any Two

Which Two Would You Give

Up?

Project management

Project implementation - support

collaboration of various project roles

Project progress tracking and reporting

Requirements management

Development team collaboration

Project planning, organizing and managing

resources

Insights into project health and visibility

for all stakeholders

Project scoping and conceptualization

Project Testing and Debugging

Requirements Development Test Deploy Maintenance

Test

Planning Test Design

Environment

Prep

Test

Execution Test Analysis

Team

Foundation

Server

(TFS)

Simplicity thru Integration • Enhance Team Collaboration

• Integrated Development

• From Code to the Database

Team Creativity Unleashed • Architecture as a living Asset

• Spend more time creating code than

debugging it

• Prototype Ideas to bring projects to life

Application Quality Ensured • Spend Less Time Debugging

• Testing Done Right

• Proactive Project Management

Lets Leaders Deliver: • Lower development cost

• Higher quality projects

• Consistent predictable results

• Faster time-to-market

4 Key Benefits of MS ALM Solution

Understand Existing Systems

Eliminate Bugs

Could one change break something unrelated?

How much faster you could learn a new system if you could visualize it?

− Visualize code and assets.

− Identify upstream and downstream dependencies.

− Generate a Sequence Diagram.

− Code has a tendency to "go bad" as time passes.

− How can you ensure architectural integrity?

Queue

• Tester files bug.

Setup

• Developer searches for the source of the defect.

Run

• Developer fixes bug.

Wait

• Bug is assigned to tester.

Move

• Code is moved to test environment.

Risk comes from

not knowing what

you’re doing.”

- Warren Buffet

Are we going to deliver a quality project on time?

What do I need to know now to course

correct?

What ‘fires’ will we have to put out that

we don’t know about?

What can I do to reduce the risk?

DOORS®