CTC/ITC 310 Program Management California State University Dominguez Hills First Exam Answer Key November 20, 2018 Instructor: Howard Rosenthal

Similar documents
2. True or false: In Scrum all the requirements for the project are known prior to the start of development.

CTC/ITC 310 Program Management California State University Dominguez Hills Final Exam Answer Key December 13, 2018 Instructor: Howard Rosenthal

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

Project Management CTC-ITC 310 Fall 2018 Howard Rosenthal

Agile Program Development. Agile Manifesto 9/3/2013. What is Agile Development? 12 Principles of Agile Development 1 of 4

Organizational Agility and How To Attain It

Criteria. Kanban. Scrum. Acceptance. Acceptance Criteria. Kanban. Scrum. Refinement. Agile Manifesto. Acceptance Test. Product Backlog.

Maureen Weverka & Kathy Burnham Mutual of Omaha. November 9, Mutual of Omaha Insurance Company. All Rights Reserved.

Part 1. Software engineering Facts. CSC 4181 Compiler Construction Software Engineering Lectures. What is software engineering? What is software?

approach to successful project

Chapter 01 - The Process The Process Application Process ACP Qualifications Scheduling Your Exam Rescheduling/Cancelling Fees

Achieving Resiliency with Agile Methods

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

Introduction to Agile and Scrum

Agile Essentials Track: Business Services

Co-founder and Managing Director of RADTAC Specialist in Agile and Iterative approaches since mid 80s Agile Alliance Founder Member in 2002

Agile Software Development in a Regulated Environment. Natalie Custer

Agile Projects 7. Agile Project Management 21

Lecture 5. Software Processes CSC 4700 Software Engineering. Software Development Processes. The software process

The Software Life Cycle

Acceptance Criteria. Agile. Details that indicate the scope of a user story and help the team and product owner determine done-ness.

Software Engineering Lecture 5 Agile Software Development

Processes and Life- Cycles. Kristian Sandahl

Agile Software Development:

Processes and Life- Cycles. Kristian Sandahl

Software Process. Overview

SAFe 4.0 Glossary. Scaled Agile Framework Terms and Definitions. English. VERSION 4.0.

Managing Projects of Chaotic and Unpredictable Behavior

Johanna Rothman Part II Design and Manage an Agile and Lean Project Chapter 5 Start Your Agile Project Right. Copyright 2017

Chapter 4 Document Driven Approach for Agile Methodology

Chapter 2 Objectives. Pfleeger and Atlee, Software Engineering: Theory and Practice (edited by B. Cheng) Chapter 2.

SAFe in a Nutshell SCALED AGILE FRAMEWORK

Agile Transformation In the Digital Age

Lecture 8 Agile Software Development

Businesses now operate in rapidly changing environment.

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

PMI Agile Certified Practitioner (PMI-ACP) Duration: 48 Hours

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

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

Boston University Metropolitan College. MET CS634 Agile Software Development

An Agile Projects Introduction Course #PMCurrent-1

Agile Certified Professional

This document is copyrighted, the distribution of this document is punishable by law.

Events. Artifacts. Roles. Product Owner Scrum Master Development Team. Sprint Sprint Planning Daily Scrum Sprint Review Sprint Retrospective

AGILE SOLUTIONS. Agile Basics

Scrum Intro What s in it for me?

Agile Easy Read Snippets - Book 1. Agile Snippets. David Geoffrey Litten Agile Primer

BA25-Managing the Agile Product Development Life Cycle

ARCHITECTING PROJECT MANAGEMENT for Enterprise Agility. Enable Organization with Agile using Tooling/Technology

CS314 Software Engineering Project Management

The Software Life Cycle

CS 5704: Software Engineering

AGILE methodology- Scrum

Sample Exam ISTQB Agile Foundation Questions. Exam Prepared By

Software Engineering & Project Management Engr. Abdul-Rahman Mahmood MS, PMP, MCP, QMR(ISO9001:2000)

Metodologías Agiles en E///

Chapter 3 Agile Software Development

Tuesday, October 25. Announcements

Can Your Proposal Process Be More Agile?

Course Title: Agile for Business Analysts

Chapter 3 Agile Software Development. Part 1b

Software Engineering Part 2

Organizational Matters

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

Introduction... 1 Part I: Understanding Agile... 7

Course Title: Agile for Business Analysts

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

Paul Gorans, Agile Competency Lead, IBM GBS Federal Project Management Symposium

Agile Surveillance Points

SWE 211 Software Processes

Agile at Scale -Beyond SAFe. John B Hudson, B.Sc., PMP, ACP, CSM, SPC

Sign up to mailing list Join Slack, teaching team is available. All links are on the course website Slides are uploaded there too

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

1. The Case for Agile 2. The Scrum Process 3. Scaling Scrum

A Guide to Critical Success Factors in Agile Delivery

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

Software Processes. With a focus on Agile/Scrum CPSC310 Software Engineering

Processes. Object Orientated Analysis and Design. Benjamin Kenwright

