PMINJ Chapter 02 May Symposium Hybrid Agile The Best of Both Worlds

Size: px

Start display at page:

Download "PMINJ Chapter 02 May Symposium Hybrid Agile The Best of Both Worlds"

Allyson Stewart
5 years ago
Views:

2 CONTENTS Waterfall Overview High Level Agile Overview What Does the Business Want? Hybrid Agile Overview Review the Methodology Management Style: Scrum or Traditional PM? Does it meet the business needs? Real life examples When to Use What 2 Copyright 2015 HCL Technologies Limited

3 Timeline 1956 First Discussed at a Symposium 1970 First publicized description was in an article by Winston Royce 1976 First time Waterfall terminology used 1985 US Department of Defense adopts Waterfall methodology as their standard WATERFALL OVERVIEW Highlights Structured Approach Sequential process that flows through stages - Requires previous phase to be signed off as completed - Emphasis on Documentation (Design, test plan, code reviews, migration plan, etc) 3 Copyright 2015 HCL Technologies Limited

4 PROS & CONS OF WATERFALL METHODOLOGY PROS Provides a framework and discipline for implementing projects Simple and easy to understand/use Catches flaws during the Design Phase Reduces number of errors and the severity of the errors released to production Provides a defined Planning schedule so the business knows when they will hit milestones Allows users to work in only one system as a new system or update is being launched Understanding requirements ahead of time saves on development costs Able to better plan budgets more accurately CONS Risks associated when user is not engaged between Design and UAT Changes are more costly the further in the lifecycle Working software isn t built until very late in the lifecycle Requirements have a high probability of changing; users don t know what they want until they see something in action Sometimes a designer s assumptions aren t feasible 4 Copyright 2015 HCL Technologies Limited

5 WHAT IS AGILE? Characteristics Freeform software Design Model? Flexible, adaptive planning, evolutionary development Promotes Communications Customer Feedback Throughout Process Collaboration More Important than Design Small Teams Self Managing Autonomous No defined scope Backlog - Grooming Philosophy? Methodology? Way of Life? 5 Copyright 2015 HCL Technologies Limited

6 Why did we move in this direction? AGILE, HOW DID WE GET HERE? Looking for a better way to develop software more nimble approach, unknown requirements Increased need/desire for a better user experience Need to reduce risk of being totally off-track and not finding out until UAT Need to quickly adapt to changing requirements Why is Agile so popular? High user involvement Increase users adoption Growing Evangelist Basis Can see results faster No big gotcha just before go-live as users provided feedback along the way Where does it fall short of meeting business needs? No clearly defined scope, inability to plan or commit to dates 6 Copyright 2015 HCL Technologies Limited

8 PROS & CONS OF AGILE METHODOLOGY PROS Allows consistent user input and feedback throughout the project s lifecycle Products can be released in smaller segments, which enables you to see results sooner Minimizes the risk of unknowns during UAT testing Great for when requirements are unclear (rapid prototyping) Flexible Design Model CONS No defined scope - only commit to number of sprints and stories based on estimated velocity; can lead to longer projects than what is acceptable to business Plan one sprint at a time can t commit to business when functionality can be delivered Users may need to work in multiple system simultaneously Parts of business may become unhappy as their requirements get continually reshuffled to bottom and never delivered Hard to predict timelines Hard to estimate budgets No clear plan; everything is a bit nebulous People leaving project can have huge impacts 8 Copyright 2015 HCL Technologies Limited

9 USER EXPERIENCE TRENDS UX is Everything get to know users through personas, customer journey maps, usability testing Big UX Trends for 2016 SMARTER DEVICES Devices are becoming smarter, so the required user decisions are decreasing when using your product; this allows for less cluttered forms and processes MORE INTERACTION, LESS PIXELS OS s are coming with more robust UI pattern libraries that are very flat, which makes the interactions and animations vital to a users enjoyment of an experience PROTOTYPING IS THE NEW KING With numerous prototyping tools launched before 2016 (Invision, Marvel, Sketch, etc.) and more coming this year (Adobe XD), prototyping at the designer level will be vital in crafting experiences the users love TOUCH FIRST With the new hybrid laptop devices gaining more mainstream adoption in 2015, it is no longer a mobile first design world; it is now a touch first design world 9 Copyright 2015 HCL Technologies Limited

