CKPM 217-S2023-Assignment 2-updated 13June2023

pdf

School

Toronto Metropolitan University *

*We aren’t endorsed by this school

Course

217

Subject

Computer Science

Date

Jan 9, 2024

Type

pdf

Pages

Uploaded by Jheblack

Assignment #2 1 | P a g e Course: Agile Project Management Code: CKPM 217 DA0 S2023 Instructor: Jamal El Ali Email: jelali@torontomu.ca Due Date: Sunday 16 Jul 2023, 11:55 pm Overview of Assignments: Assignment 2 will be completed by the same group you worked with in Assignment #1. This assignment is to be submitted using the digital drop box. The digital drop box is under the "Assessment" tab in the D2L platform. The assignments are due at 11:55 pm Eastern Time on the due date. As a group, remember to select one member in your group to submit your work on the due date. If, for some reason, you cannot meet the assignment deadline, please make arrangements with your instructor before the due date to avoid late penalties. There will be a Peer Evaluation at the end of each assignment to comparatively rate your group members based on your perceived contribution – this will provide the instructor with information on any members that went significantly above or below the average contribution. Evaluation: 25% of the Final Grade Description Assignment #2: Following your group's proposal for assignment #1, your project group will be selected to deliver the Agile Project Management services to the client to address the issues. As part of Agile Project Management service delivery, your project team is required to conduct detailed planning to ensure the client organization can deliver the product. The planning paper/presentation should cover the following key areas: 1. The vision statement for the product 2. Sequential roadmap for product delivery 3. Ten user stories (sample number of user stories for this exercise) 4. Estimation of the ten user stories 5. Release Plan 6. Sprint backlog Assignment Format: You can submit your assignment using an MS Word document or a PowerPoint presentation format.

Assignment #2 2 | P a g e Case Description: Impending Catastrophe of UltraFund • UltraFund is one of the largest fund management companies in the world. • Its innovative funds attract investors more than the funds at any other organization. • By 1997, Charles Schwab, eTrade, and other financial companies had revolutionized stock trading. • Customers could now manage their fund accounts, buy and sell stocks and play the margins without the assistance of stockbrokers. • The Internet and mobile technology have enabled this functionality. • Unfortunately, UltraFund had fallen behind this revolution. • Its technology organization was large, bureaucratic, and cumbersome. • To make matters worse, they implemented CMM level 3 last year. • If incorrectly implemented, these practices can increase bureaucracy as they had at UltraFund. • UltraFund explored ways to enable new technologies that could manage customer transactions. • They landed on developing a sophisticated workflow system (XFlow) from the licensed source code of a commercial workflow product internally. • The XFlow engineering team customized the product to meet UltraFund's needs, and it became central to UltraFund's information and workflow. • The engineering team in Salt Lake City enhanced and maintained XFlow for UltraFund companies worldwide. • Given the internal success of XFlow, the engineering team planned to sell it to other companies. • This decision created tension between the engineering group and internal customers. • The engineering group prioritized enhancements that made the product more commercially viable, while the internal customers prioritized bug fixes that would solve their internal operational problems. • Over several years the two groups grew distrustful of each other, and several of the larger business units at UltraFund started investigating the possibility of replacing XFlow. • If the internal customers implemented other workflow systems, interfaces would have to be built to accommodate them, and the UltraFund workflow would become less seamless. • Also, losing some internal customers would hurt the remaining internal customers by decreasing the funds available to enhance and sustain XFlow. • This was the start of a potential catastrophe at UltraFund.

Assignment #2 3 | P a g e Tips and Templates: This section provides you with tips on where you will find information in your textbook that can help you create assignment #2. All the artifacts you need are derived directly from your course textbook (Layton, M.C. & Ostermiller, S.J., (2020). Agile Project Management for Dummies . John Wiley & Sons, Inc.) 1. Product Vision Statement Template - Refer to pages 165 – 170 for more information on creating a vision statement for your product. Below is a template that helps guide you through creating a vision statement. Your product vision statement should identify the future state of your product. When creating a vision statement, think of answers to each point below. Once you have identified the answers, string them into a simple sentence or two and refine them. Your final vision statement should be an "elevator pitch." 2. Product roadmap - Refer to pages 171 – 182 for more information on creating a product roadmap. Your product roadmap should cover the below four key areas: I. Identify product requirements and add them to the roadmap II. Arrange the product requirements into logical groups a. TIP: Remember: at this level, you only work at the Epic level. You can organize the features into themes (see page 176, Figure 9-6 of your text) III. Estimate requirement effort at a high level and prioritize the product's requirements (see pages 176 – 178 of your text) IV. Envision high-level timeframes for the groups on the roadmap (see page 179 of your text) 3. Create User Stories – Create ten user stories using the product roadmap and epics noted. Refer to pages 184 – 192 for more information on creating user stories. Remember that this is only a sample of the user stories for the purposes of this assignment. These ten user stories won't cover your entire project. 4. Estimating – Estimate the ten user stories in step #3 and provide some rationale for your estimation. Please refer to pages 192 - 196 of your course textbook for estimation techniques. 5. Release Plan – Create a release plan for your project. Refer to pages 197 - 205 on how to create a release plan. 6. Spring backlog – Determine the length of sprints for your project and then create a sprint backlog for the first sprint. Refer to pages 205 - 213 on how to create a sprint backlog. For: <Target Customer> Who: <needs> The: <Product Name> Is a: <Product category> That: <Product benefit, reason to buy> Unlike: <competitors> Our Product: <differentiation/value proposition>

