coursework-banner

GCU MGT641 Agile Project Management Week 3 Assignment

GCU MGT641 Agile Project Management Week 3 Assignment

MGT641 Agile Project Management

Week 3 Assignment  

CLC: High Level Analysis

This is a CLC.

Now that a vision has been established for the project, your team will complete a High Level Analysis (HLA) to articulate the project idea, map the project’s design, and forecast a preliminary schedule. While an HLA can be a detailed requirements document when complete, your team will produce only selected parts of an HLA, including a use case diagram, a general workflow diagram, and the first version of your product backlog.

Use Case Diagram: The use case diagram should identify the actors, actions, systems, and processes involved in delivering value to end users. For example, if your team is responsible for developing a new software product, your use case diagram should visually represent all of the interactions among the people, processes, and systems required to deliver the software to end users. The ultimate goal of the use case diagram is to articulate the team’s understanding of what the product owner wants and what the requirements are. Keep in mind, since this is part of a High Level Analysis, the diagram need only provide an overview of major operations and interactions. The diagram will be used to further break down project requirements in the workflow and backlog.

General Workflow Diagram: The general workflow diagram should break down the workflow for completing the major milestones in the project. Using your use case diagram, map the project’s progression to demonstrate the order in which major steps in the project should be undertaken. This provides all team members with a shared understanding of the project’s scope and direction.

Product Backlog: Complete the first version of your product backlog using the attached “Product Backlog” template. The product backlog is the comprehensive and prioritized list of all of the features for your product. The backlog is a living document in that features may be added, deleted, or reprioritized as the product owner demands new features or as there are shifts in priorities as the project develops. The backlog is also used to plan your team’s sprints. Try to make your backlog as comprehensive as possible at this point; however, be prepared to revise and add to it as you work through your project and learn more about what it requires.

Note on Diagramming Tools: You are not required to use a specific tool to create your diagrams. Use case and workflow diagrams can be made in Microsoft Visio or with the drawing tools in Word. There are also several diagramming tools available on the Internet (e.g., Smartdraw.com, Gliffy.com, and draw.io). Some are open source or offer free trials. Investigate the saving and sharing options when choosing a tool. For example, some tools only save to PDFs, which are not editable. You are encouraged to investigate your options and select what works best for your team. You must be able to save and submit or otherwise share your diagram with the instructor.

APA style is not required, but solid academic writing is expected.

This assignment uses a scoring guide. Please review the scoring guide prior to beginning the assignment to become familiar with the expectations for successful completion.

You are not required to submit this assignment to LopesWrite.