Project Manager's Role in Agile projects?

Agile Scrum Foundation Certification Training Brochure

Scrum Team Roles and Functions

Course Title: Planning and Managing Agile Projects

By: Ronny Trefftzs CSCI 5828: Foundations of Software Engineering Spring 2012 Professor: Kenneth Anderson

Improving Agile Execution in the Federal Government

Certified Scrum Master

Mike Vincent. mvasoftware.net

Copyright Intertech, Inc All Rights Reserved. May 18, 2011

Foundations of Software Engineering. Process: Agile Practices Michael Hilton

Agile at Mid-Scale. Al Shalloway. Introducing FLow for Enterprise Transformations (FLEX)

A Case Study. What, When, Why. Agile Systems Engineering. Project Objectives. How to accomplish this??? What is All at Once? Logistical Planning

It can be done. Agile at Scale

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

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

Experiential Education for Agile Software Engineering

The Faster Road to Innovation Why Workopolis Went Agile

Introduction to Disciplined Agile Delivery

Waterfall Vs. Agile PM

In-House Agile Training Offerings

Introduction to Software Engineering: Project Management ( Highlights )

QAIassist IT Methodology General Context

Transcription:

CTC/ITC 310 Program Management California State University Dominguez Hills First Exam Answer Key November 20, 2018 Instructor: Howard Rosenthal There are 30 questions on this exam. Each question is worth 4 points (Note. 9-10 and 24-25 are each worth 8 points total). This means that you can earn up to 20 extra credit points for this exam. Some answers can be answered in a few words, while others require a little more extensive writing. If more than one item is asked for, only give the number of answers asked for. Any list will be graded starting from the top. Number all questions. Answer the questions in order if possible. 1. Give three examples of project phases. Concept Development Feasibility Study Requirement Development Prototyping Architecture and Design Deployment Closure 2. List two advantages and two disadvantages of the Spiral Model. Advantages High amount of risk analysis. Good for large and mission-critical projects. Software is produced early in the software life cycle. Disadvantages Can be a costly model to use. Risk analysis requires highly specific expertise. Project s success is highly dependent on the risk analysis phase. 3. What is the key improvement in the V-Model model when compared to the classic Waterfall Model? Test Plans for each level are created in concert with the analysis and design, improving the chances for a smooth Acceptance Test. 4. List four additional factors that may be used in selecting the right life cycle. Total cost Duration Market Stability Technology Business Climate Number of departments affected Organizational environment 1

5. What is DevOps? DevOps is a culture which promotes collaboration between Development and Operations Team to deploy code to production faster in an automated & repeatable way 6. List any two reasons why DevOps is used. Faster to market DevOps allows Agile Development Teams to implement Continuous Integration and Continuous Delivery that helps them to launch products faster into the market DevOps reduces the time to market up to 50% through streamlined software delivery This is particularly the case for digital and mobile applications Predictability DevOps offers significantly lower failure rate of new releases Reproducibility Version everything so that earlier version can be restored anytime Maintainability Effortless process of recovery in the event of a new release crashing or disabling the current system Improved Quality DevOps helps the team to provide improved quality of application development as it incorporates infrastructure issues Reduced Risks DevOps incorporates security aspects in the software delivery lifecycle It helps in reduction of defects across the lifecycle. Resiliency The Operational state of the software system is more stable, secure, and changes are auditable Cost Efficiency DevOps offers cost efficiency in the software development process which is always an aspiration of IT companies' management Breaks larger code base into small pieces DevOps is based on the Agile programming method allowing for the breaking larger code bases into smaller and manageable chunks 7. What is a user story? Functional increments of work, usually created in concert with the customer, are called user stories. 8. What are personas? When the project calls for it - for instance when user experience is a major factor in project outcomes - the team crafts detailed, synthetic biographies of fictitious users of the future product: these are called "personas 2

9-10. List the four basic principles of 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 11. How are work assignments allocated in the Agile environment? Assigning work and getting the status of the work completed moves from the project manager to the team members The rationale behind this is that the Agile team is a self-organized group of highly skilled professionals, accountable for the work they commit to in a sprint. The team takes ownership and accountability for meeting the project and team goals. 12. What is the role of the team lead/scrum Master in an Agile environment? This role, called Scrum Master in Scrum or team coach or project lead in other methods, is responsible for facilitating the team, obtaining resources for it, and protecting it from problems. This role encompasses the soft skills of project management but not the technical ones such as planning and scheduling, activities which are better left to the team as a whole. 13. What is the role of the Product Owner in an Agile environment? The Product Owner, called on-site customer in XP and active stakeholder in AM, represents the stakeholders. This is the one person responsible on a team (or sub-team for large projects) who is responsible for the prioritized work item list (called a product backlog in Scrum), for making decisions in a timely manner, and for providing information in a timely manner. 14. List and describe the three key elements of a useful project charter. Vision The vision defines the Why of the project. This is the higher purpose, or the reason for the project s existence Also describes who benefits and how Mission This is the What of the project and it states what will be done in the project to achieve its higher purpose Success Criteria The success criteria are management tests that describe effects outside of the solution itself 15. List three questions asked by the team during an Agile retrospective. What worked well for us? What did not work well for us? What actions can we take to improve our process going forward? 3

