Blue Mountain RAM Product Roadmap Jim Erickson, President and CEO Randy Paroda, Director of Product Development.

Slides:



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

Program Management School Agile & ADDIE Add-Up (AAAU) Elliott Masies Learning 2012 October 21-24, 2012.
Feb Alten Group Started in France in 1988 Currently more than people Presence in 10 countries Active in The Netherlands since 2002.
Agile Software Development Robert Moore Senior Developer Curtin University.
Delivering Enterprise Projects Using Agile Methods Brent Barton May 23, 2006.
Property Management Product Development Update Randy Lott Director, Development AMSI.
SDLC – Beyond the Waterfall
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,
What is Agile? Agile is a software methodology based on iterative and incremental development, where requirements and solutions evolve through collaboration.
SCRUM John Drew. SCRUM - overview Scrum is a project management discipline that has evolved since the early 1990s to deliver software that meets business.
Agile development By Sam Chamberlain. First a bit of history..
Software Process and Problem Statements CSSE 371, Software Requirements and Specification Mark Ardis, Rose-Hulman Institute September 3, 2004.
Agile Software Development Matt Rice November 27, 2006.
Computer Engineering 203 R Smith Agile Development 1/ Agile Methods What are Agile Methods? – Extreme Programming is the best known example – SCRUM.
The Challenge to Survive in Today’s Software Development Environment Evaluating the Agile Methodology.
Software Engineering: A Practitioner’s Approach, 6/e Chapter 4 Agile Development copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc. For University.
Coming up: The Manifesto for Agile Software Development 1 Software Engineering: A Practitioner’s Approach, 7/e Chapter 3 Agile Development Software Engineering:
Managing a Project Using an Agile Approach and the PMBOK® Guide
Programming with eyes wide open. Your host today Subby Angelov Team
Agile Process: Overview n Agile software engineering represents a reasonable compromise to conventional software engineering for certain classes of software.
An Agile View of Process
Software engineering Process models Pavel Agejkin.
An Overview of Agile L e a d i n g C h a n g e T h r o u g h C o l l a b o r a t i o n.
Chapter 4 Agile Development
Chapter 4 Agile Development 1. The Manifesto for Agile Software Development 2 “We are uncovering better ways of developing software by doing it and helping.
CPSC 371 John D. McGregor Session 22 Process. Specification and design problem solution specification implementation specification.
© Blackboard, Inc. All rights reserved. Back to the Feature: An Agile, User-centric Software Development Lifecycle Cindy Barry Senior Product Manager Martha.
AgileCamp Presents: Agile 101. Good luck in your presentation! This slide deck has been shared by AgileCamp Kit under the Creative Commons Attribution.
By Saravanan Bala. General Report 31 % of Software projects are cancelled 75 % of the software projects are considered failures by the people who initiated.
1 - Agile in a nutshell. 2 - Basic principles ●Relies on an iterative, incremental development mechanism with continuous adaptation to customer requirements.
IS Methodologies. Systems Development Life Cycle - SDLC Planning Planning define the system to be developed define the system to be developed Set the.
THE AGILE MENTALITY CHAPTER Topics  Why Use Agile and Scrum?  Agile Development –Manifesto for Agile Software Development  Scrum Methodology.
1 The Manifesto for Agile Software Development “We are uncovering better ways of developing software by doing it and helping others do it. Through this.
Looking Ahead with Blue Mountain RAM Jim Erickson, President Randy Paroda, Director of Product Development September 18, 2013.
CS 3610: Software Engineering – Fall 2009 Dr. Hisham Haddad – CSIS Dept. Chapter 4 Agile Development Discussion of Agile Development and Agile Process.
© 2007 BigVisible Solutions, Inc. All Rights Reserved Training Solutions Agile Training Game v
Agile Methodology Paul Mohrbacher. Agile Manifesto We are uncovering better ways of developing software by doing it and helping others do it. Through.
Theories of Agile, Fails of Security Daniel Liber CyberArk.
#AgileEd. Using Agile in the Classroom Cindy Royal, Associate Professor Texas State University slideshare.net/cindyroyal #AgileEd.
Cultivating Agile Requirements
10 key principles of agile software development
Agile Development Chapter 10 - part 2. Agile Philosophy  A guiding philosophy and set of guidelines for : developing information systems in an unknown,
JASS 2006 Agile Software Development. JASS 2006 Agenda.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Think Scrum, act Scrum Scrum Practitioner like a boss Thibault Clavier.
Agile Methodology. -Dhanashree Kumkar -Plus91 Technologies.
Agile Gintarė Bernotaitytė © 2013.
Embedded Systems Software Engineering
Agile/XP Introduction
Chapter 5 Agile Development Moonzoo Kim KAIST
Agile Methods SENG 301.
AGILE SCRUM METHODOLOGY
Flight Software Conference 2016
Software & Software Engineering Pertemuan-4 Dosen :Kundang K Juman
Agile Software Development
Agile Software Development Brian Moseley.
By: By: Agile Scrum Master Online Training.
Copy rights  Exam Eligibility  Exam Pattern  Pre requisites  Content Distribution  Tools and Techniques  Domains and Tasks for.
Tim Hirner - Flagship Speakers January 23, 2014
Agile Software Development
How to Successfully Implement an Agile Project
Lecture 2 Revision of Models of a Software Process
Agile Process: Overview
Chapt 2 Iterative Evolutionary Agile.
Introduction to Agile Blue Ocean Workshops.
Adjective: Able to move quickly and easily. Principles and Values
Project Lifecycle and IT Product Life Cycle
Adapting Agile in Pharmaceutical Industries
Presentation transcript:

