Agile History and Values Quiz Explanations

Similar documents
Agile Projects 7. Agile Project Management 21

Function Point Analysis and Agile Methodology

THE ADVANTAGES OF AGILE METHODOLOGIES APPLIED IN THE ICT DEVELOPMENT PROJECTS

MIS Systems & Infrastructure Lifecycle Management 1. Week 10 March 24, 2016

3. Comparison of Above Described SDLC Models

The Systems Development Lifecycle

How to Utilize Agile Project Management for GIS Projects. Lana Tylka and Jennifer Prather

Software LEIC. Lecture 23

Get to CMMI ML3 Using Agile Development Processes for Large Projects. Catherine Clark, Business Solutions Architect

Lean IT Opex in the Clouds August 16, 2017 Sudhagar Raghavan

Get to CMMI ML3 Using Agile Development Processes for Large Projects. Catherine Clark, Business Solutions Architect

Chapter 2: Project Methodologies and Processes

QAIassist IT Methodology General Context

Agile Essentials Track: Business Services

Risk Management and the Minimum Viable Product

Case Study: How to Eliminate Flaws of Waterfall and Agile Development Processes Using a Hybrid Model

Agile. How would you implement agile methodologies and tools for web projects? What do you see as the benefits and challenges to doing this?

Software Development Life Cycle

Software Development Methodologies

INTRODUCTION. Objectives. Unit 1: Introduction to Systems Analysis and Design. Key Ideas

Strike the right balance with Disciplined Agile Delivery (DAD)! October 6, 2016 Kiron D. Bondale, PMP, PMI-RMP, CDAP, CDAI

Watson Internet of Things. Agile Development Why requirements matter

Ian Koenig Quality IS Projects, Inc. Philippines Chapter Project Management Institute June 8 th 2010

Major attributes of the Lifecycle. The Systems Development Lifecycle. Project phases. Planning. Design. Analysis

SOFTWARE ENGINEERING SOFTWARE-LIFE CYCLE AND PROCESS MODELS. Saulius Ragaišis.

6 Tips. How to Sell Agile to Your Executives is brought to you by

AGILE AND SCRUM IN A SMALL SOFTWARE DEVELOPMENT PROJECT- A CASE STUDY

approach to successful project

Project Management Basics (Stefan Sobek PMP) Chapter 2: PM in IT-Context

Software Life Cycle. Main Topics. Introduction

Software processes. Software Applications A.Y. 2018/2019

Where Is The Discipline In Disciplined Agility?

Oracle Unified Method (OUM) Using OUM with Agile Techniques. Jan Kettenis Oracle Global Methods Oracle Consulting Netherlands

6/29/ Professor Lili Saghafi

CS350 Lecture 2 Software Dev. Life Cycle. Doo-Hwan Bae

Agile Development Processes. CSCE Lecture 3-08/31/2017

Agile 101. Brent Hurley Chief Problem Solver Gira Solutions. Values, Principles

Agile Development & Systems Engineering: The Odd Couple. December Glenn Tolentino, PhD John Wood, PhD

Critical Success Factors for Agile Methodology Adaptation in Software Development Organizations

Introduction to Agile (Scrum)

The Customer CAN always be right Realizing Business Agility through Customer Collaboration

Application of Agile Delivery Methodologies. Bryan Copeland Energy Corridor Brown Bag Event August 31, 2016

Agile Software Development

Portfolio & Program Management in an Agile Environment

Are we Agile Yet? Agile is NOT a Destination

Software Design COSC 4353/6353 D R. R A J S I N G H

Callers are in a Listen Only Mode

AGILE LESSONS FROM THE NEW PMBOK. Presented by Eddie Merla, PMI-ACP, PMP

Software Process. Overview

Mainstream Careers AGILE IS THE FUTURE! Agile-Scrum Course Brochure

BCS THE CHARTERED INSTITUTE FOR IT. BCS HIGHER EDUCATION QUALIFICATIONS BCS Level 6 Professional Graduate Diploma in IT SOFTWARE ENGINEERING 2

Agile Software Development. Agile Software Development Basics. Principles of the Agile Alliance. Agile Manifesto. Agenda. Agile software development

