How to create a scrum board

Projects that conform to the Agile methodology often use something called a scrum board. You can think of a scrum board as a digital whiteboard containing yellow "stickies," each listing a task, posted beneath categories such as "to do," "in process," in testing," and so forth. Using a scrum board in this way allows all project members to see where important tasks are in the overall project process quickly and easily.

For this learning team assignment, you will collaborate with your team members to create an Agile scrum board based on the project charter you created with your team in Week 2.

Note that in an industry situation, you would most likely use a specialized software tool to manage your scrum board such as Jira, Rally, Asana, or Basecamp. However, in this course, you will be using a tool that you may already be familiar with—Microsoft® Excel®—to create your scrum board and other deliverables. It is the organization and assignment of tasks that is important about a scrum board, not the specific software tool you use to create and manage the scrum board.

To complete this learning team assignment:

Review the Learning Team Scrum Board Example (attached) spreadsheet. (Note: Click the Board tab that appears at the bottom of the spreadsheet to see the scrum board example.)

Create a scrum board in Microsoft® Excel® format similar to the linked example. The scrum board you create should align with the project charter you created in the Week 2 Project Charter learning team assignment. Be sure your finished scrum board incorporates a project budget.

C:\Users\djshirey\OneDrive - University of Phoenix\F_Drive\Style Guides\UPX Logos\Horizontal format\UOPX_Sig_Hor_Black_Medium.pngProject Charter Template
1.0 Project Identification
Name

Android Customer Relationship Management System

Description

Design, develop, and implement the android customer relationship management app

Sponsor

Project Manager

Project Team Resources

2.0 Business Reasons for Project
· To improve customer relationship services

3.0 Project Objectives (Purpose)
· To develop tools, guidelines, and support for customer service department

4.0 Project Scope
· In scope:

· Cloud-based web server infrastructure to host the android app

· Development of android relationship management system app

· Out of scope:

· It is exclusive of local test server for Quality Assurance

5.0 Requirements – User Stories
User Story

Description

Balance

“As I want to so that ”

Reporting an erratic deduction

“As I want to so that ”

Checking status

“As I want to so that ”

6.0 Milestone Dates
Item

Major Event/Milestone

Date

1.

Developing the web

6/20/2019

2.

Development of the app’s prototype

7/20/2019

3.

Networking the information across various departments

8/20/2019

4.

Implementing the system and informing the stakeholder groups

9/5/2019

6.

Website the application

9/30/2019

7.

Evaluation, consultations, lessons learned

10/30/2019

7.0 Risks
Severity

Description

Moderate

Availability of the required resources such as appropriate policies

Extremely high

Compatibility issues due to fast rate of advancement of android systems

Low

Issue with deadlines

8.0 Project’s Acceptance/COS (Condition of Satisfaction)
· “Given when then ”

9.0 Project’s Budget
· Cloud-based web site - $25,000

· Development:

· Bespoke App- $170,000

· Off-the-Shelf app - $22,000

10.0 Sign-Off
Project Sponsor

Date