Question

1. How is creating a product backlog is different than developing requirements in a waterfall methodology?
2. What are the advantages and disadvantages of a product backlog?
3. Do you think having a backlog is an advantage or disadvantage?
   • Why or why not?

Answer 1

How is creating a product backlog is different than developing requirements in a waterfall methodology?

Creating a product backlog

1.         Add ideas to the backlog -Stakeholders will ordinarily be moving toward you with ideas for item upgrades

2. Get clarification -When you're drawn closer by a partner with an item expansion or fix, ensure you comprehend:

•          The explanation for the expansion or fix

•          The measure of significant worth it adds to the item all in all

•          The particulars of the thing

3. Prioritize - The backlog ought to have plainly characterized, high-need things at that point and dubious things that are not a need at the base. In the event that a thing has no worth, it ought not be added to the backlog.

4. Update the backlog regularly - The backlog is a living record; ensure you're continually organizing, refining, and staying up with the latest.

You may have several things in your backlog as ideas for item upgrades are proposed. A portion of these things might be disposed of, yet a considerable lot of them will start advancing up the backlog for further refinement and, eventually, improvement.

Requirement development in waterfall methodology

•          Requirements: During this initial stage, the possible requirements of the application are systematically examined and recorded in a particular archive that fills in as the reason for all future turn of events. The outcome is commonly a requirements report that characterizes what the application ought to do, yet not how it ought to do it.

•          Analysis: During this subsequent stage, the framework is examined so as to appropriately produce the models and business rationale that will be utilized in the application.

•          Design: This stage to a great extent covers technical design requirements, for example, programming language, information layers, administrations, and so on. A design detail will regularly be made that traces how precisely the business rationale shrouded in analysis will be technically executed.

•          Coding: The genuine source code is at long last written in this fourth stage, executing all models, business rationale, and administration combinations that were determined in the earlier stages.

•          Testing: During this stage, QA, beta analyzers, and every other analyzer efficiently find and report issues inside the application that should be settled. It isn't unprecedented for this stage to cause a "fundamental rehash" of the past coding stage, all together for uncovered bugs to be appropriately crushed.

•          Operations: Finally, the application is prepared for arrangement to a live situation. The operations stage involves the organization of the application, yet in addition ensuing help and support that might be required to stay up with the latest.

What are the advantages and disadvantages of a product backlog?

Advantage

The product backlog records the exceptional work important to make a product. This incorporates thoughts and prerequisites, structural refactoring work, and deformities. The beneficial thing about a rundown is that it requires prioritization choices: The product proprietor needs to choose when a thing ought to be actualized. Prioritization gives guidance to the group, and it bolsters run arranging: The backlog things are requested through and through, yet they are nitty gritty as indicated by their need. The things at the top ought to be little and prepared for the following run. Having the backlog prioritized makes it additionally conceivable to complete discharge arranging: It foresees when a thing is probably going to be conveyed

Disadvantage

Working with a rundown is useful when the emphasis is on including usefulness, on composing and organizing client stories. However, making an extraordinary product requires something other than client stories. The client travels, the visual plan, and the nonfunctional properties must be considered as well. Sadly, they don't fit into a rundown. As an outcome, agile groups either disregard catching the client experience, or they keep the UX ancient rarities independently, for example, on a wiki page, or in a project the board instrument. While the previous can bring about a product with a helpless client experience, the last isn't extraordinary either: data that belongs together is put away independently. This makes it increasingly hard to keep the different antiques in a state of harmony, and it can cause irregularities and blunders.

Do you think having a backlog is an advantage or disadvantage? Why or why not?

Backlog is an advantage,

Product backlog as a method of putting a brainstorm or a product plan without hesitation. You'll without a doubt be drawn nearer by partners (or clients) who have numerous thoughts for improving the product. Not all the thoughts are acceptable and not all the thoughts are significant, yet without a sorted out product backlog, it's hard to separate between the extraordinary, important thoughts and the thoughts that would just be an exercise in futility. Here are some different advantages of the product backlog:

1.   It's a sorted out rundown that is effortlessly fought.

2.   It's easy to prioritize.

3.   It can be changed as needs change.

4.   It permits you to promptly observe conditions and request them.

5.   It permits you to consider products in the long-term, not simply in terms of quick needs.

To put it plainly, a product backlog permits you and your group to make systematic, keen enhancements to a product as time goes on.

***Please leave a thumbs up**

Answer 2

A product backlog is basically used bh the Agile project developers. In this, product agile backlog is used as a list of the user's demands and rhe stories. Agile team usually would have a product owner who would be responsible for gathering the user's or client's stories and thus priortisinh then in the product backlog. These stories are then turned into the tasks by the Agile developers.

Waterfall project teams do not include these product owners or backlogs. They don't even use e user stories. They make an initial documentation regarding the requirement of the user and for them, that is their product backlog. That initial document is based on the user's demands and would include all of the requirements and the final software product they have demanded.

The advantages of the Product backlog are:

1. Discussed face to face and is simple in making and interacting with the user.

2. It provides the customer with the effective control to make relevant changes whenever possible.

3. Allows higher flexibility and more scope for changes in the project.

The disadvantages of the same would be:

1. Time consuming as you would reach out to the client every now and then and would interact with them to work on the necessary changes.

2. Also costly because you couldn't order and have all resources at once. You would order as per the demand changes and this would require more costs and resources for its completion.

I think that having this product backlog is advantage by all means. Being it time consuming or ever costly, the biggest factor of the advantage is the risk free nature of the project. By working and having alligned communication with the client, one can develop the same project and product as per the requirements of the clients and could achieve better results without fail and risk.