Agile Mumbo Jumbo. Helping ICEAA and Cost Estimators Be Agile. ICEAA Professional Development & Training Workshop

AGILE SOLUTIONS. Agile Basics

Agile Project Management. Finding the Optimal Approach

Tear It Down to Build it up

Agile & Innovation State of Research

SCEA 2010 EST06. Estimating Issues Associated with Agile Development. Bob Hunt Vice President, Services Galorath Incorporated

Dave Ulrich outlines underlying (HR) principles and practice, their development and how they are likely to shape up in the future.

Cracking Agile Big Rocks. Chuck Suscheck Quick Solutions Inc. Columbus, OH

Project Management in Practice Agile Agile 101 Introduction to Agile

Applying Agile Principles to Project Management. Tyler Monson PMP, CSM Hiren D. Vashi PMP, PMI-ACP, CSM, CSP

Frameworks - Which one should you choose?

Agile Software Development:

Agile Software Development

Agile Management Guide

SOFTWARE DEVELOPMENT LIFE CYCLE (SDLC)

Introduction to Disciplined Agile Delivery

Session 11E Adopting Agile Ground Software Development. Supannika Mobasser The Aerospace Corporation

AGILE DATA ARCHITECTURE CHEAPER, FASTER, BETTER AGILE DATA ARCHITECTURE SPRINTS: AGILE -VS- JAD 11/10/14. Agile! Full time co-location

An Evolutionary Lifecycle Model with Agile Practices for Software Development at ABB

The Lessons Learned of a BA on an Agile Project

Mastering Agile: Lessons Learned in. World Kevyn Matijevich 2017

Agile SCRUM in Systems Engineering A Practical Application

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

Thriving in an Agile Environment. Kathryn Poe Rocky Mountain Chapter Feb 16, 2012

DevOps in an Open Heterogeneous World Flint Brenton, CEO. November 2016

THE ROLE OF THE BUSINESS ANALYST IN A DEVOPS ENVIRONMENT DISCUSSION PAPER

Let s Talk About Being Agile

User-centered System Design. Agile

Software Engineering Part 2

Fundamentals of Agile Webinar. Copyright 2011 Coveros, Inc.. All rights reserved.

Management by Consensus

Agile/Lean & Safety: Perfect Match or Impossible Combination?

Introduction. Figure 1-1

Systems Analysis and Design 8 th Edition. Chapter 1 Introduction to Systems Analysis and Design

V Model material adapted from Steve Easterbrook. Waterfall Model material adapted from Steve Easterbrook. Lifecycle of Software Projects

Managing Successful Programmes (MSP ): A basic overview. Rod Sowden, Aspire Europe Ltd. AXELOS.com. The Stationery Office 2011

Agile Software Construction. This Course. Course information. Course Contents. Daisy: Software Engineering Agile Methods

Directing Agile Change

Solutions for higher performance! Agile. Methodologies. Key. Principles. Series-I

Introduction to Agile Software Development

A Literature Review on Agile Model Methodology in software Development

Agile Project need Agile Controls and Audit. Christopher Wright BSc(hon), CPFA, CISA, MBCS, MAPM Certified ScrumMaster,

Lecture 1. Topics covered. Rapid p development and delivery is now often the most important requirement for software systems.

The ABC of Agile Business Change. James Yoxall BCS 17 September, 2013

Tips for Success for a BA in an Agile Environment

Becoming Agile: A Grounded Theory of Agile Transitions in Practice

Transcription:

