The reason and avocation of this project is upgrading employee desktop computers

Question

The reason and avocation of this project is upgrading employee desktop computers and software for three regional offices. “Numerous organizations have a process set up to help with project management and execution. One open door for development includes making sensible evaluations of how huge a project is and the amount it will cost” (Project Management Institute, 2013). There are a wide range of names for instruments utilized with this process: business needs particular, prerequisites determination or, basically, business necessities. We as a whole know the battles we confront utilizing a computer that simply isn't exactly up to snuff. We are for the most part agonizingly mindful of the early cautioning signs when a computer is headed out. There is inconvenience running our most loved web program, site pages stack a bit slower and exceed expectations archives solidify up and crash through and through. We comprehend that as a private venture you have to strike a harmony between efficiency while keeping up a financial plan. For the most part, as a computer age and as new programming is introduced on the frameworks it will bit by bit require more assets to run it appropriately. This will start to affect general PC execution and back off different capacities also.

Using info above Post a one-page Project Scope Statement that:

Describes the product or service

Specifies the acceptance criteria

Defines the project deliverables

Explains the project exclusions, constraints and assumptions

Explanation / Answer

Describes the product or service

in the Products and Services section of your business plan, you will clearly describe--yep--the products and services your business will provide.

Keep in mind that highly detailed or technical descriptions are not necessary and definitely not recommended. Use simple terms and avoid industry buzzwords so your readers can easily understand.

On the other hand, describing how the company's products and services will differ from the competition is critical. So is describing why your products and services are needed if no market currently exists. (For example, before there was Federal Express, overnight delivery was a niche business served by small companies. FedEx had to define the opportunity for a new, large-scale service and justify why customers needed--and would actually use--that service.)

Patents, copyrights, and trademarks you own or have applied for should also be listed in this section.

Depending on the nature of your business, your Products and Services section could be very long or relatively short. If your business is product-focused, you will want to spend more time describing those products.

Products and Services section for our cycling rental business could start something like this:

Product Description

Competition

Future Products

Specifies the acceptance criteria

In a perfect world, people would understand each other at a glance and nothing could create confusion among them. But in the real world we have to come up with ways to communicate our ideas clearly so that our peers don’t misunderstand us.

In software development, acceptance criteria help to properly set a client’s expectations for a product. Criteria for an app such as “I want my app to be awesome and popular with as many people as possible” don’t really tell us much; we eliminate misunderstandings between a client and a development team by referring to clearly defined acceptance criteria for user stories.

So how can we make sure that user stories are completed correctly and comply with a client’s demands? This is where acceptance criteria come into play. Acceptance criteria are a formalized list of requirements that ensure that all user stories are completed and all scenarios are taken into account. Put simply, acceptance criteria specify conditions under which a user story is fulfilled. Concisely written criteria help development teams avoid ambiguity about a client’s demands and prevent miscommunication.

Writing acceptance criteria is not only important for eliciting the vision of a product from your client, but for the development process as well. It’s natural that different people see the same problem from different angles.

To define boundaries. Acceptance criteria help development teams define the boundaries of a user story.

To reach consensus. Having acceptance criteria synchronizes the development team with the client.

To serve as a basis for tests. Last but not least, acceptance criteria are a cornerstone of positive and negative testing aimed at checking if a system works as expected.

To allow for accurate planning and estimation. Acceptance criteria scenarios allow for the correct division of user stories into tasks so user stories are correctly estimated and planned

Acceptance Criteria for the User Story at the beginning of this article might look like the following:

Defines the project deliverables

the most important thing is to define the desired project results and work through the deliverables to each of them. The more defined the deliverables are, the easier it is to forecast the timeline, the budget and the scope. Let’s discuss the process of collecting and analyzing project deliverables.

A deliverable is any unique and verifiable product, result, or capability to perform a service that must be produced to complete a process, phase, or project.

I’ll be talking about collecting and analyzing project deliverables, but I’ll also allow myself to change the term ‘deliverable’ for the term ‘project result’ while keeping the definition.

Before the project starts, the project manager and the customer should agree upon which results the customer expects from the projects. Sometimes it’s not as easy as it seems. Try to define project objectives for holding a corporate celebration, then define the results that will let you achieve that objectives. Was that easy to do? I believe not.

The customer has formulated the following objectives:

Thus the expected project results:

The input to the process can be anything, such as:

While the output can include:

When you’re producing a product or a service in the course of a project there will be due dates for deliverables, as well as specific and measurable key performance indicators, such as quality or quantity. Jennifer also distinguished between project deliverables and product deliverables.

Project management deliverables include:

Explains the project exclusions, constraints and assumptions

This is an important topic from a PMP certification exam point of view. You may see a question on this topic on your test.

We always make assumptions and are bound by constraints. These are an important part of our life whether we realize it or not. We always deal with them in our daily life.

For example, suppose you plan to go shopping at a big mall, which is far away from your home. It will take one hour to reach there by car.

You made the assumption that you will leave your home around 6:00 PM and reach there by 7:00 PM. After that, you can enjoy shopping.

This was your assumption. What about the constraints?

At first glance, you can think of two constraints. The first constraint is the amount of money to be spent on shopping. If you have $500 in your hand, you cannot spend more than this amount. This is your first constraint. The second constraint can be the mall’s closing time. If the mall closes at 10:30 PM, you cannot continue your shopping after this time. You have to wrap up everything before this time.

Likewise, projects also have assumptions and constraints. It is necessary for you to understand them if you want to complete your project successfully. A successful project manager always keeps an eye on his project’s assumptions and constraints and understands them thoroughly.

The assumptions and constraints can be identified and documented throughout the project’s life cycle. These parameters play an important role during the planning process. Your risk management plan is heavily dependent on assumptions. If you failed to properly analyze them, it may affect your project’s outcome.

The assumptions and constraints are an important aspect of your project. Although they are not managed like the requirements or risks, a proper documentation of them helps protect you from many potential issues.

You can find your project’s assumptions and constraints in the project scope statement.

Okay, let’s discuss them one by one.

Assumptions

An assumption is a belief of what you assume to be true in the future. You make assumptions based on your knowledge, experience or the information available on hand. These are anticipated events or circumstances that are expected to occur during your project’s life cycle.

Assumptions are supposed to be true but do not necessarily end up being true. Sometimes they may turn out to be false, which can affect your project significantly. They add risks to the project because they may or may not be true.

Suppose in our shopping example, you assumed that it would take one hour for you to reach the destination. What will happen if, due to traffic, you don’t reach the mall on time?

Your assumption is false and your plan for shopping is endangered.

This can also happen to your project. For example, you have made the assumption that some particular equipment will be made available to you whenever you need it. However, when the time comes, the equipment is not available.

Related Questions

Navigate

• Browse (All)
• Browse T
• Subjects

Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.