Your preview ends here

Eager to read complete document? Join bartleby learn and gain access to the full version

Access to all documents
Unlimited textbook solutions
24/7 expert homework help

Assignment #2 4 | P a g e Assignment Rubric: # Assignment #2 Rubric Mark Instructor Comments 1 Vision Statement 5 2 Product Roadmap 15 3 10 User Stories 10 4 Estimating 10 user stories 5 5 Release plan 5 6 Sprint Backlog 5 7 Completeness, format, teamwork (if applicable), spelling, grammar 5 TOTAL /50 NOTE: • Since the case is relatively high-level, you will need to make some assumptions to complete this assignment. • The completed project proposal should be 6 to 8 pages in length if using MS Word or 10 to 15 slides if using PowerPoint presentation format. • As this is a university-level course, the assignments are designed to promote critical thinking. The description of the case itself may seem somewhat confusing. Apply the knowledge and skills acquired from this course and take a pragmatic approach to apply the agile principles to complete this assignment. • The assignment covers most (not all) of the key aspects of an Agile project • Be creative and innovative! Reference Text: Layton, M.C. & Ostermiller, S.J., (2020). Agile Project Management for Dummies . John Wiley & Sons, Inc. Good luck with your final assignment!

Related Documents

Copyy of CSE 300 Resource Review.pdf

CMPSC_461_Fall_2023_Assignment_1_solution.pdf

c09.docx

INTL433_Progress Assignment_Pt1.pdf

INTL433_Final Assignment_Pt1.pdf

Guided Practice - Troubleshooting_chamel6755.docx

CharleneMelvin-5.1 ClassAcivity CIS106.docx

Recommended textbooks for you

Programming with Microsoft Visual Basic 2017

Computer Science

ISBN:9781337102124

Author:Diane Zak

Publisher:Cengage Learning

COMPREHENSIVE MICROSOFT OFFICE 365 EXCE

Computer Science

ISBN:9780357392676

Author:FREUND, Steven

Publisher:CENGAGE L

Np Ms Office 365/Excel 2016 I Ntermed

Computer Science

ISBN:9781337508841

Author:Carey

Publisher:Cengage

Microsoft Visual C#

Computer Science

ISBN:9781337102100

Author:Joyce, Farrell.

Publisher:Cengage Learning,

CMPTR

Computer Science

ISBN:9781337681872

Author:PINARD

Publisher:Cengage

New Perspectives on HTML5, CSS3, and JavaScript

Computer Science

ISBN:9781305503922

Author:Patrick M. Carey

Publisher:Cengage Learning

SEE MORE TEXTBOOKS

Recommended textbooks for you

Programming with Microsoft Visual Basic 2017
Computer Science
ISBN:9781337102124
Author:Diane Zak
Publisher:Cengage Learning
COMPREHENSIVE MICROSOFT OFFICE 365 EXCE
Computer Science
ISBN:9780357392676
Author:FREUND, Steven
Publisher:CENGAGE L
Np Ms Office 365/Excel 2016 I Ntermed
Computer Science
ISBN:9781337508841
Author:Carey
Publisher:Cengage
Microsoft Visual C#
Computer Science
ISBN:9781337102100
Author:Joyce, Farrell.
Publisher:Cengage Learning,
CMPTR
Computer Science
ISBN:9781337681872
Author:PINARD
Publisher:Cengage
New Perspectives on HTML5, CSS3, and JavaScript
Computer Science
ISBN:9781305503922
Author:Patrick M. Carey
Publisher:Cengage Learning