Program Management School Agile & ADDIE Add-Up (AAAU) Elliott Masies Learning 2012 October 21-24, 2012.

Slides:



Advertisements
Similar presentations
Keith McMillan Principal, Adept Technologies Copyright (C) 2008, Adept Technologies llc.
Advertisements

Applying Agile Methodologies to Traditional Publishing Kristen McLean Bookigee, Inc. February 12 th, 2011.
Iteration Planning.
Colin Weaver The Eleven Essential Behaviours of Successful Agile Project Teams.
COPYRIGHT © 2012 ALCATEL-LUCENT. ALL RIGHTS RESERVED. 1 Agile documentation development methodology Giby Panicker and Judith Benjamin 1-Dec-2012.
What is Agile? Agile is a software methodology based on iterative and incremental development, where requirements and solutions evolve through collaboration.
Agile 101.
Agile Project Management with Scrum
SCRUM John Drew. SCRUM - overview Scrum is a project management discipline that has evolved since the early 1990s to deliver software that meets business.
Blue Mountain RAM Product Roadmap Jim Erickson, President and CEO Randy Paroda, Director of Product Development.
Agile Process Models. Prescriptive models don’t work It is unrealistic to not have changes. Why? The Agile Manifesto: Individuals and interactions over.
Agile development By Sam Chamberlain. First a bit of history..
International Scrum Institute Accredited Scrum Certifications for Agile Software Practitioners.
Agile Software Development Matt Rice November 27, 2006.
Agile Methods.
Managing a Project Using an Agile Approach and the PMBOK® Guide
Programming with eyes wide open. Your host today Subby Angelov Team
Introduction to Agile.
Software engineering Process models Pavel Agejkin.
Agile Design and SCRUM Brent M. Dingle, Ph.D. “For the last few centuries, … science has been attempting to break matter down into ever smaller bits, in.
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.
Get quality results faster: Agile Projects and your team Presenters: Laurie Barnas and Wendy Taylor, Associate Registrars, University of Victoria.
Chapter 3 – Agile Software Development 1Chapter 3 Agile software development.
Larry Apke Agile Expert
1 Agile Methodology & Programming Ric Holt July 2009.
Chapter 4 Agile Development
Software Engineering- Scrum 徐 瑋 Alen 林芳瑜 Flora 1.
Current Trends in Systems Develpment
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.
Stephen Chief Strategy Officer Telerik
© 2006 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 1 Agile Assessment Gadi Lifshitz, Ayelet Kroskin, Barak Yagour, Yael Dubinsky.
THE AGILE MENTALITY CHAPTER Topics  Why Use Agile and Scrum?  Agile Development –Manifesto for Agile Software Development  Scrum Methodology.
Dr. Nguyen Hai Quan.  Why SCRUM?  What is SCRUM?  Some terms  SCRUM Meetings  Sprint  Estimation  Product backlog  Sprint backlog  Whiteboard.
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.
Het einde van het beroep van tester - Wat Agile, DevOps en Scrum betekenen voor het testvak -
AP-1 4. Agile Processes. AP-2 Agile Processes Focus on creating a working system Different attitude on measuring progress XP Scrum.
Jeff Briggs Senior Consultant Capstone Consulting.
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
AGILE - IMPLEMENTATION (C) CLARION TECHNOLOGIES. ability to move quickly and easily…. AGILE MEANING (LITERALLY)
Module 2: What is Agile? Why use it? TLO: Given a DoD program involved in software development, the student will recognize situations where applying agile.
Using Scrum to Improve Teamwork, Communication, Quality and Speed
 Overview of agile project management  Key concepts and terminology  Available resources and tools  Applicability of agile project management to different.