1. Which statement would NOT be a reasonable conclusion regarding the evolution of the Waterfall model? The Waterfall model is obsolete and no longer relevant today The Waterfall model added structure and discipline to a development process The Waterfall model became particularly important as a means of scaling large, complex projects By providing a way of systematically managing and tracking requirements all the way through the development process to final testing, the Waterfall process provided a way to significantly improve project quality over adhoc, unstructured development processes Explanation: The first answer is a false statement; therefore, it is the correct answer - The Waterfall model is not obsolete. It is still used in industries such as construction that are heavily plan-driven and require predictability and control over costs and schedule The second answer is a true statement; therefore, it is not the correct answer - Prior to the Waterfall model, there was a need for discipline and structure to improve project quality and improve the ability to scale large projects The third answer is a true statement; therefore, it is not the correct answer - without a more structured and disciplined way to manage large, complex development efforts it is difficult to scale a project The third answer is a true statement; therefore, it is not the correct answer - This statement is correct - the Waterfall model provides a way of ensuring "traceability" of requirements all the way through the project including testing and acceptance which will normally result in improved quality. 2. Joint Application Design (JAD) and Rapid Application Development (RAD) are examples of some of the approaches from the 1980's and 1990's that ultimately led to the development of Agile Explanation: JAD and RAD are two models that became popular in the 1980 s and 1990 s that ultimately influenced the development of Agile. 1

3. The Agile Manifesto was created in 2001 to synthesize the values and principles behind a number of different Agile approaches that had been developed up until that time Explanation: This statement is true Prior to the Agile Manifesto in 2001, there was a proliferation of different Agile methodologies that had evolved and the Agile Manifesto synthesized many of the basic values and principles that were common to those methodologies 4. An important Agile Manifesto value is that processes and tools are not consistent with an Agile approach Explanation: This statement is false. The Agile Manifesto value is Individuals and interactions over processes and tools and it s important to recognize that all of the value statements are meant to be relative statements and not absolutes. For that reason, it would be incorrect to conclude that processes and tools are not consistent with an Agile approach 5. Agile development puts an emphasis on creating an environment that is based on empowered teams in order to encourage innovation and creativity Explanation: This statement is true. An important reason for creating empowered teams is that it is essential for projects that require creativity and innovation 6. One of the major problems associated with an over-reliance on documentation is that it can inhibit normal communications Explanation: This statement is true. One of the major problems associated with an over-reliance on documentation is that it can inhibit normal communications 2

7. It is not possible to have a contract with a customer in an Agile environment Explanation: This statement is false. The Agile Manifesto Value is Customer Collaboration over contract negotiation ; however, it is important to recognize that all Agile Manifesto values are meant to be relative and not absolute. Therefore, it is very possible to have a contract with a customer in an Agile environment and the contract can be loosely-defined or tightly-defined. 8. It is always very important in an Agile project to define requirements in order to manage customer collaboration Explanation: This statement is false. The Agile Manifesto Value is Customer Collaboration over contract negotiation. Making that work typically requires a spirit of trust and partnership with the customer rather than relying heavily on well-defined detailed requirements. 9. An Agile approach emphasizes creating an environment that is designed to be responsive to changes in order to optimize the value of the product that is ultimately delivered to the customer Explanation: This statement is true. The Agile Manifesto Value is Responding to change over following a plan. That is one of the most important values in an Agile approach. 10. An important consideration with all Agile values is that they are intended to be relative statements and not absolutes and it requires judgment to interpret them in the context of the situation Explanation: This statement is true. A very important characteristic of all Agile Manifesto values is that they are intended to be relative statements and not absolutes and they have to be interpreted in the context of the situation. 3

11. Which Agile Manifesto Value would be most relevant to this situation: A Scrum Master insists on rigid compliance with a well-defined process for performing Scrum Explanation: The second answer is most relevant to this situation. Processes in an Agile environment are meant to be adaptive. Therefore, it is normal to adapt the processes to fit a given situation if necessary. 12. Which Agile Manifesto Value would be most relevant to this situation: A customer has requested a project team to submit a fixed-price bid on a large Request for Proposal (RFP) Explanation: The third answer is most relevant to this situation. If a customer has requested a fixed price bid on a request for proposal (RFP) an appropriate response might be to try to negotiate the situation with the customer to convince the customer that it might be better to enter into a more collaborative type of relationship. 4

13. Which Agile Manifesto Value would be most relevant to this situation: A customer realized in the middle of a project that what was being built will not really meet his needs and a very different solution is more appropriate; however, the new approach will significantly increase the cost and schedule for completing the effort Explanation: The fourth answer is most relevant to this situation In this situation, an appropriate response might be to make the customer and business sponsor aware of the impact of the change and if the customer and business sponsor agrees that it is the right thing to do, go ahead and implement the change. 5