IT Productivity Platforms II - 9 Rules for Agile Project Success

www.outsystems.com Page 1 © 2012 outsystems – all rights reserved

9 Rules for Agile Project Successin Enterprise IT

IT Productivity Webinar SeriesPart 2 - July 26, 2012


IT Productivity Webinar SeriesPart 1 – The New Productivity Platforms


Dave ThomasCEOBedarra Research Labs

Jeff NewlinVP & GM North AmericaOutSystems

9 Rules for Agile Project SuccessIn Enterprise IT


Why do (big) IT projects fail?(common wisdom)

Unclear business objectives

Lack of business sponsorship & participation

No formal development process

Too much focus on process, not on outcome

Lack of scope control

The world changes

Poor architecture

Unforeseen surprises (integrations...)

Size, simply too BIG to succeed


Agile


Agile + High Productivity Platforms

• Closing the scope

• Poor architecture

• The world changes

• Need for extensive team management– Dev, Architecture, Test/QA, Release Management


Agile + High Productivity Platforms

• Closing the scope

• Poor architecture

• The world changes

• Need for extensive team management– Dev, Architecture, Test/QA, Release Management

Agile Project can and do fail…


9 Rules for Agile Project Successin the Enterprise


#0

Be One Teamban the us vs. them


The ideal project team

• Two headed team

• Engagement Team– EM = PM + BA + Scope Creep Negotiator– BA– Business Stakeholders

• Delivery Team– DM = Senior Dev + Architect + Team Leader– Senior Dev, Dev– Architect

One SCRUM master is NOT enough!


#1

Have a Vision for the appand make sure everyone knows it



#2

Enforce business participation



#3

Think win/win when negotiating scope creep


Features and Functions Used in a Typical System

Source: Standish Group Study Reported at XP2002 by Jim Johnson, Chairman


Total project budget = Timebox

Features that are used: always or often sometimes rarely or never

Original Scope


Total project budget = Timebox

Features that are used: always or often sometimes rarely or never

Prioritized Scope


Sprint 1 Sprint 2 Sprint 3

Time-boxed Scope


new features

Changes in Scope



Features fornext release


Dropped

Re-prioritized Scope


• Requires maturity from everyone...

• ...especially under stress!

Easy to break Rule #0

This is TOUGH!

Features fornext release


Dropped

Re-prioritized Scope


#4

Build the smallest possible system



#5

Remove adoption pains


• Watch out for issues by trainers

If it is hard to teach, it is hard to use!• First impressions count

Fix annoying stuff ASAP!• Common tasks need a great UX

One extra click is NOT OK• Speed is paramount!

Your app must be pretty and fast

Aim for truly satisfied users


#6

Prepare for early rollout

#7

Adapt testing to the situation


#8

Start integrations early



#9

Overcome releasefobia


Afraid to release


Agile Enterprise Tips0. Be one team

1. Have a Vision

2. Business participation

3. Win/Win negotiations

4. Smallest possible system

5. Remove adoption pains

6. Prepare for early rollout

7. Adapt testing

8. Start integrations early

9. Overcome releasephobia

9 Agile Tips for SuccessPart 2 – IT Productivity Series Webinars

Look for you invitation to our final webinar to address overcoming

releasephobia!

Technology

IT Productivity Platforms II - 9 Rules for Agile Project Success