CMGT 410 education changes / sellfy.com - PowerPoint PPT Presentation

About This Presentation
Title:

CMGT 410 education changes / sellfy.com

Description:

CMGT 410 Assignment Week 1 Project Plan Draft CMGT 410 Assignment Week 2 Documenting the Project Lifecycle CMGT 410 Assignment Week 3 Create a Scrum Board CMGT 410 Assignment Week 3 Project Scheduling and Documentation CMGT 410 Assignment Week 4 Handling a Project Crisis CMGT 410 Assignment Week 5 User Acceptance Testing CMGT 410 Assignment Week 5 Bugs vs. Feature Requests – PowerPoint PPT presentation

Number of Views:8
Slides: 11
Provided by: shaja123

less

Transcript and Presenter's Notes

Title: CMGT 410 education changes / sellfy.com


1
CMGT 410 Experience Tradition/sellfy.com
2
CMGT 410 Experience Tradition/sellfy.com
  • CMGT 410 All Assignments (New Syllabus)
  • https//sellfy.com/p/fia8/
  •  
  • CMGT 410 Assignment Week 1 Project Plan
    Draft CMGT 410 Assignment Week 2 Documenting
    the Project Lifecycle CMGT 410 Assignment
    Week 3 Create a Scrum Board CMGT 410
    Assignment Week 3 Project Scheduling and
    Documentation

3
CMGT 410 Experience Tradition/sellfy.com
  • CMGT 410 Assignment Week 1 Project Plan Draft
  • https//sellfy.com/p/HUaq/
  •  
  •  
  •   
  • CMGT 410 Assignment Week 1 Project Plan DraftA
    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.

4
CMGT 410 Experience Tradition/sellfy.com
  • CMGT 410 Assignment Week 2 Documenting the
    Project Lifecycle
  • https//sellfy.com/p/4qxk/
  •  
  •  
  • CMGT 410 Assignment Week 2 Documenting the
    Project LifecycleWell-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 Assignment
    Week 1. The documentation you will create for
    this assignment aligns with the initiation and
    planning phases of a project.

5
CMGT 410 Experience Tradition/sellfy.com
  • CMGT 410 Assignment Week 3 Create a Scrum Board
  • https//sellfy.com/p/XB0A/
  •  
  •  
  • CMGT 410 Assignment Week 3 Create a Scrum
    BoardProjects 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 Assignment Week 2.

6
CMGT 410 Experience Tradition/sellfy.com
  • CMGT 410 Assignment Week 3 Project Scheduling and
    Documentation
  • https//sellfy.com/p/vxiV/
  •  
  •  
  • CMGT 410 Assignment Week 3 Project Scheduling and
    DocumentationOne 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.

7
CMGT 410 Experience Tradition/sellfy.com
  • CMGT 410 Assignment Week 4 Handling a Project
    Crisis
  • https//sellfy.com/p/u28v/
  •   
  • CMGT 410 Assignment Week 4 Handling a Project
    CrisisYou 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.

8
CMGT 410 Experience Tradition/sellfy.com
  • CMGT 410 Assignment Week 5 Bugs vs. Feature
    Requests
  •  https//sellfy.com/p/U2k5/
  •  
  •   
  • CMGT 410 Assignment Week 5 Bugs vs. Feature
    RequestsThere 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.

9
CMGT 410 Experience Tradition/sellfy.com
  • CMGT 410 Assignment Week 5 User Acceptance
    Testing
  • https//sellfy.com/p/ZLol/
  • CMGT 410 Assignment Week 5 User Acceptance
    TestingUser 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 mannerthat
    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.

10
CMGT 410 Experience Tradition/sellfy.com
Write a Comment
User Comments (0)
About PowerShow.com