We think you have liked this presentation. If you wish to download it, please recommend it to your friends in any social system. Share buttons are a little bit lower. Thank you!
Presentation is loading. Please wait.
Published byLukas Jayne
Modified about 1 year ago
logo van Flair Polteq logo_RGB.png “Fast delivery on a slow train” Marc van 't Veer
logo van Flair Polteq logo_RGB.png RGB Blauw Rood Groen 2© 2014 Amsterdam Central Station Source: ARCADIS NL Train Bus Ferry-boat Subway Bicycle
logo van Flair Polteq logo_RGB.png RGB Blauw Rood Groen 3© 2014 Casus New e-commerce program with 100+ employees Back-end in waterfall, (mobile)website in iterations, mobile app in agile mode A big chain of applications (20+), enterprise service bus with web services Multiple suppliers from NL, UK, IND, BG 1 go live moment Suppliers are responsible for system testing
logo van Flair Polteq logo_RGB.png RGB Blauw Rood Groen 4© 2014 Problem definition Natural focus on processes and the logistic chain in a waterfall process Market analysis – Competition, high demanding customer, device/platform fragmentation, response/agile, time to market Risks – Product owner can’t be part of all parallel teams – Missing impact of decisions made on the other development parts (front- vs. back-end) – Missing perspectives (usability) and direct input of end users during DLC
logo van Flair Polteq logo_RGB.png RGB Blauw Rood Groen 5© 2014 Parallel development – no alignment SIT UAT Back-end Front-end TiP / Pilot supplier development Go live DesignTestBuild Waterfall Iteration Agile
logo van Flair Polteq logo_RGB.png RGB Blauw Rood Groen 6© 2014 Is alignment needed? Is there a risk analysis? One central planning? A mile- stone roadmap? A progress report? A DTP/MTP? When are you done? What is your scope? What and how do you prepare? Do you have preparation time and when is this? How many test runs do you have? Who is responsible for regression effects? Responsibilities? To whom do you report? How do you collaborate with other teams? Do you review? Are there dependencies? How to handle system integration defects? When do you have a total product? How stable is your test environment? When to install, patch, delivery, hotfix, upgrade, backup a system? Are there supplier conflicts? Process Team
logo van Flair Polteq logo_RGB.png RGB Blauw Rood Groen 7© 2014 What happens if ….? A defect is found? The market or business is changed? A change is needed? There is a missed impact or dependency? Delivery deadline of a system is changed? An extra release is needed?
logo van Flair Polteq logo_RGB.png RGB Blauw Rood Groen 8© 2014 What makes it so complex for a tester? Continuous switch between process and product view Sensitive to changes in planning Looks like a matrix organization Complex communication process Regular (weekly) merges Parallel working releases There is waiting time Constant scope discussions Do we have time to test after all alignments? How do we plan the testing?
logo van Flair Polteq logo_RGB.png RGB Blauw Rood Groen 9© 2014 My approach - Changing gears Enablers, what is helping a testers Testers need to be flexible, deliver a service and have extra skills – Gears in your head – Gears in your working methods
logo van Flair Polteq logo_RGB.png RGB Blauw Rood Groen 10© 2014 What is helping a tester - enablers Centralized defect management (process and tool) A product owner for all teams Multiple fully deployed integration environments A unified stub framework for all interfaces A central heartbeat on a combined release calendar Central register of interface descriptions A forum to discuss planning, defects, design choices and risks within all teams Clear list of dependencies between projects Automated regression test (incl. the tools to run it) Overview of the progress of the different teams Alignment process over the teams
logo van Flair Polteq logo_RGB.png RGB Blauw Rood Groen 11© 2014 How many heartbeats can you handle? Consider how many normal installations, fixes, re- deployments, backups, test preparation and execution is possible in X period of time (like a month)? Look at the method: Do you want to go multiple times through the waterfall or is agile more fixed to the expected features and time line? Select a heartbeat that fits the whole organization
logo van Flair Polteq logo_RGB.png RGB Blauw Rood Groen 12© 2014 Combined release calendar SIT UAT SIT regression UAT Chain TiP / Pilot 70% Must haves ? 30% Next release Go live Back-end Front-end Test environment 2 Test environment 1 supplier development DesignTestBuild Iteration Agile
logo van Flair Polteq logo_RGB.png RGB Blauw Rood Groen 13© 2014 Gears in your head Terms / vocabulary Cope with changing priorities Able to switch between process and product focus Handle multiple roles, responsibilities and tasks Able to time travel on the release calendar Concurrent have a scrum master, test and project manager Need domain knowledge (applications/organization) Be flexible in your traditional work in phases and join multi-disciplinary agile team
logo van Flair Polteq logo_RGB.png RGB Blauw Rood Groen 14© 2014 Gears in your working methods Perform risk sessions Keep your administration constant up to date You can transfer defects between the agile, iterative and waterfall team Able to schedule your work multiple ways Be a specialist on a system and understand the chain Multiple suppliers internal, local and outsourced Determine impact of defects over multiple releases Your communication skills need to be top
logo van Flair Polteq logo_RGB.png RGB Blauw Rood Groen 15© 2014 Conclusion Every supplier can run in a different pace or follow a different development method Combination of agile, iterative and waterfall makes it complex Key is the chosen hart beat for the release calendar (some) Development alignment is needed Testers can help and be the oil in the machine A tester needs to be flexible and learn to change gears between the multiple teams
logo van Flair Polteq logo_RGB.png RGB Blauw Rood Groen 16© 2014 “Fast delivery on a slow train” Questions?
Basic SDLC Models. Agenda SDLC definition Waterfall SDLC V-Shape SDLC Spiral SDLC RUP SDLC Agile methods.
Exploring Enterprise Agile Transformation Strategies Mike Cottmeyer, Enterprise Agile Coach LeadingAgile, LLC.
Kathy Reed June 4, 2013 IIBA Austin CBAP Study Guide for the Business Analyst Body of Knowledge (BABOK) Version 2.0.
The Role of a BA in a Vendor Software Solution Sharon Ashton Mathew Stordy.
1 GREY BOX TESTING Web Apps & Networking Session 10 Boris Grinberg
Unit-V -SOFTWARE QUALITY. To develop and deliver robust system, we need a high level of confidence that Each component will behave correctly Collective.
The right tools for the job How to choose a web / bespoke development company.
E-Sourcing Today A Perspective on the Role and Scope of e- Sourcing and the State of the e-Sourcing Marketplace.
Software Development Practices and Methodologies Svetlin Nakov Telerik Corporation
Encombrement maximum du logotype depuis le bord inférieur droit de la page (logo placé à 1/3X du bord; X = logotype) Axa UA Leerstoel - Testing.
Presentation Title | Date | Page 1 The Road to SOA.
What is the Value of Architecture Andrew L Macaulay Global Head of Architects Community March 2006 In collaboration with Microsoft Architect Insight Conference.
Software Development QA Best Practices May 20, 2010 Suzette Hackl, CSM Senior Project Manager Skyline Technologies, Inc.
The Smart Implementation Intergraphs Approach & Strategy to Support Successful System Implementations Richard Smykay August 2008 Hilton Opera Hotel.
Project Management in Team Software Projects The primary challenge of project management is to achieve all of the goals of the project charter while adhering.
® IBM Software Group © 2008 IBM Corporation A new feature providing mainframe development flexibility David Myers Rational Developer for System z Product.
Business Value of IT Outsourcing Gopal Kuchibhotla 8 th February 2006.
Manage an IT Project. Aim This presentation is prepared to support and give a general overview of the ‘How to Manage and IT Project’ Guide and should.
Extreme Programming Patrick Mattis Alana Trafford Akarsh Sakalaspur.
Extreme Programming ( an introduction ). Software Engineering Computer programming as an engineering profession rather than an art or a craft Meet expectations:
Best Practices for Implementing An Information Solution By Even Brande.
CM MatchPoint Agile Plex Track A / Session 17 Christoph Heinrich, CM First This sessions shows how to use CM MatchPoint for the management and automated.
1 Business Processes and their Improvement. 2 Session Objectives n Develop an understanding of business processes n Review process modeling basics n Introduce.
9/4/20141 Iterative Project Management Chapter 2 – How Do Iterative Projects Function? Iterative Project Management / 01 - Iterative and Incremental Development.
1 st 5 minutes: Fill out Exercise #13 Write your team answers to #1 & 2 on your flip chart.
. MORE THAN CONSULTANTS. WERE ESSENTIALISTS. 1 1 Improving Business Analysis and Requirements Engineering. Presented by: Morris Oslin, Trissential, LLC.
Chapter:4 Principles That Guide Practice Unit II.
Planning, Organizing and Controlling. What is a project plan? A project plan is a model of the process that the project team intends to follow to realise.
Keith McMillan Principal, Adept Technologies Copyright (C) 2008, Adept Technologies llc.
© 2016 SlidePlayer.com Inc. All rights reserved.