[control] [data] [process] [strategy] [partners] [testing] [validation]
|
|
- Michael Quinn
- 6 years ago
- Views:
Transcription
1 [control] [data] [process] A practical approach to using Agile in an FDA regulated environment environment Jim Gunning Director, Q-CSV Johnson & Johnson [strategy] [partners] [testing] [validation]
2 Agenda What is Agile? Regulatory expectations for software development Agile vs. Waterfall Agile in Practice Benefits and Challenges Confidential. For J&J internal use only. 2
3 What is Agile? Agile is a group of software development methods in which requirements and solutions evolve through collaboration between self-organizing, cross-functional teams. Agile Implementation track used in J&J is based on the Agile SCRUM methodology Allows for iterative and incremental software development where requirements and the solution itself evolve based on feedback from cross-functional teams It promotes adaptive planning and minimizes the cost of change Confidential. For J&J internal use only. 3
4 Agile values and principles Agile promotes adaptive planning, evolutionary development, early delivery, continuous improvement, and encourages rapid and flexible response to change. Individuals and interactions over Working software over Processes and tools Comprehensive documentation Customer collaboration over Responding to change over Contract negotiation Following a plan Confidential. For J&J internal use only. 4
5 Regulatory Expectations for software development Regulatory agencies do not prohibit or encourage the use of any specific software development methodology, but they do indicate some expected characteristics of the selected software lifecycle and development: Established (controlled) processes for producing high-quality software (control over design and development processes) Evidence of design control, or how the requirements set has evolved during the development of the product, and require risk management to be integrated into the design process Software VERIFICATION and VALIDATION conducted throughout the software development lifecycle Documentation (evidence) to demonstrate compliance to regulations and to facilitate the investigation of software problems Confidential. For J&J internal use only. 5
6 Reconciling the Scrum Approach with Regulations Scrum Expectations Working software over comprehensive documentation Responding to change over following a plan Individuals and interactions over processes and tools Regulatory Expectations Established (controlled) processes for producing high-quality software (control over design and development processes) Evidence of design control, or how the requirements set has evolved during the development of the product, and require risk management to be integrated into the design process Software VERIFICATION and VALIDATION conducted throughout the software development lifecycle Documentation (evidence) to demonstrate compliance to regulations and to facilitate the investigation of software problems Regulatory agencies do not prohibit or encourage the use of any specific software development methodology, but they do indicate some expected characteristics of the selected software lifecycle and development. Confidential. For J&J internal use only. 6
7 Comparing Waterfall to Agile Waterfall inherently wants to lock down requirements in the beginning of development and isn t designed to handle change well In reality change during the computer system development is unavoidable and in some cases beneficial Change can come from a variety of drivers and can impact development Agile does not attempt to lock down requirements in the beginning and assumes requirements and design will evolve and change as more is known during the course of sprinting (Cone of Uncertainty) Agile breaks projects down into user stories which are little chunks of user functionality End users and business stakeholders get to see and experience the system early in the development process Quality improves because testing starts in the sprints Risk is reduced because the risk process is incorporated early Confidential. For J&J internal use only. 7
8 The Role of Documentation in Waterfall Produce documentation that is valuable to both the development team and regulatory stakeholders. Requirements /Design Build Test/Validate In a linear model such as waterfall, in which process activities are executed by different people over different times, documentation provides a means for those people to communicate over time. In the flow of activities shown above, each activity would produce documentation to be handed off to the person who needs it in the subsequent activity. Users(Business) produce requirements documentation to be handed off to developers (IT) to design, who then produce design documentation to be handed off to designers to do develop testing QA approves various documents and testing based on an understanding of they system and design as described in requirement and specification documents Confidential. For J&J internal use only. 8
9 The Role of Documentation in Agile In a parallel model such as Agile, the need for documentation changes significantly. A single team consists of people playing multiple roles and working on multiple activities at the same time so there is less need and less value in producing written documentation as the main mechanism of communication between those people and activities. Documentation still maintains its importance in communicating the results of a team s activities and there are two important audiences to consider: External stakeholders, such as customers, regulators, and auditors, who need information about what was done in order to assess the product and the processes used to create it. Considering regulators and auditors, the team must consider, When we are done, will we have sufficient evidence to demonstrate that our quality system processes were followed correctly? The second audience is a development team that will take the results of the team s activities to build upon in some future work Confidential. For J&J internal use only. 9
10 Agile documentation Who are you communicating with? Once we consider documentation a way of communicating it s worth considering how best to communicate with each audience. Internally (Scrum team) The Scrum team should choose the best way to communicate. Often the most efficient way to communicate will be face to face a key agile principle. Where teams need more precise or long lasting communication they will create documents that are useful to them, such as the product backlog. Stakeholders outside the team In waterfall projects, much of the communication outside of the team is provided by status updates by project managers. In agile, the frequent availability of working software makes this the new method of communication. Working software communicates progress and achievement of stakeholder s requirements clearly and effectively. Project managers still provide status updates and other documentation will describe more precisely what the software does but this documentation only supports working software. It describes what has been built as compared to waterfall documentation s focus on what will be built. Regulatory partners (eg. QCSV) As with other stakeholders outside the team the primary method of communication in agile is through presentation and testing of working software. As this is a key relationship however, communication should occur as early and frequently as possible. It will involve face to face communication as well as documents such as the Agile Compliance Plan, Product backlog, testing scripts/records etc. Confidential. For J&J internal use only. 10
11 Agile documentation This slide lists some of the key agile documentation. Where a project is a linked to a previous waterfall release it may be appropriate to use some of that documentation. Existing legacy life of the system waterfall documentation can be updated when new scope has an impact on existing requirements. Also mapping of waterfall documentation and agile documentation will help when new scope has an impact on existing requirements. Product backlog This is where the requirements for the project are kept. Functional requirements, regulatory and security requirements etc. are all broken down here into items called user stories. These express an aspect of what what the product should do from a single perspective (eg. User/admin etc.) Agile compliance plan This document outlines how the Team will ensure that all SDLC deliverables and activities throughout the Agile project fulfil compliance requirements. Testing scripts/records These records are an essential part of producing high quality code and also form a vital part of the traceability chain. They should demonstrate what has been tested, what the acceptance criteria are, who did the testing etc. And should allow tracability back to the requirement (and reason for that requirement) the code meets. Confidential. For J&J internal use only. 11
12 Agile Traceability When considering traceability in agile projects, it s worth considering its two roles; as useful documentation and for regulatory compliance. To achieve these roles without impacting time spent developing working software, you may need to consider the toolset you use to achieve traceability Traceability as useful documents As traceability records are effectively documents, we should try to apply the agile principle of Working software over comprehensive documentation. This means that creating the traceability records should take less less time and effort to do that it saves later in the project (by assisting in areas such as testing/bug reporting etc.) Traceability for regulatory compliance Traceability is necessary to provide a trail of changes and decisions that can be followed for software that is being developed under regulatory compliance. Traceability toolset The first approach is to consider the tooling used during development. As far as possible, development, testing and application lifecycle management tools should interoperate to create traceability automatically e.g. storing unit tests with developed code, allowing tests to be linked to user stories in the product backlog. This helps ensure that the traceability records help to create value (in the form of working software) rather than eating into value by taking up more time than they save. This may mean that you need to evaluate the toolset you have used in your project under waterfall to ensure that it can support an effective agile approach. If it does not, special attention must be paid to how to transfer any traceability records from one tool to another. Useful documents Regulatory compliance Toolset Confidential. For J&J internal use only. 12
13 Agile Testing In waterfall, the testing phase often falls towards the end of the project. From one point of view this is understandable this is the first time that enough pieces of the application are complete enough to enable them to be tested together. Unfortunately we also know that the end of the project is when the cost of any code changes is at its highest. A key agile principle is that we Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. The key words in this principle are working software. By delivering working software every sprint (no matter how small that functionality may be) we have something that can be tested much earlier and more often. In agile development, testing is a part of every sprint, not something that waits until the end of a project. Working in agile goes further than just testing at the end of each sprint though. Once a team s tasks have been prioritized and assigned correctly at the start of sprint, how can teams ensure that what they are producing is working software? The solution is test-driven development. Developers build automated testing before they build the code that it tests. The tests are stored alongside the code to help developers know when code is working or done. These tests also serve as documentation that helps to provide a part of the traceability path, showing what the code is supposed to do and the expected behaviour for parts of the software. WATERFALL TESTING WORKING SOFTWARE TEST-DRIVEN DEVELOPMENT Confidential. For J&J internal use only. 13
14 Testing for regulated applications Testing of applications being developed for regulatory environments (such as GxP) requires attention to some particular elements. Firstly it should be noted that early engagement with QCSV will help to ensure that regulatory requirements will be captured and clearly available to the agile team as soon as possible in the project. Contact should be maintained with these groups to ensure that these requirements are kept up to date throughout the project. The general changes to where testing takes place in agile compared to waterfall remain. Agile testing takes place in every sprint whereas testing to meet regulatory requirements is often late in a project. There are currently two approaches to testing for GxP applications. Option 1 Qualified QA test environment Alternatively, teams can set up a validated environment before beginning sprint 1 in conjunction with QCSV and the regulatory requirements. 1. Set up and qualify a development and a QA environment 2. Set up documentation for completion and approvals with QCSV 3. Map acceptance criteria to test scripts and conditions. This approach enables QCSV to carry out their reviews of testing/code within each sprint. Qualified test environment Option 2 Hardening Sprint Teams can carry out a final hardening sprint before release where the application is tested against the regulatory regulatory requirements that are set with QCSV. During a hardening sprint applicable documentation updates (such as sprint backlog and design/configuration design/configuration documentation for GxP) are completed and approved, pre & post approval of test scripts are obtained, code is moved to and formal testing performed in a qualified environment. Hardening sprint Confidential. For J&J internal use only. 14
15 Risk-Based Validation Testing REQUIREMENTS BUSINESS PROCESSES /REQUIREMENTS Potential hazards? Root causes of failure? BUSINESS PROCESSES SUPPLIER ASSESSMENT GxP COMPLIANCE RISK RISK SCORE + RISK PRIORITY H M L = BUSINESS PROCESS / REQUIREMENT RISK MITIGATION CONTROLS & RISK-BASED VALIDATION TESTING Recommended testing types by business process / requirement level risk Cross-functional team conducts risk assessment Confidential. For J&J internal use only. 15
16 GxP Compliance Risk Use the GxP compliance risk and the business process/requirement risk to determine risk-based validation testing Compliance Analysis HIGH DIRECT IMPACT MEDIUM INDIRECT IMPACT LOW REMOTE IMPACT Risk-Based Approach to Validation SOP BP / REQ T RISK BP / REQ T RISK BP / REQ T RISK LOW MORE LEVEL OF TESTING LESS Confidential. For J&J internal use only. 16
17 QUALITY RISK MANAGEMENT SOP for Risk-Based Approach to Validation Confidential. For J&J internal use only. 17
18 Regression Test Strategy All test scripts manually executed and Q-CSV approved assessed for regression Regression Test Bank created and approved Scripts are automated if possible Multiple regressions can be planned depending on code changes Confidential. For J&J internal use only. 18
19 Key Compliance Deliverables Compliance documentation managed in DocSpace and ALM Some documents created/approved once and others incrementally with sprints Key Documents Compliance Analysis Master Compliance Plan Compliance Plan Master Test Plan Release Sprint Test Protocol (covers all testing except Dev and UAT) IQ Protocol IQ Scripts Sprint Backlogs (User Stories) User Story Risk Assessments Functional Specifications (Embedded in user story acceptance criteria) Technical Design Specifications Test Scripts, Defects, Trace Matrix (ALM) Data Conversion/Migration Strategy Data Conversion/Migration Protocol Regression Strategy Integration Strategy (Interfaces) IQ Summary Report Release Sprint Summary Report UAT Protocol UAT Report Compliance Summary Report Master Compliance Summary Report Build Sprints Compliance Documentation Confidential. For J&J internal use only. 19
20 Benefits Closer (earlier) collaboration between CSV and Development Testing started much earlier in the beginning of development End users seeing system earlier and identifying issues early Better opportunity for course corrections within sprints Doing something cutting edge that has brought out the best from the team in terms of creativity and problem solving Confidential. For J&J internal use only. 20
21 Challenges Balancing the theoretical with the practical Environment constraints development for building and QA for formal testing Unable to perform UAT in sprints because of SOP readiness Determining and balancing correct level of CSV involvement in Dev Sprints Keeping Independent Quality Limited data in Release Sprints because of the speed of sprints as compared to ETL process Difficult to get incremental approval of compliance documentation because of speed and timing related to sprinting Compliance workarounds related to non-validated tools (JIRA) Challenges related to off-shore model Confidential. For J&J internal use only. 21
22 Questions Confidential. For J&J internal use only. 22
www.agilegurgaon.com Implementing Agile in Non-Agile World By Kshitij Agrawal www.agilegurgaon.com Agenda Case Study Context Agile Implementation Challenges Agile Journey Current State and Next Steps Key
More informationSoftware Design COSC 4353/6353 D R. R A J S I N G H
Software Design COSC 4353/6353 D R. R A J S I N G H Outline Week 2 Software Development Process Software Development Methodologies SDLC Agile Software Development Process A structure imposed on the development
More informationMIS Systems & Infrastructure Lifecycle Management 1. Week 10 March 24, 2016
MIS 5203 Lifecycle Management 1 Week 10 March 24, 2016 Study Objectives Software Development Processes contd. Alternate Software Development Methodologies 2 Alternate Software Development Methodologies
More informationLeading Practice: Test Strategy and Approach in Agile Projects
Leading Practice: Abstract This document provides best practices on how to strategize testing CA Project and Portfolio Management (CA PPM) in an agile project. The document does not include specific test
More informationImplement Effective Computer System Validation. Noelia Ortiz, MME, CSSGB, CQA
Implement Effective Computer System Validation Noelia Ortiz, MME, CSSGB, CQA Session Outline 1 2 3 4 5 Understanding Regulations and Guidelines Pertaining to Computer Systems Integrate SDLC and GAMP 5
More informationAgile-R. intecs Solutions. A new approach to combine Agile and EN for Railway software development. Agile-R. Trademark registered
intecs Solutions SYSTEM ENGINEERING SOFTWARE DEVELOPMENT PROCESS & RAMS CONSULTING VALIDATION & VERIFICATION EMBEDDED SOFTWARE Agile-R A new approach to combine Agile and EN 50128 for Railway software
More informationAGILE TEST MANAGEMENT WITH VISUAL STUDIO
AGILE TEST MANAGEMENT WITH VISUAL STUDIO any companies are implementing an agile methodology, but often still have waterfall based tools. We ve been working on several agile projects, one of which we collaborate
More informationAPRAJITA MATHUR. Compliance and Agility How it can be done!
APRAJITA MATHUR Compliance and Agility How it can be done! Agenda The Project at Hand AgileBut What we uncovered What we improved What we further improved What worked Heard of Forensics? The CSI Effect
More informationSWE 211 Software Processes
SWE 211 Software Processes These slides are designed and adapted from slides provided by Software Engineering 9 /e Addison Wesley 2011 by Ian Sommerville 1 Outlines Software process models Process activities
More informationIntroduction to Agile (Scrum)
Introduction to Agile (Scrum) Meganadha Reddy K. Technical Trainer NetCom Learning www.netcomlearning.com Agenda Agile - Introduction Manifesto for Agile Development Agile Methodologies Scrum Roles, Artifacts,
More informationWatson Internet of Things. Agile Development Why requirements matter
Watson Internet of Things Agile Development Why requirements matter Executive summary The clear benefits of agile development better collaboration, incremental delivery, early error detection and the elimination
More informationAccelerating Collaboration, Integrity and Innovation Polarion ALM - Enterprise Agile Jiri Walek Clara Cismaru VP Product Management Product Manager
Accelerating Collaboration, Integrity and Innovation Polarion ALM - Enterprise Agile Jiri Walek VP Product Management Clara Cismaru Product Manager 2004 Founded with Disruptive Vision 2005 First Unified,
More informationThe ABC of Agile Business Change. James Yoxall BCS 17 September, 2013
The ABC of Agile Business Change James Yoxall BCS 17 September, 2013 Introduction Purpose is to explore the concept of Agile Business Change What does it mean? Why might it be a good thing? Where and when
More information1. The Case for Agile 2. The Scrum Process 3. Scaling Scrum
1. The Case for Agile 2. The Scrum Process 3. Scaling Scrum Delivering late Delivering over budget Delivering the wrong thing Unstable in production Costly to maintain Smart people trying to do good work
More informationAuditing Agile projects Your grandfather s audit won t work here!
Your grandfather s audit won t work here! Auditing Agile projects For many companies, Agile methodologies are beginning to gain ascendancy over traditional Waterfall development. With their focus on speed,
More informationUsing Agile Software Development to Create an Operational Testing Tool
DISTRIBUTION STATEMENT A: Approved for public release; distribution is unlimited. ITEA Technology Review July 2011 Using Agile Software Development to Create an Operational Testing Tool 21 Jul 2011 F.T.
More informationBusinesses now operate in rapidly changing environment.
Computers II Lesson 3 3.0 Agile software development Businesses now operate in rapidly changing environment. They have to respond to new opportunities and markets, changing economic conditions, and the
More informationQuality Management_100_Quality Checklist Procedure
Quality Management_100_Quality Checklist Procedure Last updated 05/15/2017 Audience: Project Team, Process Owners, Project Management Office Frequency: As Required This procedure provides detailed information
More informationAgile Essentials Track: Business Services
Agile Essentials Track: Business Services Presenter: Mark Thomas Synopsis Are you a victim of building the wrong solutions slowly? If so, you re not alone, and considering an Agile approach may be the
More informationLean IT Opex in the Clouds August 16, 2017 Sudhagar Raghavan
150 Jahre Lean IT Opex in the Clouds August 16, 2017 Sudhagar Raghavan 8/22/2017 1 150 Jahre 8/22/2017 # 150 Jahre 8/22/2017 # 150 Jahre 8/22/2017 # Software Development Life Cycle - The Waterfall Model
More informationOwning An Agile Project: PO Training Day 2
Owning An Agile Project: PO Training Day 2 Petri Heiramo Agile Coach, CST Product Management PO Product management is a larger scope than what Scrum defines as a PO Or rather, Scrum implicitly assumes
More informationImproving Agile Execution in the Federal Government
Improving Agile Execution in the Federal Government 1 Committed Partner. Creating Results. In December of 2010 the government introduced the 25 Point Implementation Plan to Reform Federal Information Technology
More informationAgile Projects 7. Agile Project Management 21
Contents Contents 1 2 3 4 Agile Projects 7 Introduction 8 About the Book 9 The Problems 10 The Agile Manifesto 12 Agile Approach 14 The Benefits 16 Project Components 18 Summary 20 Agile Project Management
More informationEarned Value in Agile: The Definition of done in Agile Software development EVA 16, London, June 14th 15th Kjetil Strand, Promis AS
Earned Value in Agile: The Definition of done in Agile Software development EVA 16, London, June 14th 15th Kjetil Strand, Promis AS 20.06.2011 PROMIS AS 1 Outline of the talk Background Earned Value Analysis
More information7 Agile Best Practices for BA s
7 Agile Best Practices for BA s Jiri Walek VP Product Management Clara Vincenc Cismaru Product Manager Agenda 01 How BA fits into Agile 02 7 Agile Best Practices 03 Conclusion 04 Questions & Answers +
More informationTop 5 Reasons Why Agile Fails (and how to avoid them!) March 2017
Top 5 Reasons Why Agile Fails (and how to avoid them!) March 2017 Ten10 will be presenting on some of the common reasons we see why Agile fails, and how these can be avoided. Name: Steven Osman Role: Ten10
More informationSoftware Development Life Cycle:
Software Development Life Cycle: The systems development life cycle (SDLC), also referred to as the application development life-cycle, is a term used in systems engineering, information systems and software
More informationLecture 1. Topics covered. Rapid p development and delivery is now often the most important requirement for software systems.
Chapter 3 Agile Software Development Lecture 1 Topics covered Agile g methods Plan-driven and agile development Extreme programming Agile project management Scaling agile methods Rapid software development
More informationAgile Test Plan How to Construct an Agile Test Plan
Agile Test Plan How to Construct an Agile Test Plan XBOSoft White Paper How to Construct an Agile Test Plan www.xbosoft.com 2 Agile is changing not only the way we develop software but the way we work
More informationLecture 8 Agile Software Development
Lecture 8 Agile Software Development Includes slides from the companion website for Sommerville, Software Engineering, 10/e. Pearson Higher Education, 2016. All rights reserved. Used with permission. Topics
More informationAgile Manifesto & XP
Agile Manifesto & XP Chapter 3.1-3.3 CMPT 276 Dr. B. Fraser Based on slides from Software Engineering 9 th ed, Sommerville. Slides 8 18-06-10 1 Topics 1) What is Agile trying to do? 2) How to choose plan-driven
More informationReducing Business Risk
July 2005 Reducing Business Risk Through Agile Development Fred Tingey Head of Risk Systems BNP Paribas Introduction Context What is Agile Programming? Traditional vs Agile approach A New Way to do Things
More informationOn various testing topics: Integration, large systems, shifting to left, current test ideas, DevOps
On various testing topics: Integration, large systems, shifting to left, current test ideas, DevOps Matti Vuori www.mattivuori.net matti.vuori@mattivuori.net @Matti_Vuori TUT lecture series of SW Technologies:
More informationSign up to mailing list Join Slack, teaching team is available. All links are on the course website Slides are uploaded there too
Sign up to mailing list Join Slack, teaching team is available All links are on the course website Slides are uploaded there too Week 1 (Oct 16 Oct 20) Introduction lectures Week 2 (Oct 23 Oct 27) Work
More informationFIT2101 Software Engineering Process and Management
FIT2101 Software Engineering Process and Management Agile and Software Process Models Topics Covered Features of Agile What Agile Isn t Agile Process Models Software Process Models In 2001 leaders of lightweight
More informationDESJARDINS NEXT DELIVERY APPROACH. New Enterprise in Expansion and Transformation (NeXT) Case Study February 22, 2018
DESJARDINS NEXT DELIVERY APPROACH New Enterprise in Expansion and Transformation (NeXT) Case Study February 22, 2018 IMPORTANT THINGS TO KNOW This case study is presented by Levio, a DAC Bronze Partner,
More informationSoftware Development Life Cycle
Software Development Life Cycle Author : harvix-distrogmail-com When people are asked to define the SDLC (Software Development Life Cycle), they often come up with something like the following: 1. Planning
More informationBusiness Analysis Essentials
Understand the business analyst's role and responsibilities in a successful project. In this introductory course, you'll delve into the role and responsibilities of the business analyst (BA)- the communication
More informationSoftware Engineering Lecture 5 Agile Software Development
Software Engineering Lecture 5 Agile Software Development JJCAO Mostly based on the presentation of Software Engineering, 9ed Exercise Describe the main activities in the software design process and the
More informationWATERFALL & SCRUM THE RIGHT TOOL FOR THE RIGHT JOB. Robin Brandenburg, PMP, CSM, SCPM
WATERFALL & SCRUM & THE RIGHT TOOL FOR THE RIGHT JOB Robin Brandenburg, PMP, CSM, SCPM 4/16/2013 2 Agenda Introduction The Frameworks SCRUM Differences in Waterfall and SCRUM Comparing the Frameworks Key
More informationMendix Application Test Suite Expert Webinar - September Expert Services Consultant
Mendix Application Test Suite Expert Webinar - September 30-2016 Clyde Waal Eduard de Bruijn - Expert Services Consultant - Solution Consultant Agenda Introduction to ATS Demo ATS Adopting ATS Roadmap
More informationGet to CMMI ML3 Using Agile Development Processes for Large Projects. Catherine Clark, Business Solutions Architect
Get to CMMI ML3 Using Agile Development Processes for Large Projects Catherine Clark, Business Solutions Architect Can CMMI and Agile complement each other? 2 Can CMMI and Agile complement each other?
More informationAgile Maturity and the Quality custody-battle
Agile Maturity and the Quality custody-battle SoftTest 2016 - Adapting & Innovating for Change 13 th October 2016 13 th October 2016 How do we know we can Go Live? 2 HPE TSS R&D Overview Our Agile SAFE
More informationDecomposing SAFe. Saturday, April 30th, 2016 at IIT Chicago Always FREE! Registration is OPEN!
Decomposing SAFe Saturday, April 30th, 2016 at IIT Chicago Always FREE! Registration is OPEN! http://www.chicagocodecamp.com/ I ll be at Manager s Workshop on Monday Half-Day Tutorial: Value Stream Mapping
More informationWhat is Continuous Integration. And how do I get there
What is Continuous Integration And how do I get there Related Workshops Introduction to DevOps Transform your Organization with DevOps Concepts DevOps Implementation Boot Camp Comprehensive literacy on
More informationData Collection for Agile Projects Blaze Smallwood ICEAA Conference 2016
Data Collection for Agile Projects Blaze Smallwood ICEAA Conference 2016 1 Table Of Contents Background: Agile Software Development Methodology Types of Data and Data Sources How Data is Used 2 What is
More informationAgile Software Development in a Regulated Environment. Natalie Custer
Agile Software Development in a Regulated Environment Natalie Custer Disclaimer This presentation represents the understanding of the presenter on the topic addressed. It does not in anyway, form or like
More informationScrum, Creating Great Products & Critical Systems
Scrum, Creating Great Products & Critical Systems What to Worry About, What s Missing, How to Fix it Neil Potter The Process Group neil@processgroup.com processgroup.com Version 1.2 1 Agenda Scrum / Agile
More informationProcesses and Life- Cycles. Kristian Sandahl
Processes and Life- Cycles Kristian Sandahl 2 Maintenance Requirements Validate Requirements, Verify Specification Acceptance Test (Release testing) System Design (Architecture, High-level Design) Verify
More informationAgile Software Development:
Agile Software Development: 1.Agile methods 2.Plan-driven and agile development 3.Extreme programming (XP) 4.Agile project management 5.Pair Programming 6.Scrum 7.Scaling agile methods Rapid software development:
More informationLearning Objectives. Agile Modeling and. Major Topics. Prototyping. Patched Up Prototype. Agile Modeling, but First. Prototyping
Agile Modeling and Prototyping Systems Analysis and Design, 7e Kendall & Kendall 6 Learning Objectives Understand the roots of agile modeling in prototyping and the four main types of prototyping Be able
More informationAGILE SOLUTIONS. Agile Basics
AGILE SOLUTIONS Agile Basics info@one80services.com one80services.com AGILE SOLUTIONS Agile Basics Table of Contents 2 Who We Are 3 What Is Agile? 4 Agile Values 5 Agile Principles 6 Agile Development
More informationThe Changing Roles of BAs and QAs in a SCRUM world
By Stan Wrobel The Changing Roles of BAs and QAs in a SCRUM world For Business Analysts: - Requirements Elicita0on - Business Requirements Documents - So5ware Requirements Documents - Requirements Traceability
More informationAgile. How would you implement agile methodologies and tools for web projects? What do you see as the benefits and challenges to doing this?
Agile How would you implement agile methodologies and tools for web projects? What do you see as the benefits and challenges to doing this? What is Agile? The term agile (sometimes written Agile) was popularised
More informationSoftware Engineering & Project Management Engr. Abdul-Rahman Mahmood MS, PMP, MCP, QMR(ISO9001:2000)
Software Engineering & Project Management Engr. Abdul-Rahman Mahmood MS, PMP, MCP, QMR(ISO9001:2000) armahmood786@yahoo.com alphasecure@gmail.com alphapeeler.sf.net/pubkeys/pkey.htm http://alphapeeler.sourceforge.net
More informationKnowledge Solution Services
Knowledge Solution Services How a PMO can Support Agile Success Presented by David Herron www.davidconsultinggroup.com Why PMOs Are Important It is clear that the demand for technological services in the
More information8 th of April 2015 Bucharest, Romania Vlad Gabriel Sorin Agile PM/Scrum Master
8 th of April 2015 Bucharest, Romania Vlad Gabriel Sorin Agile PM/Scrum Master 1. Introduction 1 min. 2. Waterfall vs Agile 5 min. 3. Agile - General Concepts 5 min. 4. Agile methods: Scrum vs XP vs Lean
More informationSOFTWARE ENGINEERING SOFTWARE-LIFE CYCLE AND PROCESS MODELS. Saulius Ragaišis.
SOFTWARE ENGINEERING SOFTWARE-LIFE CYCLE AND PROCESS MODELS Saulius Ragaišis saulius.ragaisis@mif.vu.lt CSC2008 SE Software Processes Learning Objectives: Explain the concept of a software life cycle and
More informationAgile Acquisition. Peter Modigliani 10 Dec 12. Presented to: Mr. Koen Gijsbers. General Manager NATO Communications and Information Agency
Agile Acquisition Peter Modigliani 10 Dec 12 Presented to: Mr. Koen Gijsbers General Manager NATO Communications and Information Agency Approved for Public Release; Distribution Unlimited 12-4964 2012-The
More informationThis document is copyrighted, the distribution of this document is punishable by law.
Lecture 1 A project is a temporary endeavor undertaken to create a unique product, service or result A process is a series of actions taken in order to achieve result, a project is temporary with a clear
More informationMicrosoft Exam Delivering Continuous Value with Visual Studio 2012 Application Lifecycle Management Version: 9.0
s@lm@n Microsoft Exam 70-498 Delivering Continuous Value with Visual Studio 2012 Application Lifecycle Management Version: 9.0 [ Total Questions: 95 ] Question No : 1 You are utilizing the Microsoft Visual
More informationCopyright Intertech, Inc All Rights Reserved. May 18, 2011
Copyright Intertech, Inc. 2011. All Rights Reserved. May 18, 2011 About Me Dave Schueck Principal Consultant Intertech Dschueck@Intertech.com 20 years experience Variety of technologies, roles, systems,
More informationProcesses. Object Orientated Analysis and Design. Benjamin Kenwright
Processes Object Orientated Analysis and Design Benjamin Kenwright Outline Review What are Processes? Why are they important in Object Orientated Analysis and Design Conclusion and Discussion Summary Revision
More informationCase Study: How to Eliminate Flaws of Waterfall and Agile Development Processes Using a Hybrid Model
Case Study: How to Eliminate Flaws of Waterfall and Agile Development Processes Using a Hybrid Model Agile Waterfall Hybrid Model The Waterfall Model has been the ideal choice for software development.
More informationThe Eight Stages of an Agile Approach That Works
The Eight Stages of an Agile Approach That Works An Overview of the OutSystems Approach to Agile Introduction With the experiences gathered through 500+ Agile projects, the OutSystems team has developed
More informationProcesses and Life- Cycles. Kristian Sandahl
Processes and Life- Cycles Kristian Sandahl 2 Maintenance Requirements Validate Requirements, Verify Specification Acceptance Test (Release testing) System Design (Architecture, High-level Design) Verify
More informationBUSINESS INSIGHTS. Making the Transformational Shift to Scrum
BUSINESS INSIGHTS > Making the Transformational Shift to Scrum 1 Meeting Market Demand Transforming an organizational culture to one that embraces and succeeds with that new methodology is essential. Choosing
More informationBUSINESS INSIGHTS > Making the Transformational Shift to Scrum
BUSINESS INSIGHTS > Making the Transformational Shift to Scrum 1 Meeting Market Demand Transforming an organizational culture to one that embraces and succeeds with that new methodology is essential. Choosing
More informationAgile and Secure Can We Be Both? San Antonio AITP. August 15 th, 2007
Agile and Secure Can We Be Both? San Antonio AITP August 15 th, 2007 Agenda Background Evolution of traditional software development methodologies Benefits of Agile development Requirement for Secure development
More informationBusiness Analyst and Product Owner Where do they meet & conflict? Cherifa Mansoura
Business Analyst and Product Owner Where do they meet & conflict? Cherifa Mansoura www.linkedin.com/in/linkedincherifamansoura Introduction BA responsibilities in an agile environment PO Responsibilities
More informationValidation Documentation. Presented by John Montalto 27 March, 2013
Validation Documentation Presented by John Montalto 27 March, 2013 Validation planning Validation policies define management intent and commitment Validation Master Plans (VMPs) Individual Validation Plans
More informationA Continuous Delivery Journey SHOBHA SUBRAMONIAN APRIL 05, 2018
A Continuous Delivery Journey SHOBHA SUBRAMONIAN APRIL 05, 2018 Picture source: QuizzClub.com Copy r i g ht S A S I nst i t ut e I nc. A l l r i g ht s r e se r v e d. INTRODUCTION A Case Study in moving
More informationCopyright Software Engineering Competence Center
Copyright Software Engineering Competence Center 2012 1 Copyright Software Engineering Competence Center 2012 5 These are mapped categories to the waste categories of manufacturing. An excellent overview
More informationA practical guide to governance of enterprise-scale Agile projects. 4 October 2011
A practical guide to governance of enterprise-scale Agile projects 4 October 2011 What are we talking about! Governance of enterprise-scale Agile projects What is Governance? What is enterprise-scale Agile?
More informationUNIFI 1.5 : Simplifying Qualification and Validation June 2012
UNIFI 1.5 : Simplifying Qualification and Validation June 2012 2011 Waters Corporation 1 Waters Regulated Bioanalysis System Solution Sample Preparation Solutions Best in class ACQUITY UPLC I-Class The
More informationAgile Systems Development In a Medical Environment
Agile Systems Development In a Medical Environment 2016 Jama Software, Inc Meet Jama Requirements & Test Management Cary Bryczek Jama Software Simplify Complex Product Development https://www.jamasoftware.com/
More informationLecture 2: Software Quality Factors, Models and Standards. Software Quality Assurance (INSE 6260/4-UU) Winter 2016
Lecture 2: Software Quality Factors, Models and Standards Software Quality Assurance (INSE 6260/4-UU) Winter 2016 INSE 6260/4-UU Software Quality Assurance Software Quality Quality Assurance Factors and
More informationDebunking Agile Myths
Debunking Agile Myths Rick Clare CBAP, PMP, CSM, MSPM Solutions Partner 634 Alpha Drive Pittsburgh, PA 15238 (888) 762-3683 Fax (412) 963-8618 Presentation Purpose Purpose This presentation will discuss
More informationIntroduction to Agile and Scrum
Introduction to Agile and Scrum Matthew Renze @matthewrenze COMS 309 - Software Development Practices Purpose Intro to Agile and Scrum Prepare you for the industry Questions and answers Overview Intro
More informationARCHITECTING PROJECT MANAGEMENT for Enterprise Agility. Enable Organization with Agile using Tooling/Technology
ARCHITECTING PROJECT MANAGEMENT for Enterprise Agility July 14 to 16, 2016, NIMHANS Convention Centre, Bengaluru Enable Organization with Agile using Tooling/Technology Leverage of Technology Paper Id:
More informationGet to CMMI ML3 Using Agile Development Processes for Large Projects. Catherine Clark, Business Solutions Architect
Get to CMMI ML3 Using Agile Development Processes for Large Projects Catherine Clark, Business Solutions Architect Manifesto for Agile Software Development We are uncovering better ways of developing software
More information[Name] [ ID] [Contact Number]
[Name] [Email ID] [Contact Number] THIS IS ONLY MODEL RESUME - DO NOT COPY AND PASTE INTO YOUR RESUME. PROFILE SUMMARY 15+ years of IT experience in Consulting and worked with the Major clients for the
More informationManaging a Project and Keeping Sane While Wrestling Elegantly With PMBOK, Scrum and CMMI (Together or Any Combination)
Managing a Project and Keeping Sane While Wrestling Elegantly With PMBOK, Scrum and CMMI (Together or Any Combination) Neil Potter The Process Group neil@processgroup.com 1 Agenda Summary of PMBOK, CMMI
More informationCM MatchPoint Agile. Christoph Heinrich, CM First Plex Track A / Session 17
CM MatchPoint Agile This sessions shows how to use CM MatchPoint for the management and automated deployments in agile projects using frameworks like SCRUM Christoph Heinrich, CM First Plex Track A / Session
More informationAgile Resources Series 2
Table of Contents Purpose... 3 Criteria for Using Agile Development Techniques... 3 1. Agile Overview... 3 1.1 Definition of Agile Development... 3 1.2 Benefits of Agile Development... 4 1.3 Roles and
More informationOrganizational Matters
Organizational Matters Christoph Matthies christoph.matthies@hpi.de Software Engineering II WS 2018/19 Prof. Plattner, Dr. Uflacker Enterprise Platform and Integration Concepts group Communication If you
More informationWhy SCRUM I O A N N I S K O S T A R A S A G I L E C R E T E
Why SCRUM I O A N N I S K O S T A R A S A G I L E C R E T E 2 0 1 6 Agenda 2 What is SCRUM? Why it sucks? What is Scrum? 3 SCRUM is Scrum in a Nutshell a methodology an agile framework for software development
More informationBCS THE CHARTERED INSTITUTE FOR IT. BCS HIGHER EDUCATION QUALIFICATIONS BCS Level 6 Professional Graduate Diploma in IT SOFTWARE ENGINEERING 2
BCS THE CHARTERED INSTITUTE FOR IT BCS HIGHER EDUCATION QUALIFICATIONS BCS Level 6 Professional Graduate Diploma in IT SOFTWARE ENGINEERING 2 Friday 30 th September 2016 - Morning Answer any THREE questions
More informationMeasuring Effort and Productivity of Agile Projects
Measuring Effort and Productivity of Agile Projects Measuring Effort Measuring effort means the same thing in agile and non-agile methods: you need to know the hours spent by people working on the release.
More informationBA Role or Skill: David Mantica ASPE Inc. IIBA Lexington, KY Wednesday, August 19 th
BA Role or Skill: David Mantica ASPE Inc. IIBA Lexington, KY Wednesday, August 19 th Agenda A look at the SDLC Crossing the Chasm Decisions in SDLC Overview and Roles in the SDLC The Challenge Model of
More informationAttend Learn Grow Taking Your Career to the Next Level. 4th Annual Professional Development Days! May th, 2018
Attend Learn Grow Taking Your Career to the Next Level 4th Annual Professional Development Days! May 23-24 th, 2018 Our Transition from Waterfall towards Agile Jeff Fearn Why Agile Why Today? Aggressive
More informationSDEFT: Scrum Driven Engagement Framework for Testing
SDEFT: Scrum Driven Engagement Framework for Testing Overview In the contemporary scenario, Agile Development Manifesto symbolizes cutting edge of the software development industry. Organizations need
More informationIntroduction to Agile/Extreme Programming
Introduction to Agile/Extreme Programming Matt Ganis, Senior Technical Staff Member (Certified Scrum Master) IBM Hawthorne, New York ganis@us.ibm.com August 2007 Session 8061 Current slides at: http://webpage.pace.edu/mganis
More informationAdvanced Release Planning
Agile Project Management Jim Highsmith Chapter 8 Advanced Release Planning Failure to keep Release Plans current! Management needs to know how a business problem will be solved, its cost, how long it will
More informationSession 11E Adopting Agile Ground Software Development. Supannika Mobasser The Aerospace Corporation
Session 11E Adopting Agile Ground Software Development Supannika Mobasser The Aerospace Corporation The Aerospace Corporation 2017 Overview To look beyond the horizon and to embrace the rapid rate of change
More informationPolarion ALM. Use Cases & Demo. Pasi Ahola, Tapio Tuomola Taipuva Consulting Oy
Polarion ALM Use Cases & Demo Pasi Ahola, Tapio Tuomola Taipuva Consulting Oy Agenda 1. Introduction What is ALM Application Lifecycle Management? Why? Industry trends for justification 2. Demo Based on
More informationCourse Title: Planning and Managing Agile Projects
Course Title: Planning and Managing Agile Projects Course ID: BA15 Credits: 21 PDUs Course Duration: 3 days (Live in person class only) Course Level: Basic/Intermediate Course Description: This 3-day course
More informationSucceed with Agile at Scale
IBM Software Group Succeed with Agile at Scale Alfred Tse/Osmond Ng Rational Software Technical Professionals Growth Markets Asia Pacific June 25, 2009 2008 IBM Corporation Agenda Agile Software Development
More informationComparing Scrum And CMMI
Comparing Scrum And CMMI How Can They Work Together Neil Potter The Process Group help@processgroup.com www.processgroup.com Version 1.0 1 Agenda Definition of Scrum Agile Principles Definition of CMMI
More information