{"id":433562,"date":"2018-10-05T22:53:45","date_gmt":"2018-10-05T22:53:45","guid":{"rendered":"https:\/\/essaypaper.org\/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-lea\/"},"modified":"2018-10-24T08:42:23","modified_gmt":"2018-10-24T08:42:23","slug":"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-lea","status":"publish","type":"post","link":"https:\/\/www.benedictsol.com\/blogs\/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-lea\/","title":{"rendered":"Create a scrum board in Microsoft\u00ae Excel\u00ae 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."},"content":{"rendered":"
\n\n\n

CMGT 410 Week 1 Project Plan Draft<\/h2>\n

A project plan is a document created at the beginning of the project lifecycle that gives stakeholders and everyone else involved in a project a clear idea of what a project will entail in terms of effort, time, cost, and anticipated results.<\/p>\n

One of the things that must be identified before the project plan can be created is the methodology, or approach, the project manager plans to use to manage the project. Choosing a methodology is important because a methodology provides the framework\u2014that is, an overall process and suggested documents and deliverables\u2014that will guide project development from beginning to end. Some project methodologies are more appropriate for some types of projects than for others.<\/p>\n

For this assignment, you will:<\/p>\n

1. Choose a project methodology for two different projects based on project requirements, and explain why you chose each methodology for each project.<\/p>\n

2. Brainstorm your own project and create a draft simplified project plan for that project. You must indicate in your simplified project plan whether you intend to apply the Agile or waterfall methodology. You may create your simplified project plan using Microsoft\u00ae\u00a0Excel\u00ae\u00a0or, if you choose, another software application such as Microsoft\u00ae\u00a0Project\u00ae.<\/p>\n

To complete this assignment:<\/p>\n

Read\u00a0\u00a0Agile Project Management and the PMBOK\u00ae\u00a0Guide<\/i>\u00a0.<\/p>\n

Answer\u00a0the\u00a0Methodology Selection and Rationale\u00a0questions.<\/p>\n

Brainstorm\u00a0a project you would like to explore in this course. You may choose a project from your work experience, from a description of a project in your textbook or in an online reading, or a project that is brand new but that you think would improve a business process at work, at home, or at school.<\/p>\n

Read\u00a0the two linked examples of project plans implemented as Microsoft\u00ae\u00a0Excel\u00ae\u00a0spreadsheets,\u00a0Example Plan A\u00a0and\u00a0Example Plan B. You will be using these as guides in creating your own draft project plan. Notice especially the differences between these two examples in terms of length (overall and task length), structure of the work breakdown (iterative vs. non-iterative), and methodology.<\/p>\n

Research\u00a0additional project plan examples online.<\/p>\n

Create\u00a0a simplified project plan for your own brainstormed project that resembles the two linked examples.<\/p>\n

Save\u00a0your simplified project plan as a Microsoft\u00ae\u00a0Excel\u00ae\u00a0spreadsheet document.<\/p>\n

Submit\u00a0both your completed Methodology Selection and Rationale questions and your project plan draft (Microsoft\u00ae\u00a0Excel\u00ae\u00a0document).<\/p>\n<\/td>\n<\/tr>\n\n\n\n

CMGT 410 Week 2 Documenting the Project Lifecycle<\/h2>\n

Well-written project documentation clarifies intent, documents decisions and results, and allows project managers to assess project progress (and report it, as necessary, to project stakeholders) at every step of the project lifecycle.<\/p>\n

For this assignment, you will create two examples of project documentation that align with the Project Plan Draft assignment you completed in Week 1. The documentation you will create for this assignment aligns with the initiation and planning phases of a project.<\/p>\n

If you chose the waterfall methodology for your Week 1 Project Plan Draft assignment, create the following:<\/p>\n

\u00b7 A business requirements document, or BRD: Use the\u00a0Business Requirements Template\u00a0as the basis for your BRD.<\/p>\n

\u00b7 A work breakdown schedule, or WBS: Use the\u00a0Work Breakdown Structure (WBS) Example\u00a0document as the basis for your WBS.<\/p>\n

Alternatively, if you chose the Agile methodology for your Week 1 Project Plan Draft assignment, create the following:<\/p>\n

\u00b7 A product requirements document, or PRD: Read \u201cProduct Requirements Documents, Downsized\u201d for assistance in creating this document.<\/p>\n

\u00b7 User stories\/scenarios and acceptance criteria: Review \u201cAgile Requirements Snail: Feature to User Story to Scenario\u201d for help in creating this document. Then use the\u00a0Scenarios\u00a0and\u00a0COS\u00a0tabs located in\u00a0User Scenarios And Acceptance Criteria Example\u00a0as the basis for your user stories\/scenarios and acceptance criteria.<\/p>\n

Submit\u00a0your completed BRD and WBS, or your completed PRD and user stories\/scenarios with acceptance criteria.<\/p>\n<\/td>\n<\/tr>\n\n\n\n

CMGT 410 Week 3 Create a Scrum Board<\/h2>\n

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 \u201cstickies,\u201d each listing a task, posted beneath categories such as \u201cto do,\u201d \u201cin process,\u201d in testing,\u201d 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.<\/p>\n

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.<\/p>\n

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\u2014Microsoft\u00ae\u00a0Excel\u00ae\u2014to 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.<\/p>\n

To complete this learning team assignment:<\/p>\n

Review\u00a0the\u00a0Learning Team Scrum Board Example\u00a0spreadsheet. (Note:\u00a0Click the\u00a0Board\u00a0tab that appears at the bottom of the spreadsheet to see the scrum board example.)<\/p>\n

Create\u00a0a scrum board in Microsoft\u00ae\u00a0Excel\u00ae\u00a0format 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.<\/p>\n

Submit\u00a0the team assignment.<\/p>\n<\/td>\n<\/tr>\n\n\n\n

CMGT 410 Week 3 Project Scheduling and Documentation<\/h2>\n

One of the most important documents in a project is the kickoff presentation. Because this document formally begins, or \u201ckicks off,\u201d project development, it can only be created after the project has been planned, approvals have been obtained, and personnel are in place. A good kickoff presentation communicates succinctly to all attendees what needs to be accomplished to complete the project, in what order, and by whom. It sets expectations and, ideally, energizes project team members. The desired outcome of a project kickoff presentation is for team members to begin tackling the first defined project tasks and know whom to contact if they encounter delays.<\/p>\n

For this assignment, you will create a kickoff presentation in Microsoft\u00ae\u00a0PowerPoint\u00ae\u00a0based on the draft project plan you created in the Week 1 Project Plan Draft individual assignment.<\/p>\n

To complete this assignment:<\/p>\n

Review\u00a0the \u201cKickoff Presentation\u201d section in Ch. 9, \u201cCommunication; Project Communication Strategy; from Project Kickoff to Daily Meetings,\u201d of\u00a0The Complete Software Project Manager: Mastering Technology from Planning to Launch and Beyond.<\/p>\n

Create\u00a0an 8- to 9-slide project kickoff presentation in Microsoft\u00ae\u00a0PowerPoint\u00ae\u00a0similar to this\u00a0Project Kickoff sample template. The kickoff presentation you create should include details pertaining to the project you defined in the Week 1 Project Plan Draft assignment, including budget details as appropriate. Specifically, your presentation should include:<\/p>\n

\u00b7 A high-level project definition<\/p>\n

\u00b7 Business case (a description of the business problem\/opportunity the plan is designed to solve\/exploit)<\/p>\n

\u00b7 Project approach<\/p>\n

\u00b7 Description of team members and roles<\/p>\n

\u00b7 Project scope<\/p>\n

\u00b7 Out of scope<\/p>\n

\u00b7 Timeline<\/p>\n

\u00b7 Budget and budget reporting<\/p>\n

\u00b7 Risks, cautions, and disclaimers<\/p>\n

Submit\u00a0your completed project kickoff presentation.<\/p>\n<\/td>\n<\/tr>\n\n\n\n

CMGT 410 Week 4 H
\nandling a Project Crisis<\/h2>\n

You are a project manager. During testing, a business user identifies a problem: the tested version lacks a fundamental capability that, as it turns out, was never identified. This capability does not just represent a nice-to-have feature; it is integral to the IT deliverable functioning in the real world. You comb through your project management software, old emails, and meeting agendas, but you cannot find the functionality documented anywhere.<\/p>\n

As you dig into the problem, you realize that the new functionality the business user is asking for cannot be delivered given the underlying technology that was chosen for this project. The relational database identified in the project plan is simply too slow in reporting and data transfer to support the new functionality.<\/p>\n

You discuss the problem with the project architect, who suggests two alternatives:<\/p>\n

1. Tune the relational data queries and upgrade the relational database server.<\/p>\n

2. Move all of the data from the relational database to a Big Data repository, such as Hadoop.<\/p>\n

As project manager, your task is to write a memo to the project sponsor in which you:<\/p>\n

\u00b7 Succinctly outline the problem identified<\/p>\n

\u00b7 Describe the two alternatives listed above<\/p>\n

\u00b7 Articulate the cost of each alternative in terms of its impact to the schedule, cost, and functionality of the final deliverables<\/p>\n

\u00b7 Recommend one alternative over the other based on those costs and schedule impacts<\/p>\n

To complete this assignment:<\/p>\n

Read\u00a0the following articles to familiarize yourself with some of the differences between Big Data repositories and relational database management systems:<\/p>\n

\u00b7 \u201cNoSQL and Hadoop: Document-Based versus Relational Databases\u201c<\/p>\n

\u00b7 \u201cWhat is Apache Hadoop?\u201d<\/p>\n

Write\u00a0a 2- to 3-page memo that meets the requirements described above.<\/p>\n

Cite\u00a0any sources you include in APA format.<\/p>\n

Save\u00a0your work as a Microsoft\u00ae\u00a0Word document.<\/p>\n

Submit\u00a0your assignment.<\/p>\n<\/td>\n<\/tr>\n\n\n\n

CMGT 410 Week 5 User Acceptance Testing<\/h2>\n

User acceptance testing, or UAT, is a round of testing in which the users who are expected to use the system after it goes live exercise the system. UAT differs from quality assurance, or QA, testing in a very important way: In UAT, real users attempt to use the system-in-development in a realistic manner\u2014that is, the way they plan to use it after it goes live. In QA, technical people (who may or may not be familiar with how the system is actually going to be used in a business setting) exercise specific bits of functionality. Because of this difference in approach, UAT often exposes bugs that were not caught in QA. In addition, UAT allows users to feel confident that the system will work as they expect it to once it has been implemented, and to signal this confidence formally by signing off on the UAT.<\/p>\n

For this assignment, you will work with your team members to build a User Acceptance Test Plan for the team project (system) you defined collaboratively in Weeks 2 and 3.<\/p>\n

As part of this plan, you will create acceptance criteria for all user stories\/scenarios associated with this project. In other words, you will collectively generate user stories\/scenarios (i.e., brainstorm how users can reasonably be expected to use the system you defined) and then define each of the user stories\/scenarios you list as a bug, a function not working as expected, a request for improvement, or a feature request.<\/p>\n

To complete this assignment:<\/p>\n

Read\u00a0\u201cAcceptance Criteria in Scrum: Explanation, Examples, and Template.\u201d<\/p>\n

Review\u00a0the following sections of Ch. 13, \u201cLaunch and Post-Launch: UAT, Security Testing, Performance Testing, Go Live, Rollback Criteria, and Support Mode,\u201d in\u00a0The Complete Software Project Manager: Mastering Technology from Planning to Launch and Beyond:<\/p>\n

\u00b7 \u201cUser Acceptance Testing: What It Is and When It Happens\u201d<\/p>\n

\u00b7 \u201cControlling UAT and \u2018We Talked About It in a Meeting Once,\u2019 Part Deux\u201d<\/p>\n

\u00b7 \u201cClassifying UAT Feedback\u201d<\/p>\n

\u00b7 \u201cBugs\u201d<\/p>\n

\u00b7 \u201cNot Working as Expected \u2013 The Trickiest Category\u201d<\/p>\n

\u00b7 \u201cRequest for Improvement\u201d<\/p>\n

\u00b7 \u201cFeature Request\u201d<\/p>\n

\u00b7 \u201cConflict Resolution and Final Launch List\u201d<\/p>\n

As a group,\u00a0complete\u00a0the COS sheet portion of the linked\u00a0UAT Plan Template.\u00a0Note: Click the\u00a0COS\u00a0tab that appears at the bottom of the spreadsheet to see the COS sheet. COS stands for Conditions of Satisfaction\/Acceptance Criteria.<\/p>\n

Save\u00a0your collaboratively completed UAT plan template using a unique file name that does not include the string \u201cTemplate\u201d.<\/p>\n

Submit\u00a0the team assignment.<\/p>\n<\/td>\n<\/tr>\n\n\n\n

CMGT 410 Week 5 Bugs vs. Feature Requests<\/h2>\n

There is no such thing as a bug-free IT project. Because bugs are a fact of IT project life, IT project managers must articulate a process for identifying, tracking, and handling the bugs that will inevitably occur. In addition, because technical and business requirements change frequently, IT project managers must also plan to log and track requests for new features and functionality.<\/p>\n

Read\u00a0the following linked documents:<\/p>\n

\u00b7 \u201cVisual Studio \u2013 Manage Bugs\u201c: This article describes the process of tracking bugs in Visual Studio, a popular .NET development suite created by Microsoft\u00ae.<\/p>\n

\u00b7 \u201cWhat Is a Bug and Issue Tracking Tool?\u201c: This article describes the process of tracking bugs in Jira, a popular bug tracking and project management tool created by Atlassian.<\/p>\n

Create\u00a0a 3-page Microsoft\u00ae\u00a0Word document of a bug tracking process for the project you created in the individual assignments in Weeks 2 and 3. Be sure to differentiate between bugs and feature requests. For this assignment, you will only be tracking bugs.<\/p>\n

Your tracking process must include:<\/p>\n

\u00b7 Description of software you propose using for bug tracking (in-house developed or third-party)<\/p>\n

\u00b7 Description of issues that will be considered bugs (vs. feature requests)<\/p>\n

\u00b7 Description of who will use the system to track bugs<\/p>\n

\u00b7 Description of who will monitor the system, follow up with the requestor as necessary, and implement the bug fixes<\/p>\n

\u00b7 Description of bug-related information (such as a unique tracking number, description, assignee, etc.) necessary to identify, fix, and log bugs<\/p>\n

Submit\u00a0your completed document.<\/p>\n<\/td>\n<\/tr>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

CMGT 410 Week 1 Project Plan Draft A project plan is a document created at the beginning of the project lifecycle that gives stakeholders and everyone else involved in a project a clear idea of what a project will entail Read More …<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[144,16,145,146],"tags":[],"class_list":["post-433562","post","type-post","status-publish","format-standard","hentry","category-academic-papers","category-academic-writing","category-academic-writing-service","category-academy-management-assignment-help"],"_links":{"self":[{"href":"https:\/\/www.benedictsol.com\/blogs\/wp-json\/wp\/v2\/posts\/433562","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.benedictsol.com\/blogs\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.benedictsol.com\/blogs\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.benedictsol.com\/blogs\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.benedictsol.com\/blogs\/wp-json\/wp\/v2\/comments?post=433562"}],"version-history":[{"count":0,"href":"https:\/\/www.benedictsol.com\/blogs\/wp-json\/wp\/v2\/posts\/433562\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.benedictsol.com\/blogs\/wp-json\/wp\/v2\/media?parent=433562"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.benedictsol.com\/blogs\/wp-json\/wp\/v2\/categories?post=433562"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.benedictsol.com\/blogs\/wp-json\/wp\/v2\/tags?post=433562"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}