Agile 101. Feasibility Study SDLC – What is it? Systems Development Life Cycle: The most commonly used, and generally accepted, project management approach..
Agile Development Chapter 10 - part 2. Agile Philosophy  A guiding philosophy and set of guidelines for : developing information systems in an unknown,
AGILE - IMPLEMENTATION (C) CLARION TECHNOLOGIES. ability to move quickly and easily…. AGILE MEANING (LITERALLY)
Agile Methodology. -Dhanashree Kumkar -Plus91 Technologies.
Using Scrum to Improve Teamwork, Communication, Quality and Speed.
Informed Traveler Program and Applications Agile / Scrum Overview Jerry Inberg.
Embedded Systems Software Engineering
Chapter 5 Agile Development Moonzoo Kim KAIST
Agile Methods SENG 301.
Manifesto for Agile Software Development
Agile Methodology and Scrum
AGILE SCRUM METHODOLOGY
Scrum.
Agile Training Day 2 November 17, 2015.
Waterfall, Agile & Scaling Agile
Agile Software Development Brian Moseley.
Project Management and the Agile Manifesto
Introduction to Agile Blue Ocean Workshops.
Adjective: Able to move quickly and easily. Principles and Values
Scrum Science NGSS: Engineering, Technology, Applications of Science
Be Collaborative. Be Innovative. Be Agile.
Project Lifecycle and IT Product Life Cycle
Agile, Scrum and CMMI Methodologies
Presentation transcript:

Program Management School Agile & ADDIE Add-Up (AAAU) Elliott Masies Learning 2012 October 21-24, 2012

Jeff Kachik –Program Manager, Program Management School Deborah Gadsden –Director of Operations, Program Management School Presenters

1.Undefined and changing requirements 2.Lack of stakeholder/executive involvement 3.Clear measures of success are undefined 4.Too much in too little time 5.Financial estimates are poor Why Projects Fail

Agile is a framework that focuses on teams that can adapt to change and deliver products early, often and consistently, in accordance with business priorities. What is Agile?

AGILE Scrum Master Product Owner SMEs Development Team Agile Terminology

We value: Individuals and interactions over processes and tools Completed functionality 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 Agile Manifesto: What Does It Mean?

Documentation is not necessary Processes are not necessary No need to follow a plan Agile cannot be audited I ll-disciplined means of development Testing is not needed Agile is always the best approach Misconceptions About Agile

Recognize problems sooner Incremental development Stakeholder involvement early in the process Focused attention on work/deadlines Build efficiencies daily Urgency Continuous improvement Quality Benefits of Agile

Based on a 7 year study of MITs Human Dynamics Laboratory Observed people in 21 organizations Studied communication patterns of some 2,500 plus people for six weeks at a time Key to Agile Effectiveness – Great Teams Harvard Business Review, April 2012

Collected Sociometrics or measures of how people interact A teams success can be predicted by simply looking at data without even meeting its members MIT found that: The most valuable form of communication is face-to- face. and texting are the least valuable. Key to Agile Effectiveness – Great Teams Contd

Successful teams share several defining characteristics: Members talk and listen in equal measure Members face one another; gestures are energetic Members connect directly with one another – not just the team leader Members carry on back channel or side conversations within the team Members break, go exploring outside the team, and bring back information Talent contributes far less than communication skills! Key to Agile Effectiveness – Great Teams Contd

Applying Agile – Where Do We Begin?

Represents what customers need and value Ideally, each backlog item should answer: –Who is the user? –What does the user need to do? –Why does the user need to do that? In the simplest terms, the Backlog answers the questions, What are we building, and why are we building it? Building the Backlog

Based on Scrum in Rugby Advancing the ball together Conducted daily Should last no more than 15 minutes Scrum answers three questions: –What I did yesterday? –What Im working on today? –Are there barriers inhibiting my work? Scrum

Backlog review Extreme focus on work Completion of Backlog Time focused - 2 to 3 weeks Resourcing Team publicly commits work Product owner and development team select user stories to meet iteration goal Sprint

Release is a stand alone measure of value Release planning answers three questions: –When do we want to release? –What is the priority of each story? –What would you like in the release? MoSCoW Rules Must have Should have Could have Wont have this time Release Planning

Backlog Work in progress To do Acceptance testing Done Using Kanban Boards vs. Software Tools

Agile ADDIE Add Up

Agile & ADDIE Add-Up (AAAU) Learning Story

Develop the course in three months Meet certification requirements Use Agile-ADDIE for complex 32- hour course No standards - No processes - No templates Contractors brand new to VA and to each other 20 The Challenge

Take the best of classroom methodology and make it virtual –Interactive learning environment –Problem-based learning activities –Highly engaging –Visually appealing –Innovative –Integrate instructor led with e-learning characteristics –Go green 21 The Vision Test your technology

24 Evaluation Results Scale 1 to 5 with 5 being the best Creativity beyond the norm

Evaluation Results Contd Delivered 6 sessions and 2 pilot sessions to over 150 participants

Questions