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

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

IT Productivity Webinar SeriesPart 1 – The New Productivity Platforms

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

Dave ThomasCEOBedarra Research Labs

Jeff NewlinVP & GM North AmericaOutSystems

9 Rules for Agile Project SuccessIn Enterprise IT

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

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

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

Agile

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

Agile + High Productivity Platforms

• Closing the scope

• Poor architecture

• The world changes

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

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

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…

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

9 Rules for Agile Project Successin the Enterprise

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

#0

Be One Teamban the us vs. them

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

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!

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

#1

Have a Vision for the appand make sure everyone knows it

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

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

#2

Enforce business participation

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

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

#3

Think win/win when negotiating scope creep

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

Features and Functions Used in a Typical System

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

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

Total project budget = Timebox

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

Original Scope

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

Total project budget = Timebox

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

Prioritized Scope

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

Sprint 1 Sprint 2 Sprint 3

Time-boxed Scope

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

new features

Changes in Scope

Sprint 1 Sprint 2 Sprint 3

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

Features fornext release

Sprint 1 Sprint 2 Sprint 3

Dropped

Re-prioritized Scope

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

• Requires maturity from everyone...

• ...especially under stress!

Easy to break Rule #0

This is TOUGH!

Features fornext release

Sprint 1 Sprint 2 Sprint 3

Dropped

Re-prioritized Scope

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

#4

Build the smallest possible system

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

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

#5

Remove adoption pains

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

• 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

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

#6

Prepare for early rollout

#7

Adapt testing to the situation

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

#8

Start integrations early

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

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

#9

Overcome releasefobia

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

Afraid to release

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

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!