CMGT/410 Project Planning and Implementation

CMGT410 Entire Class    CMGT/410 Entire Class NEW

 
CMGT/410 Project Plan Draft
CMGT/410 Agile vs. Waterfall
CMGT/410 Week 1 Project Plan Draft
CMGT/410 Week 1 Project Plan Draft

CMGT/410 WEEK 1

All Assignments listed for Week 1 are included in purchase!

 

Individual: Project Plan Draft

Includes Optioin #1: Project Plan Draft Excel Spreadsheet

Includes Option #2: Project Plan Draft Excel Spreadsheet

Includes Option #3: Project Plan Draft Excel Spreadsheet

Includes Option #1: Methodology Selection and Rationale Worksheet

Includes Option #2: Methodology Selection and Rationale Worksheet

Includes Option #3: Methodology Selection and Rationale Worksheet

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.

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—that is, an overall process and suggested documents and deliverables—that will guide project development from beginning to end. Some project methodologies are more appropriate for some types of projects than for others.

For this assignment, you will:

Choose a project methodology for two different projects based on project requirements, and explain why you chose each methodology for each project.
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® Excel® or, if you choose, another software application such as Microsoft® Project®.
To complete this assignment:

Read Agile Project Management and the PMBOK® Guide.

Answer the Methodology Selection and Rationale questions.

Brainstorm a 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.

Read the two linked examples of project plans implemented as Microsoft® Excel® spreadsheets, Example Plan A and Example 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.

Research additional project plan examples online.

Create a simplified project plan for your own brainstormed project that resembles the two linked examples.

Save your simplified project plan as a Microsoft® Excel® spreadsheet document.

Submit both your completed Methodology Selection and Rationale questions and your project plan draft (Microsoft® Excel® document).

 

 

Wk 1 Discussion - Agile vs. Waterfall

Includes THREE (3 Long Answers/Responses) to Discussion Question!

Post a total of 3 substantive responses over 2 separate days for full participation. This includes your initial post and 2 replies to other students. 
Due Thursday 
Respond to the following in a minimum of 175 words: 
 The waterfall project management model is often used for non-IT projects, while the Agile project management model is often used for IT projects.

  • Why is this case?
  • What differences between IT and non-IT projects make each more appropriate for a different project management model? Are there exceptions?
  • What drawbacks might occur from using the waterfall model for an IT project and the Agile approach for a non-IT project?

Discussion Questions

a)   What is the definition of a project?
b)   What is project management?  
c)   What are the advantages of following a methodology when developing an

        information system?
d)   What is the purpose of a project charter?
e)   Describe how the project’s MOV supports the development of the project’s

       scope, schedule, and budget.
f)    Why should a project be divided into phases?

 

Discussion Questions

a)  What is a scope statement?  What purpose does it serve?
b)  Why is it important to define the project's scope accurately and completely?
c)  Briefly describe scope creep.
d)  What is a statement of work? What purpose does it serve?
e)  What is a deliverable? What is the relationship between phases and deliverables?
f)   What is project kick-off meeting? What purpose does it serve?

 

 

CMGT/410 Documenting the Project Lifecycle
CMGT/410 Off-the-Shelf or Build in-House?
Well-written project documentation clarifies intent, documents decisions and results, and allows project managers to assess project progress
CMGT410 Documenting the Project Life Cycle

CMGT/410 WEEK 2

All Assignments listed for Week 2 are included in purchase!

 

Individual: Documenting the Project Life Cycle

Includes Option #1 Product Requirements doc & User Stories spreadsheet

Includes Option #2 Product Requirements doc & User Stories spreadsheet

Includes Option #3 Product Requirements doc

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.
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.
If you chose the waterfall methodology for your Week 1 Project Plan Draft assignment, create the following:
    •  A business requirements document, or BRD: Use the Business Requirements

        Template as the basis for your BRD.
    •  A work breakdown schedule, or WBS: Use the Work Breakdown Structure (WBS)

        Example document as the basis for your WBS.
Alternatively, if you chose the Agile methodology for your Week 1 Project Plan Draft assignment, create the following:
    • A product requirements document, or PRD: Read "Product Requirements

       Documents, Downsized" for assistance in creating this document.
    • User stories/scenarios and acceptance criteria: Review "Agile Requirements

        Snail: Feature to User Story to Scenario" for help in creating this document. Then

        use the Scenarios and COS tabs located in User Scenarios And Acceptance

        Criteria Example as the basis for your user stories/scenarios and acceptance

        criteria.
