9 Rules for Agile Project Success                                 in Enterprise ITIT Productivity Webinar SeriesPart 2 - J...
IT Productivity Webinar SeriesPart 1 – The New Productivity Platforms
9 Rules for Agile Project SuccessIn Enterprise IT                   Jeff Newlin                   VP & GM North America   ...
Why do (big) IT projects fail?(common wisdom)           Unclear business objectives   Lack of business sponsorship & parti...
Agile
Agile + High Productivity Platforms • Closing the scope • Poor architecture • The world changes • Need for extensive team ...
Agile + High Productivity Platforms • Closing the scope • Poor architecture • The world changes • Need for extensive team ...
9 Rules for AgileProject Success  in the Enterprise
#0Be One Teamban the us vs. them
The ideal project team• Two headed team• Engagement Team         One SCRUM master  – EM = PM + BA + Scope Creep Negotiator...
#1Have a Vision for the appand make sure everyone knows it
#2Enforce business participation
#3  Think win/win whennegotiating scope creep
Features and Functions Used in aTypical System            Source: Standish Group Study Reported at XP2002 by Jim Johnson, ...
Original Scope                              Total project budget = TimeboxFeatures that are used:   always or often       ...
Prioritized Scope                              Total project budget = TimeboxFeatures that are used:   always or often    ...
Time-boxed ScopeSprint 1   Sprint 2   Sprint 3
Changes in ScopeSprint 1   Sprint 2   Sprint 3                                 new features
Re-prioritized                              Scope           DroppedSprint 1   Sprint 2   Sprint 3                         ...
This is TOUGH!                           Re-prioritized                              Scope           DroppedSprint 1   Spr...
#4Build the smallest possible system
#5Remove adoption pains
Aim for truly satisfied users• Watch out for issues by trainers              If it is hard to teach, it is hard to use!• F...
#6  Prepare for early rollout             #7Adapt testing to the situation
#8Start integrations early
#9Overcome releasefobia
Afraid to release
9 Agile Tips for SuccessPart 2 – IT Productivity Series Webinars                                     Agile Enterprise Tips...
IT Productivity Platforms II - 9 Rules for Agile Project Success
IT Productivity Platforms II - 9 Rules for Agile Project Success
IT Productivity Platforms II - 9 Rules for Agile Project Success
IT Productivity Platforms II - 9 Rules for Agile Project Success
Upcoming SlideShare
Loading in …5
×

IT Productivity Platforms II - 9 Rules for Agile Project Success

361
-1

Published on