Blue Mountain RAM Product Roadmap Jim Erickson, President and CEO Randy Paroda, Director of Product Development

Product Roadmap  Presentation outline –Listening to our customers –The development process –Blue Mountain RAM platform –What’s next

The Development Process  Development Methodology  Software Quality Assurance  Product backlog  Release strategy

The Development Process  Development Methodologies  Adaptive –Near term is clearer –Far term is fuzzy –Accept change  Predictive –Well planned –Change is difficult –Change control board Development Methodology Continuum

The Development Process  From the Agile Manifesto –Individuals and interactions over processes and tools –Working software over comprehensive documentation –Customer collaboration over contract negotiation –Responding to change over following a plan While there is value in the items on the right, we value the items on the left more.

The Development Process a group of software development methods based on iterative and incremental development, where requirements and solutions evolve through collaboration between self-organizing, cross-functional teams. It promotes adaptive planning, evolutionary development and delivery, a time-boxed iterative approach, and encourages rapid and flexible response to change. It is a conceptual framework that promotes foreseen interactions throughout the development cycle.  Agile software development is …

The Development Process

 Scrum –Story writing –Estimation –Release planning –Iteration planning –Metrics

Software Quality Assurance  Where we started  Challenges we faced  Where we are today

Software Quality Assurance  Where we started –Calibration Manager 1 Circa 1992 DOS application –SOPs in place –First customer audits soon to follow –Validation Protocol 1994

Software Quality Assurance  Challenges we faced –Traditional Waterfall Methodology –Beta participation decreased –Internal audits increased –Findings increased –Internal processes became counter-productive

Software Quality Assurance  Where we are today –QSII Driven from the top E2500, GAMP 5, ICH 8, 9, 10 Initial phase was 30 month effort Complete rewrite of our Quality Manual

Software Quality Assurance  Where we see ourselves Development Methodology Continuum AdaptivePredictive ScrumBM TodayBM in 2000

Release Strategy  Product lifecycle –Customer expectation Goldilocks syndrome (not too fast, not too slow) Balance revalidation against new functionality –5 – 10 years Major releases (30 months +/- 6) Service releases ( 12 months +/- 4) Hotfix (as needed)

Product Backlog  Prioritized list of features and functionality –Product Advisory Board  Sources include –Users –Customer Advisory Board –Sales team –Product owner

Blue Mountain RAM Platform

 Complimentary applications –Upgrade utilities –Direct data import –Onboarding utility –Configuration manager –Configuration comparison tool

Blue Mountain RAM Platform  Blue Mountain RAM R3 SR2 –IE 9 support –Application hyperlinks –Embedded documents and images –Reports in workspaces –Rule Engine enhancements –Usability enhancements

What’s Next  High visibility backlog items –Change control –Mobile / Asynchronous –Enterprise tools –Document libraries –Hosting –Usability enhancements

Blue Mountain RAM Product Roadmap Discussion