Submit your completed BRD and WBS, or your completed PRD and user stories / scenarios with acceptance criteria.

 

Learning Team: Project Charter & Business Requirements

For this team assignment, you will collaborate with your colleagues to create a project charter for an Agile development based on the Project Charter Template. 

To complete this learning team assignment: 

Review "The Project Charter, a Key Document" in Ch. 5, "Project Research and Technology Choice; Conflicts at the Start of Projects; Four Additional Project Delays; Initial Pitfalls," of The Complete Software Project Manager: Mastering Technology from Planning to Launch and Beyond

With your team members, write a project charter for a collaboratively brainstormed project appropriate for Agile development. Your team's completed charter should closely resemble the linked Project Charter Template and include the following: 

  • Project scope: For assistance in describing your project's scope, review Ch. 6, "Final Discovery; Project Definition, Scope, and Documentation," of The Complete Software Project Manager: Mastering Technology from Planning to Launch and Beyond, with special emphasis on the section titled, "The Scope Document".
  • A product requirements document (PRD) section consisting of multiple user stories: Review " Agile Requirements Snail: Feature to User Story to Scenario" if you need assistance designing user stories.
  • Acceptance criteria/conditions of satisfaction for each defined user story 

Submit the team assignment.

 

 

Wk 2 Discussion - Off-the-Shelf or Build in-House?

Includes THREE (3 Long Answers/Responses) to Discussion Question!

IT projects can be based on existing, off-the-shelf software that is customized to meet the needs of the project deliverables. Or, IT projects can be built from the ground up, in-house. Imagine you and your colleagues are consultants who have been asked to weigh in on the custom vs. off-the-shelf question at the beginning of an IT project at a Fortune 500 company.  

  • What are the benefits of choosing and customizing off-the-shelf software to meet your project’s needs vs. building the entire project in-house.
  • What are the drawbacks?

Consider cost, the impact on the in-house team’s development staff, the software’s ability to grow with future project requirements, and how the choice will affect project support and maintenance.

 

Supporting Activity Discussion Questions

a) What is a WBS? What purpose does the WBS serve?
b) What makes estimating an IT project challenging?
c) What can lead to inaccurate estimates? How can an organization improve the accuracy of estimating IT projects?
d) What is the impact of consistently estimating too low? Too high?
e) Why is counting lines of code (LOC) a popular method for estimating and tracking programmer productivity?  What are some problems associated with this method?

 

Supporting Activity Discussion Questions

a) What are phase exits, stage gates, and kill points? What purpose do they serve?
b) What is a business case? Why should an organization develop a business case?
c) Describe technical feasibility.
d) Describe the criteria that should be used to make a project selection decision.
e) Describe the balanced scorecard approach.

 

CMGT/410 Project Scheduling and Documentation
CMGT/410 Working through Project Hazards
CMGT/410 Create a Scrum Board
Learning Team Scrum Board

CMGT/410 Week 3

 

All Assignments listed for Week 3 are included in purchase!

 

Learning Team:   Create a Scrum Board

Includes Option #1 Scrum Spreadsheet

Includes Option #2 Scrum Spreadsheet

Includes Option #3 Scrum Spreadsheet

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 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.

Submit the team assignment.

 

 

Individual: Project Scheduling and Documentation

Includes Option #1 Powerpoint presentation

Includes Option #2 Powerpoint presentation

Includes Option #3 Powerpoint presentation

One of the most important documents in a project is the kickoff presentation. Because this document formally begins, or "kicks off," 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. 

For this assignment, you will create a kickoff presentation in Microsoft PowerPoint based on the draft project plan you created in the Week 1 Project Plan Draft individual assignment. 

To complete this assignment:

Review the "Kickoff Presentation" section in Ch. 9, "Communication; Project Communication Strategy; from Project Kickoff to Daily Meetings," of The Complete Software Project Manager: Mastering Technology from Planning to Launch and Beyond. 

Create an 8- to 9-slide project kickoff presentation in Microsoft® PowerPoint® similar to this Project 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:

  • A high-level project definition
  • Business case (a description of the business problem/opportunity the plan is designed to solve/exploit)
  • Project approach
  • Description of team members and roles
  • Project scope
  • Out of scope
  • Timeline
  • Budget and budget reporting
  • Risks, cautions, and disclaimers 

Submit your completed project kickoff presentation.

 

 

Wk 3 Discussion - Working Through Project Hazards