In this webinar, we’ll share the experience from over 800 agile projects across a wide range of enterprise IT shops, and describe the 9 rules for your agile project success in Enterprise IT.
www.outsystems.com/company/events/web/9-rules-for-agile-project-success/

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
361
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
14
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • Must define what failure is: late, over budget, does not meet business objective or solve the ultimate problem, solves the problem, but creates othersSize, simply too BIG to succeedTeam, scope, features, integrations, stakeholders
  • Agile came about in response to these and other reasons for failure of big IT projects
  • Mention last webinar with ForresterClosing the scope Your dev platform must provide enough speed and flexibility for change to sustain changes (scope creep) without substantial increase in costPoor architectureYour dev platform must enforce good architectural practices. Plus it must make it cost effective to refactor Large portions of the application when appropriate.The world changesShort, highly productive projects. 2x to 4x time compression.Need for extensive team managementLarge OutSystems projects are done by small teams of less than 8 people. They are on avg. 11x times more productive
  • Mention last webinar with ForresterClosing the scope Your dev platform must provide enough speed and flexibility for change to sustain changes (scope creep) without substantial increase in costPoor architectureYour dev platform must enforce good architectural practices. Plus it must make it cost effective to refactor Large portions of the application when appropriate.The world changesShort, highly productive projects. 2x to 4x time compression.Need for extensive team managementLarge OutSystems projects are done by small teams of less than 8 people. They are on avg. 11x times more productive
  • We did not include it as a rule, because it is so fundamental… however, since it is so often the cause of problems on a project, it needs to be mentioned
  • Developers are usually insulated from the business. They don’t understand the pain the users go through. Bridge this gap.Create a Vision documentWhy the app and what are the benefits (make money, save money, compliance).Who is going to use it (the User Profiles).The top 10 to 20 most important user stories (tasks) of these Profiles.The Glossary of relevant business terms
  • Remove IT buffersDo not isolate the Business from design decisions.Force business team members to never miss Sprint Demos and Analysis sessions.Business folks are crucial at Sprint Demos. Their capacity to tell you what they need skyrockets.Business project members need to be empowered to make decisions & tradeoffs. Make sure their bosses will not undermine them later.Bring real users that represent the ProfilesBeware of Business Managers that are not users. Beware of Extranet Profiles’ representation (they are not part of the organization…).
  • Risk of delay & being over budget increase exponentially with app sizeDon’t do a big bang. Release one Function, one Product line, one Country, etc first and then follow-on with the restThe extra cost more than gets compensated by the absence of riskTrain the organization in releasing often and iterating2,500 FPs seems to be the limit for one release
  • We discussed the Death by 1000 cuts – the big issues get addressed. The little ones, if ignored, will kill user adoption!Extend life of a project until you assured the users are truly satisfied w/ the app- Give high priority to changes reported by Trainers- Make a great First Impression- Use the Tuning Sprint to correct the top 5-10 “adoption killers” of the app- Focus on a great UX for common tasks- Use email as a way to bring back occasional users to the app- Lower average response time to <1s. Common tasks should have 200 ms response time
  • Focusing on what is important:Delivering a great app that users love to use and that maximizes business benefitCollaboratingto the end goalTrying to bridge knowledge gapsMaking tradeoffs and NOT doing things
  • Testing/QA procedures will need to adapt to an agile way of doing thingsAdd QA team early in the projectWith the variation in scope it is impossible for QA to define test plans based on initial scope documentsClassify apps inUI centric: focus is in showing data and capturing data (e.g. CRM system)Batch/engine centric: focus is on processing according to complex processing rules (e.g. Billing System)
  • “We want perfection!”Business stakeholders are unsure about what users will say. Not sure if the system does what it needs to doToo big a system will require an exponentially larger roll-out that will consume a large investment from the users“We don’t want a second release”We need people in other projects.We don’t want to support the cost of releasing changes.
  • IT Productivity Platforms II - 9 Rules for Agile Project Success

    1. 1. 9 Rules for Agile Project Success in Enterprise ITIT Productivity Webinar SeriesPart 2 - July 26, 2012
    2. 2. IT Productivity Webinar SeriesPart 1 – The New Productivity Platforms
    3. 3. 9 Rules for Agile Project SuccessIn Enterprise IT Jeff Newlin VP & GM North America OutSystems Dave Thomas CEO Bedarra Research Labs
    4. 4. 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
    5. 5. Agile
    6. 6. Agile + High Productivity Platforms • Closing the scope • Poor architecture • The world changes • Need for extensive team management – Dev, Architecture, Test/QA, Release Management
    7. 7. 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…
    8. 8. 9 Rules for AgileProject Success in the Enterprise
    9. 9. #0Be One Teamban the us vs. them
    10. 10. The ideal project team• Two headed team• Engagement Team One SCRUM master – EM = PM + BA + Scope Creep Negotiator – BA is NOT enough! – Business Stakeholders• Delivery Team – DM = Senior Dev + Architect + Team Leader – Senior Dev, Dev – Architect
    11. 11. #1Have a Vision for the appand make sure everyone knows it
    12. 12. #2Enforce business participation
    13. 13. #3 Think win/win whennegotiating scope creep
    14. 14. Features and Functions Used in aTypical System Source: Standish Group Study Reported at XP2002 by Jim Johnson, Chairman
    15. 15. Original Scope Total project budget = TimeboxFeatures that are used: always or often sometimes rarely or never
    16. 16. Prioritized Scope Total project budget = TimeboxFeatures that are used: always or often sometimes rarely or never
    17. 17. Time-boxed ScopeSprint 1 Sprint 2 Sprint 3
    18. 18. Changes in ScopeSprint 1 Sprint 2 Sprint 3 new features
    19. 19. Re-prioritized Scope DroppedSprint 1 Sprint 2 Sprint 3 Features for next release
    20. 20. This is TOUGH! Re-prioritized Scope DroppedSprint 1 Sprint 2 Sprint 3 Features for next release • Requires maturity from everyone... • ...especially under stress! Easy to break Rule #0
    21. 21. #4Build the smallest possible system
    22. 22. #5Remove adoption pains
    23. 23. Aim for truly satisfied users• 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
    24. 24. #6 Prepare for early rollout #7Adapt testing to the situation
    25. 25. #8Start integrations early
    26. 26. #9Overcome releasefobia
    27. 27. Afraid to release
    28. 28. 9 Agile Tips for SuccessPart 2 – IT Productivity Series Webinars Agile Enterprise Tips 0. Be one team 1. Have a VisionLook for you invitation to our final 2. Business participation 3. Win/Win negotiations webinar to address overcoming 4. Smallest possible system 5. Remove adoption pains releasephobia! early rollout 6. Prepare for 7. Adapt testing 8. Start integrations early 9. Overcome releasephobia
    1. A particular slide catching your eye?

      Clipping is a handy way to collect important slides you want to go back to later.

    ×