16. Who owns the backlog in the Agile environment? The Product Owner 17. What is refactoring? Refactoring is improving code without adding new functionality. 18. List three benefits of the daily stand-up in Agile. The team can evaluate the progress on a daily basis and see if they can deliver as per the iteration plan Each team member informs all about his/ her commitments for the day It provides visibility to the team on any delay or obstacles 19. What is Scrum? Scrum is a single-team process framework used to manage product development The framework consists of roles, events, artifacts and rules that uses an iterative agile delivery approach to deliver working products within timeboxes of one month or less Scrum defines "a flexible, holistic product development strategy where a development team works as a unit to reach a common goal It challenges assumptions of the "traditional, sequential approach to product development, and enables teams to self-organize by encouraging physical colocation or close online collaboration of all team members, as well as daily faceto-face communication among all team members and disciplines involved 20. List three communications responsibilities of the Product Owner. Communication tasks of the Product Owner to the stakeholders include: Demonstrating the solution to key stakeholders who were not present at a sprint review Defining and announcing releases Communicating team status Organizing milestone reviews Educating stakeholders in the development process Negotiating priorities, scope, funding, and schedule; Ensuring that the product backlog is visible, transparent, and clear 21. List three responsibilities of the Scrum Master. The Scrum Master is accountable for removing impediments to the ability of the team to deliver the product goals and deliverables and is not a traditional team lead or project manager but acts as a buffer between the team and any distracting influences. Responsibilities include: Ensuring that the Scrum framework is followed Helping the Product Owner maintain the product backlog in a way that ensures the needed work is well understood so the team can continually make forward progress 4

Helping the team to determine the definition of done for the product, with input from key stakeholders Coaching the team, within the Scrum principles, in order to deliver high-quality features for its product Promoting self-organization within the team Helping the Scrum team to avoid or remove impediments to its progress, whether internal or external to the team Facilitating team events to ensure regular progress Educating key stakeholders in the product on Scrum principles Coaching the development team in self-organization and cross-functionality 22. What questions are answered by each team member during the daily Scrum? What did I complete yesterday that contributed to the team meeting our sprint goal? What do I plan to complete today to contribute to the team meeting our sprint goal? Do I see any impediment that could prevent me or the team from meeting our sprint goal? 23. What does the Kanban Board allow us to do? A Kanban board is a tool used to visualize work and optimize the flow of the work among the team. 24-25. What are the six primary feature-driven development (FDD) roles? Project manager Chief architect Development manager Chief programmer Class Owner and/or Domain expert 26. What are the outputs of the FDD when building a features list? The result of the process is the Features List which includes A list of subject areas For each subject area, a list of the business activities within that subject area For each business activity step, the feature to satisfy the step 27. List 2 reasons why FDD methodology differs from traditional Agile in preferring individual class ownership? There is someone responsible for the conceptual integrity of that class. As enhancements are made, the class owner ensures that the purpose and design of the class is not compromised There is an expert available to explain how a specific class works. This is especially important for complex or business-critical classes The class owner typically implements a required change faster than another developer that is not as familiar with the class 5

The class owner has something of his or her own that he or she can take personal pride in 28. List any three items in the design package in FDD? A covering memo, or paper, that integrates and describes the design package such that it stands on its own for reviewers The referenced requirements (if any) in the form of documents and all related confirmation memos and supporting documentation. The Sequence diagram(s) Design alternatives (if any) The object model with new/updated classes, methods and attributes The generated output for the class and method prologues created or modified by this design Calendar/To-Do task-list entries for action items on affected classes for each team member 29. What is a Scrum of Scrums. The Scrum of Scrums is a technique to scale Scrum up to large groups (over a dozen people), consisting of dividing the groups into Agile teams of 5-10 Each daily Scrum within a sub-team ends by designating one member as "ambassador" to participate in a daily meeting with ambassadors from other teams, called the Scrum of Scrums Depending on the context, ambassadors may be technical contributors, or each team's Scrum Master, or even managers of each team 30. Describe systems wide thinking in the SAFe environment. Systems wide thinking is a holistic approach to analysis that focuses on the way that a system's constituent parts interrelate and how systems work over time and within the context of larger systems The systems wide thinking approach contrasts with traditional analysis, which studies systems by breaking them down into their separate elements. Systems wide thinking can be used in any area of research and has been applied to the study of medical, environmental, political, economic, human resources, and educational systems, among many others System wide thinking Assumes variability and changes, so preserve options Builds incrementally using an Agile methodology Bases milestones on objective evaluation of previously developed systems Visualizes and limit work in progress Unlocks and motivate workers (we discuss this in a later lesson) Decentralizes decision making 6