Question

In the Week 1 Lesson Video, you were introduced to the team at Getta Byte Software. Your assignment this week is to discuss the billing project charter and submit a one- to two-page paper. Consider what additional risks, assumptions, or requirements Getta Byte should include in this charter.

Getta Byte Software—The Project Scope

We need a new billing system.

Why?

The one we have works fine.

It's manual, time-consuming, and inaccurate.

There is that...

So, it has to be automated, fast, and accurate.

An online system

Easy data entry

Dynamic updates to receivables

It should save us 25% in labor per month.

We need to work with a bunch of people.

CEO, CFO, Finance, Billing, Customer Service

How will we know if it is a successful system?

Billing cycles are reduced by 30%

We must do the first pilot by September 1.

That means development and testing is done by August 15.

Final release will be complete on September 10.

If we are able to generate reports dynamically...

Speed up transactions and response time...

We'll be golden!

We only have $250,000 to spend on this project.

What if while we are replacing the system, we have network issues?

There is a risk in data transfer from our paper records to the new system.

That budget is going to be a challenge—a real constraint.

We have to assume that our most of our current customer data are correct.

We won't be able to do anything with accounts receivable.

We won't be able to change our financial system of record, either except to interface.

I think that's all I need for a charter.

The End

In the Week 1 Lesson Video, you were introduced to the team at Getta Byte Software. Your assignment this week is to discuss the billing project charter and submit a one- to two-page paper. Consider what additional risks, assumptions, or requirements Getta Byte should include in this charter.

Getta Byte Software—The Project Scope

We need a new billing system.

Why?

The one we have works fine.

It's manual, time-consuming, and inaccurate.

There is that...

So, it has to be automated, fast, and accurate.

An online system

Easy data entry

Dynamic updates to receivables

It should save us 25% in labor per month.

We need to work with a bunch of people.

CEO, CFO, Finance, Billing, Customer Service

How will we know if it is a successful system?

Billing cycles are reduced by 30%

We must do the first pilot by September 1.

That means development and testing is done by August 15.

Final release will be complete on September 10.

If we are able to generate reports dynamically...

Speed up transactions and response time...

We'll be golden!

We only have $250,000 to spend on this project.

What if while we are replacing the system, we have network issues?

There is a risk in data transfer from our paper records to the new system.

That budget is going to be a challenge—a real constraint.

We have to assume that our most of our current customer data are correct.

We won't be able to do anything with accounts receivable.

We won't be able to change our financial system of record, either except to interface.

I think that's all I need for a charter.

The End

In the Week 1 Lesson Video, you were introduced to the team at Getta Byte Software. Your assignment this week is to discuss the billing project charter and submit a one- to two-page paper. Consider what additional risks, assumptions, or requirements Getta Byte should include in this charter.

Getta Byte Software—The Project Scope

We need a new billing system.

Why?

The one we have works fine.

It's manual, time-consuming, and inaccurate.

There is that...

So, it has to be automated, fast, and accurate.

An online system

Easy data entry

Dynamic updates to receivables

It should save us 25% in labor per month.

We need to work with a bunch of people.

CEO, CFO, Finance, Billing, Customer Service

How will we know if it is a successful system?

Billing cycles are reduced by 30%

We must do the first pilot by September 1.

That means development and testing is done by August 15.

Final release will be complete on September 10.

If we are able to generate reports dynamically...

Speed up transactions and response time...

We'll be golden!

We only have $250,000 to spend on this project.

What if while we are replacing the system, we have network issues?

There is a risk in data transfer from our paper records to the new system.

That budget is going to be a challenge—a real constraint.

We have to assume that our most of our current customer data are correct.

We won't be able to do anything with accounts receivable.

We won't be able to change our financial system of record, either except to interface.

I think that's all I need for a charter.

The End

In the Week 1 Lesson Video, you were introduced to the team at Getta Byte Software. Your assignment this week is to discuss the billing project charter and submit a one- to two-page paper. Consider what additional risks, assumptions, or requirements Getta Byte should include in this charter.

Getta Byte Software—The Project Scope

We need a new billing system.

Why?

The one we have works fine.

It's manual, time-consuming, and inaccurate.

There is that...

So, it has to be automated, fast, and accurate.

An online system

Easy data entry

Dynamic updates to receivables

It should save us 25% in labor per month.