Includes THREE (3 Long Answers/Responses) to Discussion Question!

Post a total of 3 substantive responses over 2 separate days for full participation. This includes your initial post and 2 replies to other students. 
Respond to the following in a minimum of 175 words: 
In a perfect world, every project would be characterized by clear project requirements that never changed; motivated/capable team members; proven technologies; more than adequate budgets in terms of time, money, and resources; responsible/knowledgeable stakeholders; and seamless, effective communication so that when a problem arises, it is communicated and dealt with quickly. However, we do not live in a perfect world! 
In your opinion, which three of the five common project hazards described in the book have the potential to be the most costly? Explain why. 
Reply to at least 2 of your classmates who prioritized project hazards differently than you. Explain why you disagree with your peer. To persuade your peer to see your point of view, illustrate your position by describing an example situation from the book, from your own experience, or from an online case study. Be constructive and professional in your responses.

 

 

Supporting Activity Discussion Questions

1. What are the processes and key outputs of cost management?
2. Within cost estimating, what are the different estimating types?
3. What are some approaches used when budgeting?
4. What is the difference between cost/benefit analysis and break-even analysis?

 

Supporting Activity Discussion Questions

1. What is the difference between crashing and fast tracking a project’s schedule?

2. Why should the project manager ensure that the project resources are leveled?

3. Why should assumptions used in estimating be documented?

4. What is a baseline plan?

5. Define predecessor, successor and parallel activities.

 

Supporting Activity Discussion Questions

1. Why should a project manager be concerned with monitoring a project’s progress?

2. What is the purpose of a project communication plan? What kinds of things should this plan address?

3. What is quality?

4. What is the relationship between standards and metrics?

5. What is the purpose of change control?

6. How can a company protect data on corporate laptops? Why do more organizations choose not to protect such data? Do you expect this to become a legal requirement in the future? Explain why you think so.

 

CMGT/410 Handling a Project Crisis
CMGT/410 Scope Creep
You are a project manager. During testing, a business user identifies a problem: the tested version lacks a fundamental capability
CMGT/410 Handling a Project Crisis

CMGT/410 Week 4

All Assignments listed for Week 4 are included in purchase!

 

Individual: Handling a Project Crisis

Includes Option #1 Memorandum

Includes Option #2 Memorandum

Includes Option #3 Memorandum

Includes Option #4 Memorandum

Includes Option #5 Memorandum

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.

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.

You discuss the problem with the project architect, who suggests two alternatives:

  1. Tune the relational data queries and upgrade the relational database server.
  2. Move all of the data from the relational database to a Big Data repository, such as Hadoop.

As project manager, your task is to write a memo to the project sponsor in which you:

  • Succinctly outline the problem identified
  • Describe the two alternatives listed above
  • Articulate the cost of each alternative in terms of its impact to the schedule, cost, and functionality of the final deliverables
  • Recommend one alternative over the other based on those costs and schedule impacts

To complete this assignment:

Read the following articles to familiarize yourself with some of the differences between Big Data repositories and relational database management systems:

"NoSQL and Hadoop: Document-Based versus Relational Databases"
"What is Apache Hadoop?"
Write a 2- to 3-page memo that meets the requirements described above.

Cite any sources you include in APA format.

Save your work as a Microsoft® Word document.

Submit your assignment.

 

 

CMGT/410 WK4 Discussion - Scope Creep

Includes THREE (3 Long Answers/Responses) to Discussion Question!

Scope creep refers to the tiny, incremental change or addition of requirements to an already-defined project so that, for example, a project that began by trying to produce a single ham sandwich ended up trying to produce a three-course meal for 20 people. 
For this discussion, describe a time when scope creep happened on a project in which you were involved. The project you describe may be from work (such as being affected by an IT upgrade project), school (such as participating in a team assignment), or personal life (such as planning a wedding). 

  • Who was responsible for adding requirements?
  • Who was responsible for accepting them?
  • Were the additional requirements introduced early in the project process, or late?
  • What were the outcomes? That is, was the expanded scope implemented, or not?
  • Did the project come in over budget? Was it delayed? Was it cancelled? 

If you have never been involved in any type of project in which scope creep occurred, research specific causes of project scope creep and share at least two causes that are not listed in your textbook. Be sure to cite your sources in APA format.

 

Supporting Activity Discussion Questions