10 What does the business really want? BUSINESS & STAKEHOLDER NEEDS QUALITY HIGH-END ADOPTION COMMITMENT Reduction in Time Spent Correcting Bad Processes Quality Built In Quality Processes, Quality Data Quick User Adoption Intuitive Reduce Training Time Lasting Impression Schedule Budget Value Ease of Use Improving Efficiencies 10 Copyright 2015 HCL Technologies Limited

11 What is Hybrid Agile? Also Known As: Agile Waterfall Iterative Development Wet Agile ScrumFall Others? Combines Waterfall and Agile Characteristics to : Provide a structured methodology for software development Allow for planning of when functionality will be delivered Iterative Development of UX/UI Components feedback loops User involvement throughout SDLC 11 Copyright 2015 HCL Technologies Limited

12 HYBRID AGILE METHODOLOGY DISCOVER SPRINT(S) IMPLEMENT PLANNING REQUIREMENTS HIGH-LEVEL DESIGN Sprint 1 Sprint 2 Sprint n UAT RELEASE Develop Develop Develop Project Management Process Design Technology Security Organizational Change Management 12 Copyright 2015 HCL Technologies Limited

13 HYBRID AGILE IS THE BEST OF BOTH WORLDS ADVANTAGES Scheduling Capabilities Allows business to plan when getting functionality Early User Input/Feedback Minimizes risk of users not seeing system until UAT Provides PM framework Allows UI/UX work to be done in parallel while interfaces and foundational work is being done Flexibility Requirements not fully locked down during Discovery phase. Allows for changing requirements as uncover more of the truth Provides for a big bang approach when needed. Wouldn t want users doing work between two systems as Agile approach is being used Organizational Adoption Easier for organizations to adopt than a pure Agile Methodology Project Management Traditional Project Management style easier on organizational adoption ERP Systems Great for ERP type implementations like SAP Lessen Risk of Errors Released to Production Lessens the number/severity of errors being released to production as testing downstream processes and system as a whole 13 Copyright 2015 HCL Technologies Limited

14 REAL WORLD EXAMPLES ERP implementations Large National Office Supply Company New UI on top of SAP for call center Integrated with telephony system, SAP CRM 7.0, Mainframe order entry, SAP Order entry, AS400 Order Entry Cloud based applications Designed new UI s on top of cloud based CRM system in both Telecom and Life Sciences Industries Cloud based system provided foundation. System was configured, new UI developed, and integrations built CRM systems One of the largest chipmaker/process maker companies in the world, global implementation with 10 different business groups Started as Hybrid Agile to set foundation Moved to Agile after first year Issues with Agile: Certain business groups couldn t get implemented what they wanted due to grooming of backlog 14 Copyright 2015 HCL Technologies Limited

15 THING TO THINK ABOUT? Traditional or Agile PM Style? Tools used? Business Expectations Is it Right for your Organization? In the end it s all about open and honest communication, expectation setting, working together as a team BUSINESS NEEDS Allows Interactive Design/Development Can update requirements as learn new information Feedback During Testing Cycles Minimizes Risk During UAT Timeline of When to Expect Functionality Not have to work in multiple systems Organizational Readiness Provides PM Structure Ability to more accurately budget Often times easier for organization to transition to than Agile 15 Copyright 2015 HCL Technologies Limited

16 CONCLUSION WHEN TO USE WHAT Where is Hybrid Agile a good fit? Want big bang release Need to build out foundation first can t have a user working in two systems to perform job, poor user experience Organization wants defined schedule, traditional PM practices, defined budget Where is pure Agile a good fit? Agile is good with smaller projects (mobile apps, websites that can be decomposed, building on solid foundations) Underlying principle Engage users early and often, and increase stakeholder communications 16 Copyright 2015 HCL Technologies Limited