Adapting Agile in Pharmaceutical Industries

Slides:



Advertisements
Similar presentations
Iterative Development: Done Simply Emily Lynema NCSU Libraries Code4Lib 2010.
Advertisements

QuEdge Testing Process Delivering Global Solutions.
Test Automation Success: Choosing the Right People & Process
Delivering Enterprise Projects Using Agile Methods Brent Barton May 23, 2006.
SDLC – Beyond the Waterfall
COPYRIGHT © 2012 ALCATEL-LUCENT. ALL RIGHTS RESERVED. 1 Agile documentation development methodology Giby Panicker and Judith Benjamin 1-Dec-2012.
Copyright © The OWASP Foundation Permission is granted to copy, distribute and/or modify this document under the terms of the OWASP License. The OWASP.
Agile Architecture Prabhu Venkatesan for COMP-684.
© conchango Agile Architecture Microsoft Architect Insight Conference Howard van Rooijen
Agile and Medical Device Software
Agile development By Sam Chamberlain. First a bit of history..
© ThoughtWorks, 2008 Improving Productivity and Quality With Agile Patrick Kua.
Agile
The Challenge to Survive in Today’s Software Development Environment Evaluating the Agile Methodology.
COMP 350: Object Oriented Analysis and Design Lecture 2
Agile Process: Overview n Agile software engineering represents a reasonable compromise to conventional software engineering for certain classes of software.
Mobile Apps: Review and Retrospectives Refresher Agile Transformation Team 1.
Chapter 3 – Agile Software Development Lecture 1 1Chapter 3 Agile software development.
Tuesday, June 8 th, Agile Development-Successful Delivery & Implementing Across the Enterprise.
The Software Development Process Chapter 2 Best Practices.
Agile and XP Development Dan Fleck 2008 Dan Fleck 2008.
Testing Challenges in an Agile Environment Biraj Nakarja Sogeti UK 28 th October 2009.
IS Methodologies. Systems Development Life Cycle - SDLC Planning Planning define the system to be developed define the system to be developed Set the.
Chapter 3 Agile Software Development (1/2) Yonsei University 2 nd Semester, 2015 Sanghyun Park.
© Bennett, McRobb and Farmer Avoiding the Problems Based on Chapter 3 of Bennett, McRobb and Farmer: Object Oriented Systems Analysis and Design.
CS3100 Software Project Management Agile Approaches.
© 2007 BigVisible Solutions, Inc. All Rights Reserved Training Solutions Agile Training Game v
Lecture 4 – XP and Agile 17/9/15. Plan-driven and agile development Plan-driven development A plan-driven approach to software engineering is based around.
#AgileEd. Using Agile in the Classroom Cindy Royal, Associate Professor Texas State University slideshare.net/cindyroyal #AgileEd.
CSPC 464 Fall 2014 Son Nguyen. 1. The Process of Software Architecting, Peter Eeles, Peter Cripss 2. Software Architecture for Developers, Simon Brown.
Project management methodologies Waterfall vs. agile vs. half-arsed agile.
Agile. Processes Waterfall Traditional With prototyping Sprial Agile Dynamic Systems Development Method (DSDM) Scrum Crystal eXtreme Programming (XP)
Modelling the Process and Life Cycle. The Meaning of Process A process: a series of steps involving activities, constrains, and resources that produce.
Software Testing Process
Agenda: Overview of Agile testing Difference between Agile and traditional Methodology Agile Development Methodologies Extreme Programming Test Driven.
10 key principles of agile software development
It’s Agile …. like! A Corkman’s introduction to Agile software delivery.
Agile 101. Feasibility Study SDLC – What is it? Systems Development Life Cycle: The most commonly used, and generally accepted, project management approach..
APMG-International Webinar Integrating Agile into PRINCE2® Thursday 19 December 2013 / 13:00 GMT Presented by Melanie Franklin,
Copyright 2015, Robert W. Hasker. Classic Model Gathering Requirements Specification Scenarios Sequences Design Architecture Class, state models Implementation.
Think Scrum, act Scrum Scrum Practitioner like a boss Thibault Clavier.
The role of Finance in Agile Application Development
Agile Methodology. -Dhanashree Kumkar -Plus91 Technologies.
Informed Traveler Program and Applications Agile / Scrum Overview Jerry Inberg.
Utilize Agile Project Management for GIS Projects Jennifer Prather and Lana Tylka.
Introduction to Agile Project Management Presented by Maury Richards, CSP.
Software Engineering cosc 4359 Spring 2017.
Agile development: a PM’s perspective
Chapter 5 Agile Development Moonzoo Kim KAIST
Agile Project Management Athanasios Podaras
Shifting to Agile: Are University Libraries Ready?
Flight Software Conference 2016
Waterfall, Agile & Scaling Agile
Agile Software Development
Iterative and Agile Development
Introduction to Eclipse Process Framework: EPF Composer and OpenUP
Agile Software Development Brian Moseley.
Information Technology Project Management – Fifth Edition
COMP 350: Object Oriented Analysis and Design Lecture 2
Project Management and the Agile Manifesto
Fast, Agile, Simple Decemebr 2017 Think Simple, Run Faster.
How to Successfully Implement an Agile Project
Agile Process: Overview
Introducing ISTQB Agile Foundation Extending the ISTQB Program’s Support Further Presented by Rex Black, CTAL Copyright © 2014 ASTQB 1.
Gathering Systems Requirements
Introduction to Agile Blue Ocean Workshops.
Project Lifecycle and IT Product Life Cycle
Gathering Systems Requirements
Graduate Thesis GRAD 699 (90)
System Development Methods
Presentation transcript:

