Iain Bright Agile Tour Dublin 2015. Background and challenges Building a shared understanding Sharing findings from exploratory testing What worked… and.

Slides:



Advertisements
Similar presentations
The Road to Agile From the Bottom Up Kevin Malley Tracey Clark 1 March 20 th, 2013 SWOQG.
Advertisements

Iterative Development: Done Simply Emily Lynema NCSU Libraries Code4Lib 2010.
Software Testing How has agile changed the game? Karen Greaves.
An Effective Agile Testing Framework AN AGILE TESTING FRAMEWORK
Software development process improvement Ville Wettenhovi Master thesis presentation Supervisor:Professor Jukka Manner Instructor:M.Sc. Markus Aalto Date:23th.
AgileMan Consulting So what the heck is Agile? It came about as a response to the high failure rate of software projects (> 60%), where failure means late,
Agile on Board or How We Do It at Intel Artem Fedko Copyright © 2013 Intel Corporation. All rights reserved Intel are trademark of Intel Corporation in.
Where We Are Now. Where We Are Now Traditional PM versus Agile Methods Traditional PM Approach Concentrates on thorough, upfront planning of the entire.
Chapter 12 INTERACTION DESIGN IN PRACTICE. Overview AgileUX Design Patterns Open Source Resources Tools for Interaction Design
Release Planning – Test Role and Responsibilities Emergence Tech Training / emergencetechtraining.com.
ITEC 370 Lecture 25 Lifecycles. Review Questions? F give prototype demonstration –Testing plan for your software Life cycles –Scrum (Roles, Meetings,
An Introduction to Agile Project Management CHAPTER SEVENTEEN PowerPoint Presentation by Charlie Cook Copyright © 2014 McGraw-Hill Education. All Rights.
1Lou Somers Software Engineering Projects 2IP35 Autumn 2014
Improving Process for Better Software. Who We Are An experiential learning program that provides technology solutions for our partners, and real- world.
Extreme Programming Team Members Gowri Devi Yalamanchi Sandhya Ravi.
Software Development Overview CPSC 315 – Programming Studio Spring 2009.
Xtreme Programming. Software Life Cycle The activities that take place between the time software program is first conceived and the time it is finally.
Software Development Overview CPSC 315 – Programming Studio Spring 2008.
Acceptance Test Planning. Business challenges Unclear requirements Delivered software does not meet value expectations Late-breaking changes and churn.
 What is Software Testing  Terminologies used in Software testing  Types of Testing  What is Manual Testing  Types of Manual Testing  Process that.
Copyright © 2014 ASTQB Presented by Rex Black, CTAL Introducing ISTQB Agile Foundation Extending the ISTQB Program’s Support Further.
Agile/Scrum Case study Code name: ninja.  2 scrum teams  One product backlog  8 months so far  Long term project  External integrations  R&D and.
Sections2.4: Plan Business Analysis Communication 2.5 Plan Requirements Management Process 2.6 Manage Business Analysis Performance Kristee Watts May 7,
Gaining Support for a Sustainable Agile Transformation Dennis Stevens, VP Enterprise Engagements LeadingAgile November 12, 2013.
Extreme Programming Software Development Written by Sanjay Kumar.
Agile Software Development What is Agile? And How are we implementing Agile?
CompSci 230 Software Design and Construction
Lecture # 04 & 05 CS314 Introduction To Software Development Software Development Process (SDP) Instructor :Muhammad Janas khan
Agile Software Development Brian Link
Carmen David, Senior BA Business Analysis Carmen David, Senior BA Business Analysis Foundation in Business Analysis Session 8 DELIVERING THE REQUIREMENTS.
Overview – Implementation Context – Implementation Scope – Implementation Timeline – Keys to Success – Questions.
1 “ Understanding leads to perfection” Author: Herb Isenberg Ph.D A Bird’s Eye View Quality Foundations January 2011.
RUP Implementation and Testing
Testing Challenges in an Agile Environment Biraj Nakarja Sogeti UK 28 th October 2009.
Creating a Brand New Project using Scrum and Agile Techniques Matt Turner, Mark Wightman Red Gate Software.
Extreme Programming (XP). Agile Software Development Paradigm Values individuals and interactions over processes and tools. Values working software over.
An Agile Method for E-Service Composition Author : Pouya Fatehi, Seyyed Mohsen Hashemi Department of Computer Software, Science and Research Branch, Islamic.
UI Panel: Agile User Interface Design Colin Clark.
Chapter 2 Software processes. Topics covered Software process models Process activities Coping with change.
Software Development Overview CPSC 315 – Programming Studio Spring 2013.
Process Presentation 27 th May 2010 Team BASH Sher Jun Tan, Rosh Sam Abraham, Sascha Morris, Waqas Khalid Lone, Rafael.
Dan Luttrell, Northrop Grumman USC Agile Experiences Workshop March 17-19, 2004 Agile Process in a DOD Environment - One Project’s.
WARNING These slides are not optimized for printing or exam preparation. These are for lecture delivery only. These slides are made for PowerPoint 2010.
Confidential and Proprietary 1 Project Management using Scrum at Wachovia.
Phoenix Scrum User Group Simplifying Scrum Online May 21 st 2009.
Priority mechanisms A simple priority triage system (one short sentence) Determine the Goal Covey’s Quadrants Value first Risk first Greatest good to the.
Software Quality Assurance Chip Ene, February 14, 2015.
By Manish Shrotriya CSE MS 4 Point Agile Manifesto 1.Individuals and interactions over processes and tools 2.Working software over comprehensive.
Testing under the Agile Method CSCI 521 Software Project Management based on the book Testing Extreme Programming by Lisa Crispin and Tip House.
Adaptive Software Development Process Framework. Version / 21 / 2001Page Project Initiation 2.0 Adaptive Cycle Planning 5.0 Final Q/A and.
3-Basic Agile Concepts Subtopics 1-The agile methods landscape 2-Common agile concepts and practices 3-Differences between traditional development and.
Business Intelligence in Classroom WHY:.  Purpose – knowledge to make an informed career decision  Process – Use Scrum method of project management.
Skiing and Boxing Coaching Product and Enterprise Teams 黃馨誼 蘇育光 修訂.
Agile Methods SENG 301.
Agile Project Management Athanasios Podaras
Where Agile Business Meets Agile Development
Agile Software Development Brian Moseley.
Agile Workshop Tuesday, November 7, 2017
Advantages OF BDD Testing
Chapter 12 Levels of Testing
Introducing ISTQB Agile Foundation Extending the ISTQB Program’s Support Further Presented by Rex Black, CTAL Copyright © 2014 ASTQB 1.
From a controlled chaos to well oiled machine
Quality Assurance in an Agile Development Team Michelle Wu 2018 PNSQC
Introduction If you have got a call for an Agile testing interview, then congratulations are in order. You may be feeling nervous, but it sure to be felt.
Introduction to Agile Blue Ocean Workshops.
Seeking ‘a’gile Testing
Adaptive Product Development Process Framework
Software Development methodologies
Adapting Agile in Pharmaceutical Industries
Presentation transcript:

Iain Bright Agile Tour Dublin 2015

Background and challenges Building a shared understanding Sharing findings from exploratory testing What worked… and didn’t

Not about Agile Not about testing About people and more importantly – about people working together

Spencer Stuart Greenfield project to replace legacy system Moved to Agile from iterative based Waterfall

Development and test teams not working together Little guidance on how to ‘deliver’ Get involved early Add value to development effort Hybrid version of Agile First complete module to be delivered with this approach

Model based testing technique SRD with Use Cases UI/UX templates and prototypes Mindmap shared with scrum team How to make relevant to developers Kept at arms length

Define approach Paired testing

Legacy defects Previous development stream near completion Flagged for ‘QA review’ post triage Acceptance tests added

Focus on scrum output Loosely time boxed Scope based on relevant part of model Issues and queries logged Feedback shared with lead developer and BA initially Continued through each sprint

Test model reviewed start of each sprint Time not allocated to process Share understanding with all involved UX Designers Stricter with getting issues resolved Avoid ripple effect

Improved quality Less defects raised from formal System Test Integration testing Testers knowledge of system used to guide developers automated API testing Acceptance Tests on legacy defects used for other scrum teams Increased understanding of each others roles

Collaboration shouldn’t be restricted to Agile Don’t keep it to yourself