1.    What is the purpose of a contract?
2.    What is outsourcing? How does it relate to Project Procurement Management?
3.    What is offshoring or offshore outsourcing?
4.    Why is writing a good contract important for an outsourcing relationship?
5.    What are some hidden costs of outsourcing? Why is it important to consider these costs?

 

Supporting Activity Discussion Questions

1.    What qualities are required for a good project manager?
2.    Describe the five practices for exemplary leadership.
3.    What is emotional intelligence?
4.    What is the definition of ethics?
5.    Define culture.
6.    How can a project manager change, maintain or create culture?

 

CMGT/410 User Acceptance Testing
CMGT/410 Feature Requests
CMGT/410 Bugs vs. Feature Requests

CMGT/410 Week 5

All Assignments listed for Week 5 are included in purchase!

 

Learning Team: User Acceptance Testing

Includes Option #1

Includes Option #2

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—that 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.

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.

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.

To complete this assignment:

Read "Acceptance Criteria in Scrum: Explanation, Examples, and Template."

Review the following sections of Ch. 13, "Launch and Post-Launch: UAT, Security Testing, Performance Testing, Go Live, Rollback Criteria, and Support Mode," in The Complete Software Project Manager: Mastering Technology from Planning to Launch and Beyond:

"User Acceptance Testing: What It Is and When It Happens"
"Controlling UAT and 'We Talked About It in a Meeting Once,' Part Deux"
"Classifying UAT Feedback"
"Bugs"
"Not Working as Expected – The Trickiest Category"
"Request for Improvement"
"Feature Request"
"Conflict Resolution and Final Launch List"
As a group, complete the COS sheet portion of the linked UAT Plan Template. Note: Click theCOS tab that appears at the bottom of the spreadsheet to see the COS sheet. COS stands for Conditions of Satisfaction/Acceptance Criteria.

Save your collaboratively completed UAT plan template using a unique file name that does not include the string "Template".

Submit the team assignment.

 

Individual: Bugs vs. Feature Requests

Includes Option #1

Includes Option #2

Includes Option #3

Includes Option #4

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.

Read the following linked documents:

"Visual Studio - Manage Bugs": This article describes the process of tracking bugs in Visual Studio, a popular .NET development suite created by Microsoft®.
"What Is a Bug and Issue Tracking Tool?": This article describes the process of tracking bugs in Jira, a popular bug tracking and project management tool created by Atlassian.
Create a 3-page Microsoft® Word 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.

Your tracking process must include:

Description of software you propose using for bug tracking (in-house developed or third-party)
Description of issues that will be considered bugs (vs. feature requests)
Description of who will use the system to track bugs
Description of who will monitor the system, follow up with the requestor as necessary, and implement the bug fixes
Description of bug-related information (such as a unique tracking number, description, assignee, etc.) necessary to identify, fix, and log bugs
Submit your completed document.

 

Wk 5 Discussion - Feature Requests

Includes THREE (3 Long Answers/Responses) to Discussion Question!

All projects are perfect at the beginning—but few are perfect when they end. Sometimes, project managers gather descriptions of features that weren't included in the initial release of a product and slate them for inclusion into a "2.0" version of the deliverables. Imagine you have been asked to submit a feature request for the VitalSource application you use to read your textbook for this course.

  • What feature would you request?

Be sure to describe it in sufficient detail so that the VitalSource programmers could understand and implement your request. 
Reply to at least 2 of your classmates, explaining whether the request is clear and complete enough for you to understand how to implement the request if you were a programmer at VitalSource.

  • Has your colleague described the situation(s) in which the new feature should work?
  • How the feature should work? What the program should do if the feature does not/cannot work in a given instance?

If your colleague's request is not clear or complete, explain what information is lacking. Be constructive and professional in your responses.

 

 

Discussion Questions

1. What leads to uncertainty in an IT project?

2. What is project risk management?

3. What are the seven IT project risk management processes?

4. What is risk monitoring and control?  

 

Discussion Questions

1. You are asked to make a copy of a magazine article and include it in new software you are writing.  You see that the article has a copyright notice.  What is the best thing to do?

2. Your company is in competition to win a major project for the government of country X.  You are told that you must make a large payment to the foreign minister in order to be considered for the project.  What is the best thing to do?

3. You provide a project estimate for the project to the project sponsor.  The project sponsor is unhappy with the estimate, because the project sponsor thinks the price should be lower.  The project sponsor asks you to cut 15% off the project estimate.  What should you do?

4. What is wrong with the idea of just expecting people to adapt to a new system by compliance?

5. What are some best practices for measuring project success?