Adapting Agile in Pharmaceutical Industries Submitted By Prachiben Shah GRAD 699/Late Summer

Agenda Introduction Agile Vs Waterfall Why Agile? Benefits and Challenges Problem Statement Research Approach Results and Findings Discussion –Future study Conclusion

Waterfall Traditional Methodology Suitable for Complex Projects Clear Scope Requirements are not changed Frequently Finish to Start Approach Step by step approach

Changes happen at early stage Agile Requirements change Design evolve Feedback welcome Changes happen at early stage Time boxed activities Less documentation

Agile Benefits Improve quality Risk management Empowers the system Get the clear picture of actionable items Transparency Focuses on Business Value and customers Early predictable delivery Increase Project Control Agile Benefits

Challenges Regulatory Complexity of software development Difference between agile and Documentative Approach Lack of Attempts Lack of Knowledge Resistance to change Challenges

Problem Statement Resistance to Changes Pharmaceutical Projects connect with People Safety Agile Avoids planned documents and process Myth-FDA suggests waterfall

Goal Approach to eliminate factors and make easier adaptation process Explore possibility of agile in Pharmaceutical Setting Solution to challenges Planning Educate People and awareness Regulatory Requirement : Quality Process Quality Product Quality Documentation

Research Approach Keyword Search: articles, Journals, eBooks, Blog posts Strategic plan Comparison Two approaches Choosing Agile Approach Mapping regulatory activities Results and Findings QA activities Future Studies

Result/Findings: Adaptation Approach Activities/Approach to adapt agile in pharmaceutical environment Planning Gather Insights Agile principles and its interpretations Choosing and/or customizing agile approach Mapping regulatory activities to agile practices Benefits of customized approach Balancing conflicts Alternatives for conflicts Requirement Management Documentation Importance of Documentation Requirement Define/Introduce quality stages to ease documentation QA activities (Role) Training Communication Collaboration Flexibility Automation

Agile Interpretation Agile Principles/Manifesto Interpretation Value individuals and interactions over processes and tools Robust Processes Working software over comprehensive documentation Documents Customer collaboration over contract negotiation Processes Responding to change over following a plan Individuals and interactions Roles

Customizing/Selecting Agile Practices

Hardening Sprints Formal testing Record Verification –Document Synchronization activities Formal Document approval Review

Requirement management (Documentation) Deliverables produced from Hardening Sprints Iterative activities Documentation Deliverables Release Planning Update Project Plan Architect Analysis Compose Estimate Future Stories Story Design User Story-Design evaluation Story design approval Update system architecture and system protocol Add to Requirement Document and traceability Matrix Write- Test-Develop Update Design Document and Traceability Demo Document Design Review Acceptance testing Update Test report and test suite Retrospective Update Software Development Plan

Conflicts Requirements Change Requirements from Old system Team members working differently Decision not communicated

Balancing Conflicts Just enough design input rather than completing design input Parallel activities Finish to finish approach Synchronization point in between design input and output. Timeboxed synchronization point

QA Activities Training Change of thinking Communication Collaboration Flexibility Focus on end product Integrate Tool Automation

Discussion Success Story- Griffols Automated Tool Other Regulatory industries Limited Research Articles Customized approach

Further Study In detailed Study and Surveys Research in other documentative industries Real world scenario

Conclusion Agile principles adjacent to regulations requirements Customized approach QA participation Selection of Tools Automation Possible to adapt