EBM 680 Task 2

khairul30

EBM680-Task2.docx

Home >Computer Science homework help >EBM 680 Task 2

EBM680 – Task 2

Task 1:

1. Analyze case study, Agile at Lego at: https://www.infoq.com/news/2017/09/agile-lego/

2. Analyze case study, Agile Delivery at British Telecom at http://www.methodsandtools.com/archive/archive.php?id=43

To Do:

· Write up your analysis of the two case studies in APA 7th format. Refer to specific issues in the case in your analysis. The papers should devote 2-3 pages per case study.

Task 2:

To Do: Based on the project idea submitted on Task 1

1. Submit the following 3 documents

a. scope statement,

b. communications management plan,

c. project report here

PLEASE REFER TO THE TEMPLATES BELOW:

Scope Statement (Version xx)

Project Title:

Date: Prepared by:

Project Justification:

Product Characteristics and Requirements:

Product User Acceptance Criteria:

Summary of Project Deliverables

Project management-related deliverables: business case, charter, team contract, scope statement, WBS, schedule, cost baseline, status reports, final project presentation, final project report, lessons-learned report, and any other documents required to manage the project.

Product-related deliverables: research reports, design documents, software code, hardware, etc.

Out of Scope

Everything not specifically documented as in scope is explicitly out of scope. In particular the following is out of scope for this project:

Communication Management Plan Version 1.0

Date

Project Name:

1. Stakeholder communications requirements:

2. Communications summary:

Stakeholders	Communications Name	Delivery Method/Format	Producer	Due/Frequency
Project steering committee	Weekly status report	Hard copy and short meeting	Kristin Maur	Wed. mornings at 9 AM
Sponsor and champion	Monthly status report	Hard copy and short meeting	Kristin Maur	First Thursday of month at 10 AM
Affected employees	Project announcement	Memo, e-mail, intranet site, and announcement at department meetings	Lucy Camerena and Mike Sundby	July 1, 2007
Project team	Weekly status report	Short meeting	All team members	Tues. afternoons at 2:00.

3. Comments/Guidelines:

4. Escalation procedures for resolving issues:

5. Revision procedures for this document:

6. Glossary of common terminology:

Project Report includes the following:

Student submits all of the required elements: (Project Report)

· • the project selected,

· • why you are doing this project,

· • what your main deliverables will be,

· • how you will measure success,

· • a summary of communication thus far with the client,

· • scope statement (activity 1),

· • team charter (see sample on p. 203 in Schwalbe)

· • communication plan (activity 2),

· • high level milestones, and

· a brief summary of the type of project management you will use (agile, waterfall, Kanban).

Rubrics:

Task 1

Agile Case Studies

Submission is a complete analysis, not just a summary, of the two case studies including a section that compares/contrasts the Agile implementations described. Analyses should include the student’s opinions on what went well and what did not.

Task 2 (a,b,c)

a. Scope statement demonstrates a complete

understanding of the concept of scope. It is submitted using one of the templates provided and shows a continuation of the project from the Business Case to the Project Charter and is further refined in the Scope Statement.

Specific elements:

· Product deliverables identified

· Acceptance criteria identified for the products

· Requirements for the deliverables

· Clear definition of in-scope versus out-of-scope.

b. Communication Plan

Submitted using one of the acceptable communications management plan templates from the library. Completely fills out the communication plan grid to

include at least 3 types of project communications, the audience, the medium, the owner, and the frequency of each communication.

c. Student submits all of the required elements: (Project Report)