We need to work with a bunch of people.

CEO, CFO, Finance, Billing, Customer Service

How will we know if it is a successful system?

Billing cycles are reduced by 30%

We must do the first pilot by September 1.

That means development and testing is done by August 15.

Final release will be complete on September 10.

If we are able to generate reports dynamically...

Speed up transactions and response time...

We'll be golden!

We only have $250,000 to spend on this project.

What if while we are replacing the system, we have network issues?

There is a risk in data transfer from our paper records to the new system.

That budget is going to be a challenge—a real constraint.

We have to assume that our most of our current customer data are correct.

We won't be able to do anything with accounts receivable.

We won't be able to change our financial system of record, either except to interface.

I think that's all I need for a charter.

The End

In the Week 1 Lesson Video, you were introduced to the team at Getta Byte Software. Your assignment this week is to discuss the billing project charter and submit a one- to two-page paper. Consider what additional risks, assumptions, or requirements Getta Byte should include in this charter.

Getta Byte Software—The Project Scope

We need a new billing system.

Why?

The one we have works fine.

It's manual, time-consuming, and inaccurate.

There is that...

So, it has to be automated, fast, and accurate.

An online system

Easy data entry

Dynamic updates to receivables

It should save us 25% in labor per month.

We need to work with a bunch of people.

CEO, CFO, Finance, Billing, Customer Service

How will we know if it is a successful system?

Billing cycles are reduced by 30%

We must do the first pilot by September 1.

That means development and testing is done by August 15.

Final release will be complete on September 10.

If we are able to generate reports dynamically...

Speed up transactions and response time...

We'll be golden!

We only have $250,000 to spend on this project.

What if while we are replacing the system, we have network issues?

There is a risk in data transfer from our paper records to the new system.

That budget is going to be a challenge—a real constraint.

We have to assume that our most of our current customer data are correct.

We won't be able to do anything with accounts receivable.

We won't be able to change our financial system of record, either except to interface.

I think that's all I need for a charter.

The End

Questions :

x | Ψ Week 1: Lesson: Project Manage DeVry University + ::: https://lms.devry.edu/Ims/Cours x С 0 https://lms.devry ual/interactives/DVU/MGMT404 Wk1_ProjectCharter DragDrop/index.html Apps Top Interview Quest... New Tab G Desde 1992 en la ci.. G hydraulic cylinders.. Getta Byte Project Charter Using the Project Charter titles below, drag each title to match its correct description Billing System Implementation Project Name Replace current billing system with online system. tomated, fast and accurate Easy data entry Dynamic updates to receivables Save 25% in labor per month Objectives Current system is manual, time-consuming and inaccurate Business Need Development and testing done by August 15 First pílot done by September 1 Final release on September 10 Milestones $250,000 Budget Billing cycles reduced by 30% Dynamic report generation peed up transactions and response time User Acceptance Criteria High Level Assumptions c High Level Constraints Budget Exclusions Risks Key Stakeholders Current customer data is correct No upgrade to accounts receivable system No change to financial system of record Reset Network issues during replacement Data transfer risk CEO, CFO, Finance, Billing, Customer Service 6:38 PM O Type here to search

• What have they missed?
• What would you add if you were the project manager?

Answer 1

(a) They have missed few points, as mentioned below:

1. Data Backup : They need to have a data backup ready from the existing system so that in case of any data loss it can be recovered.
2. Data integrity : They need to focus on the integrity of the data, as once it has been uploaded to the new system, they should not face integrity issues later.
3. Business continuity : They should keep in mind that while developing or piloting the new system the current running system must be fully functional and operable.
4. Rollback : They should have a feature ready for rolling back the entire system in case any critical issues happen.
5. Disaster Recovery : They must consider option or a DR ( Disaster recovery ) system, in case any failures happen later in the cycle.

(b) If I were the project manager, I would have considered certain critical factors like:

1. System Security : Since the system has financial data, it calls for better security practices in place.
2. Testing and Quality Assurance : I would have provided more time for QA, to verify the system exhaustively against the business requirements.
3. User Interface : I would have also proposed a better user interface and user friendly layout for target audience to interact with application in a better manner.
4. Post Delivery/Maintenance : I would also have considered the plan for post delivery and maintenance/support for the application, as it also plays a vital role in overall success of the project.