CMGT 410 University of the Pacific Bugs vs Feature Requests Report There is no such thing as a bug-free IT project. Because bugs are a fact of IT project l

CMGT 410 University of the Pacific Bugs vs Feature Requests Report 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 Week 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 requester 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 Project Scheduling and
Documentation
John Consiglio
CMGT/410
5/18/2020
Charles Selin
•
Provide convenient access to inmate and staff files
•
Goals and
Objectives
Having central storage for on site files:
•
•
•
•
HR will be able to access all staff files
Granting access to those who need
Updating old antiquated systems
Having workstations rather then individual
non networked computers
Project Scope
In Scope:
Out of Scope:
Central database
Remote access
New networked workstations
Cloud computing and database building
Budget / Sponsor
•
•
Approximate Cost – $95,000
Project management of OCFS will oversee and approve all design and
sign off on completed project
Implementation Timeline
May 2020
1 Aug. – 24 Sep. 2020
Design – week of 12/13/2018
UAT – User Acceptance – 2 weeks/ training
•Needs
•Looking at current configuration
Sprints – 4 weeks
•Network design
•Workstation implementation
•Database
•Testing
Release – 2 weeks
13 June – 1 July 2020
24 Sep. – 2 Oct. 2020
•
Availability of resources:
•
Risk Factors
•
•
•
•
Available programmers for database design
needs
Available funds
Availability of sponsor
Not meeting the timeline
New technology
•
•
•
•
Choosing correct cloud computing software
Implementing security features
New workstations
Training on New O/S and DB systems
Project Team
Roles and
Responsibilities
[John Consiglio]
Project Manager
[Jane Doe]
Product Owner
[John Smith]
Developer UX
[John Doe]
Developer
DB/API
[Jane Smith]
Developer
Reporting
[Scott Smith]
Tester QA/UAT
Team/Stakeholder
Communications
•
•
•
•
Team meetings (weekly project management meeting)
Daily Stand up Meetings
Status reports
E-mail update

Purchase answer to see full
attachment