What is Product Backlog and who owns it? | chisel (2023)

This article covers:

  • Was ist Product Backlog?
  • Who owns the product portfolio?
  • Who makes the final decision on prioritizing the product portfolio?
  • Who can order the items in the product portfolio?
  • What characterizes a good product portfolio?
  • How do you assess the product portfolio?
  • What techniques are there for prioritizing the product portfolio?
  • Product accumulation examples
  • Sprint-Backlog vs. Produkt-Backlog

Was ist Product Backlog?

Scrum DelaysList all the work you need to do. This is where you save the things you need to do in the future.

Specifically, a Product Backlog is a list that contains user stories, new features, changes to existing features, anderror correction.It also includes elements that help teams achieve specific outcomes.

Nothing gets done unless it's in the Product Backlog. But just because you write something down doesn't mean you're obligated to turn it in.

Onlyrepresents an optionoffering certain things instead of compromise.

Should bestraightto add an item to the Product Backlog. Removing an item from the backlog should also be just as easy.

When organizing your product portfolio, you shouldSort items by priority.The items with the highest rank represent the most important pieces of equipment to complete the task.

IsSizejDetailof a portfolio item may vary depending on how long you need it.

Working on an article shouldcontain enough informationso that the device works immediately.

However, let's assume that these articles do not have a specific time frame.

In such a case, your outline should remain broad with few details. This ensures that you can move on to other projects if needed or desired.

Product backlog items are constantly changing as team members better understand the outcome.

These changes include adding or removing backlog items and refining existing items.

Such a procedure gives thedynamic functionAevery project/product development.

With regard to the product portfolio, a team can consist of several people with different roles.

The person responsible for maintaining everything related to this list is named“Product Owner”.

Prima:Click here for information on the roles and responsibilities of a Product Owner.

This position requires tracking of items that you can delete upon completion or no longer need to be there for whatever reason.

Changes within teams, such as adding new members or changing goals, should also be reflected in a change in their priorities. This helps keep everything up to date.

What is Product Backlog and who owns it? | chisel (1)

Who owns the product portfolio?

der Product Ownerowns and decides to prioritize the product portfolio.

It would be better for every member of the wholecross-functional teamscontribute to the delays.

What is Product Backlog and who owns it? | chisel (2)

Another thing to remember is thisOwners and purposes changebased on team approach.

For example, the owner of the sprint backlog in Scrum is the delivery team.

Who makes the final decision on prioritizing the product portfolio?

In the crowd, theProduct Owner (PO)is the only person responsible for prioritizing the stories within the product portfolio.

(Video) Introduction to Scrum - 7 Minutes

Although the PO makes the final decision on prioritizing the Product Backlog, this does not mean that the Product Owner is alone in this task. You can ask for any help you need.

It would be better if you understand that the owner of the product is aLawyerfor the customer

The more they understand the client's needs, the better their project will be in terms ofcost effectivenessjsustainability.

they shouldmaintain close contact with your customersto collect all necessary information on how you would like this new product, or aspecial featuredevelop.

The exchange with other stakeholders can also give them an idea: there should be no surprises in the development.

All it takes is one big change request at an expensive time close to the release date to set things back weeks, if not months, without prior planning.

The Product Owner is the only person responsible for deciding on prioritiesat the end of the day.For this reason, you should never have multiple product owners.

There must be a single point of truth for decisions: the product owner.

So then,Where does the Scrum Master fall into all of this?

Think aboutScrum Master as team leader.

Prima:Click here to understand a scum team.

have to stayimpartial in all aspects of product designand decision-making, yet reject any obstacles that might impede a productive workflow in the project.

they are likemoderatorsTherefore. They cannot play favorites with their teammates or interfere in disagreements about the best course of action.

Suppose they venture too far into these kinds of discussions. In this case, it will only serve as an obstacle when trying to solve problems with your colleagues.

Your time would now be split between two responsibilities instead of just one.

The Scrum Master will always help the Product Owner with this. However, you will not be involved in the final decision.

Preventing the Scrum Master from prioritizing is the same logic as why aproject managerand a Scrum Master should never be the same person.

Many companies will try this because they want to performagile practice without changetheir old values, processes or organizations. But that's not how it works.

How long is the product backlog?

The product portfolio exists and changes throughout product development.

Is lasts for the life of the product.

Who can order the items in the product portfolio?

Product Owner bestellen Product Backlogs.

work with himaffected parties,the development team,and the Scrum teamPlanning and analyzing work.

IsPO and Scrum Team need to work togetherto give the development team an appropriate plan for the product backlog.

What characterizes a good product portfolio?

Below are the four characteristics of a good product portfolio.

You can keep the acronymDEEPkeep in mind and understand if your product portfolio fits.

Appropriately detailed

One ofcriticalCharacteristics of a good product portfolio is that it will bedetailed enough.

Items in the product backlog that you need to address later have less detail than the prioritized ones.

(Video) Why the Scrum Product Backlog Is Not Only User Stories And Is Not Prioritised


The product portfolio is a constantdeveloping document.Teams and product owners can add items and othersrelevante Informationevery time they find out.

You can also decide to change or remove some things.

If the product portfolio you are working on changes, that is the mark of a good product portfolio.


A good product portfolio should be availablea significant size estimate. And this estimate should relate to the effort that the team needs to put into its development.

In this way, the product owner can easilyVisualize, estimate and prioritize the itemor.

For example, the items in the team's portfolio that are prioritized are small.


A single Product Backlog should be a collection of multiple Product Backlog items. But in this case, you shouldn't put every item in the Product Backlog on top.

When such a situation arises, it is best to take with you the product elements you need for your launch. Don't focus on the other items in the product portfolio.

This way you save time and canfocus on your priorities.

How do you assess the product portfolio?

Estimating a product backlog helps product owners and teams reanalyze the items in the backlog.

You can use the following three estimation methods to estimate product backlog.


As the name suggests, this Product Backlog Estimate is also fun to work with.

Once you have onerating scaleGather your team members instead. Now deal each of them the leaderboard cards.

Read aloud the product backlog item you need to rank for. Each team member selects the map and sorts the items. But they won't disclose it until the product owner gives a notification.

Once everyone has chosen their rating for that item, the team reveals the cards.

If the estimates are similar, the group has agreed to that status.

However, if the selected estimates differ, the team needs to address them further.


Another estimate of the product backlog is the order.

Each team member takes a card that has a specific portfolio item printed on it. Then they put it on the desk.

The team then places the items on each side of the desk, taking into account how the team member views them.

One side of the desktop will display high priority items. Conversely, the other side will have the lower priority items.

Then the other team member also takes a card from the deck and places it anywhere. You can also move the existing map to either side.

Once all the cards are stacked on the deck and all members have agreed on their positions, assign a number to the backlog items. This number is assigned using theFibonacci Scales.

Rank the items starting with the bottom cards. For example, give the smallest item the number 1, and if you move to the other side of the desk, the estimate would be 3, 4, 5, and so on.

unique method

One of the unique ways to estimate product backlog depends on the jerseys you wear.

Surprised?no seas

Estimating this method is very simple.

(Video) What Does an Agile Product Owner Do?

Here's how you can do it: You can estimate the Product Backlog item by size S, M, L, XL, XXL, etc.

This method is useful if you areuncertain in numerical estimatesOr are you still thinking about the project?

Note, however, that you cannot use this estimate to the end. Once you're comfortable using the numbers, convert these jersey sizes to one of the estimates above.

Who creates the estimate for a Product Backlog Item?

Isdevelopment teamo The DT is responsible for all estimates in the product portfolio.

But the DT must consult and discuss the product backlog items with the owner.

What techniques are there for prioritizing the product portfolio?


The RICE scoring model is a prioritization frameworkdesigned to help product managersDetermine which products, features, and other initiatives make the cut.You can provide the RICE score by ranking these articles by four factors.

The factors that form the acronym RICE are:

  • To reach(the number of clients that would use this function)
  • impact(by how much it will improve your company's results or revenue)
  • Trust(the belief in our ability to meet that estimate)
  • efforts(resource requirements for development time/costs)
What is Product Backlog and who owns it? | chisel (3)

Using such a rating system can offer companies three main benefits:

  1. qualificationbetter informed decisionsby less biased decision makers.
  2. Helpdefense optionswhen interviewed by managers.
  3. reducing the riskinvolved in new ideas being introduced into already risky environments.

Moscow method:

The MoSCoW method is a frameworkforCommunicate effectively with key stakeholderswhat and why you are working on specific features.

Moscowrepresentshould have (required), should have (preferable but not required),would have (possibly advantageousor advantageous),won't get it now.

It is usually used bywaterfall basedHowever, it can work better in agile environments when time constraints make it difficult to complete the entire project at once.

It helps critical stakeholders understand which backlog items to focus on most, saving time and energy by categorizing them more efficiently.

Value vs Effort

The value versus cost prioritization methodHelpsimplifyall enumerate different characteristics and initiatives.

It quantifies them with value and cost values ​​to determine their place in the matrix accordingly.

Value vs Effortprioritization methodis a great opportunity for organizationsUse your resources in the most effective way.

In addition, he remains true to the company's values ​​and goals while delivering on promises to customers. All of these, if done correctly, will result in increased revenue or growth.

Features are classified byhow much value they offerin relation to the implementation effort.

CanMeasure it by ROI (Return on Investment)or the total cost per feature to full development. You can choose what seems most appropriate given the specific circumstances.

1-2-3 Later

The Product Owner reviews all items in the Product Backlog.3 times.

The first time they try to find the most important item to work on next and set it aside while inspecting other items in a similar fashion.

You repeat this process two more times, each new batch of options being checked in pairs (one from the previous batches).

Finally, they return to where we started: back to the original list. However, now she organizes it based on the urgency of completion.

This technique would be best to useif there are fewer than 25 backorder items in total.

Simple ordering of two factors

First, the product owner assigns each item a business value from 0 to 5; higher numbers mean they are more valuable to the company.

This person then takes responsibility for them and asks for their help, dividing them into two groups:

  1. small enoughso it can be completed in less than a day if everyone crowds in;
  2. everything else istoo big or unsafeabout fitting into the time frame.

The Product Owner analyzes everyone who fits the first category based on their score. Then arrange them and fill in what is missing.

The Product Owner should only focus on the items in the "few enough' for this disambiguation work.

(Video) 20 Product Owner Interview Questions and Answers

Leave the other items in an almost random order. It helps make prioritization decisions easier when many options have the same business value. Such a technique works well when there is an in between20 and 50 items in the product portfolio.

These techniques require some consideration when multiple items within a category have the same commercial value.

However, it is advisable not to worry too much about them. That is, as long as you place the items in "few" Size. Small size usually meansless than twenty

Prima:Click here to understand and define the purpose of a product.

FIFO with expedited shipments

With this technique, the items of the product portfolio are preservedsorted by request.

The only exception is that the Product Owner can move a set number at the beginning of each Sprint.

In addition, items at the top can be removed when completed or deemed irrelevant. This process works forany size and quantity.

However, all entries must be small enough to be completed in one sprint.

Product accumulation examples

Let's take a look at goal-based product backlog examples.

A product portfolio structured according to goals is also referred to astargeted backlog. It focuses on theproduct targetand divides it into sub-functions.

The two benefits you can get from a goal-driven backlog are:

  • Teams can spend more time on itbusiness value.You can update and improve related features of a product.
  • Since the goals are visible every day, teams feel themresponsiblefor working for her. You can create measurable feedback scores to determine if the team is on the right track.

Sprint-Backlog vs. Produkt-Backlog

IsSprint backlogIt is aplan in the short termfor teamwork.

The product portfolio is along-term plandetermined by the services that make your products more valuable.

Many people may think that these two tasks are interdependent. This is not always the case, however, as the two can actually be different approaches.

Although histhe goals are the same, they often become part of each other.

The product portfolio isa container for essential workthat keeps your company active in the market competition.

It can also change frequently as items are added or removed regularly. It is usually more prominent than the sprint setup because of thishigher granularity(minus things broken down below user story levels).

The Product Owner monitors this list, mainly unassigned tasks.

These unassigned tasks are scheduled to ensure there is always something new popping up so customers never get bored.

On the other hand, theSprint backlogIt's a container for the work items that the team needs to get done as part of their next sprint.

It is the outcome of the meeting where they decide what work will be done over the next week and month, which usually takes one to four weeks.

You generate the content for these sprints based on the agreed user stories.

But if necessary, you can also includeBugs and refactoring tasks(which makes the code more efficient).

What is Product Backlog and who owns it? | chisel (4)

Finally,Software for product managersifchiselHelp teams organize andPrioritize your product portfolio.

Click here to request a demo session with Chisel.

It is asimple but powerful toolThis makes it easier to collaborate with your team members on the back end of a project or initiative.

Conintuitive features like Kanban boards, you can easily see what tasks are due next and whether they are done or not.

(Video) What is the Product Owner Career Path?

Best of all, Chisel is free forever! Try it.

You might also be interested in:

  • Product Backlog Entry
  • A comprehensive guide on what backlog fulfillment is and how it will improve your product
  • Use cases of the RICE model


Who owns the product backlog? ›

Who Owns the Backlog? While the entire cross-functional agile team works together on the backlog, the product owner owns it. In most cases, the product owner (or product manager) holds responsibility for organizing and maintaining the product backlog.

What is in a product backlog? ›

A product backlog is a prioritized list of work for the development team that is derived from the roadmap and its requirements. The most important items are shown at the top of the product backlog so the team knows what to deliver first.

What is the definition of product backlog in agile? ›

In Agile development, a product backlog is a prioritized list of deliverables (such as new features) that should be implemented as part of a project or product development. It's a decision-making artifact that helps you estimate, refine, and prioritize everything you might sometime in the future want to complete.

Who owns the product backlog in sprint? ›

Who Owns the Sprint Backlog? According to the scrum framework, the entire agile team — scrum master, product owner, and development team members — will share ownership of the sprint backlog. This is because all members of the team will bring unique knowledge and insights to the project at the beginning of each sprint.

What is product backlog with example? ›

A product backlog is a prioritized list of work items or features that help you meet product goals and set expectations among teams. In general, each product in development should have a dedicated product backlog. Similarly, each product backlog should have a dedicated project team.

What does it mean to own the backlog? ›

The product backlog is an evolving list of requirements for a product, prioritized by the value they bring to the customer. The product owner owns the product backlog. They work closely with the development team to ensure the backlog is constantly updated and refined.

What is a product backlog quizlet? ›

A product backlog lists all the items that could be needed in a product. It is maintained by the product manager/owner and is the major input for release, wave, and iteration planning. It includes: • Functional requirements. • Non-functional requirements.

Which of the following best describes a product backlog? ›

Which of the following best describes the Product Backlog? The Product Backlog is a type of planning. However, we don't create predictive, detailed upfront plans in Agile environments: the Product Backlog is dynamic and never complete as the product exists.

What is the difference between backlog and product backlog? ›

The Product Backlog contains all the items in the software development project. The Sprint Backlog contains only the items of the Backlog specific to the current Sprint. Sprint Backlogs are the songs. The complete Product Backlog is the album.

Why is it called backlog? ›

Etymology. back +‎ log. 1680s; originally a large log at the back of a fire. Figurative sense from 1880s, meaning "something stored up for later use".

What is a product backlog in Scrum quizlet? ›

The Product Backlog is an ordered list of everything that might be needed in the product and is the single source of requirements for any changes to be made to the product. Tap the card to flip 👆

Which Scrum role owns the product backlog? ›

Scrum product owners understand the customer and business requirements, then create and manage the product backlog based on those requirements.

Who owns the team backlog? ›

The Product Owner (PO) is responsible for the team backlog. Since it includes both user Stories and enablers, it's essential to allocate capacity in a way that balances investments across conflicting needs. This capacity allocation takes into account both the needs of the team and the Agile Release Train (ART).

Who is the owner of the sprint? ›

Sprint Corporation
Former Sprint World Headquarters Campus in Overland Park, Kansas, U.S.
Total equityUS$26.07 billion (2019)
Number of employees28,500 (Q1 2019)
ParentT-Mobile US
20 more rows

Why do we need a product backlog? ›

It provides a prioritized list of actionable items for the team. With a backlog, product managers know their team always has a set of next-up tasks, which will keep the product's development moving forward.

Who can see the product backlog? ›

The Rules of Scrum: The Product Backlog is easily visible to every stakeholder (e.g. cards on a wall or an electronic tool with open access) The Product Backlog is a constantly changing artifact, owned by the Product Owner. Stakeholders need real-time visibility into the current state of the Product.

Who can write product backlog items? ›

Writing Product Backlog Items (PBIs) is a very common responsibility of Agile Business Analysts. However, it's often a task which varies widely from one Business Analyst (BA) to another.

Who is primarily responsible for maintaining the product backlog? ›

Who is responsible for maintaining the product backlog? The Product Owner (PO) “owns” the product backlog on behalf of the stakeholders, and is primarily responsible for creating it.

How does a product owner prioritize backlog? ›

One of the most common methods of prioritizing the product backlog is stack ranking. Stack ranking is done by sorting each task by priority. In this way, the task with the most critical functionalities is set at the highest rank, followed by the next set of important tasks.

Does the PO own the backlog? ›

The Product Owner is the person responsible for making changes to the backlog and for planning sprints. Given the dynamic nature of a backlog, developers, who are at the forefront of this changing landscape, might want to add or remove user stories as new needs arise.

What is a product backlog Reddit? ›

Product Backlog = anything that is not in the current sprint. Stories, bugs, tasks, and all other work items. This should be prioritized by the PO and estimated by the Dev team prior to entering a sprint. Sprint Backlog = all items in the current sprint.

Who is responsible for the product backlog quizlet? ›

Who is responsible for the Product Backlog? The Product Owner is responsible for the Product Backlog, including its content, availability, and ordering. Who is allowed to change the Sprint Backlog during the Sprint? Only the Development Team can change its Sprint Backlog during a Sprint.

Which of the following is a requirement of a product backlog item? ›

Each PBI must have these qualities: Description: What the goal of the PBI is. Value: the Business Value of the PBI as determined by the Product Owner. Estimate: the Team needs to estimate the relative effort it will take to move the PBI to Done.

What's the difference between sprint backlog and product backlog? ›

The product backlog gives an overview of the entire product. A sprint backlog gives a closer focus on the work of the product during a specific time period.

Which one is not in the product backlog? ›

Contrary to popular misunderstanding, the Product Backlog does not contain “user stories”; it simply contains items. Those items can be expressed as user stories, use cases, or any other requirements approach that the group finds useful.

How is product backlog created? ›

The product backlog is arranged according to the progress toward the implementation: There are features, tasks, tasks in progress, and executed tasks. A backlog is constructed so that the high-priority items appear at the top of the list, and the least important features are at the bottom.

Can a product backlog have more than one product owner? ›

The short answer is no, because product ownership does not scale in quite the same way as servant leadership potentially can. Multiple Development Teams, each with a Scrum Master, can draw from a single Product Backlog that must be owned by exactly one PO.

Does Scrum have product backlog? ›

The agile product backlog in Scrum is a prioritized features list, containing short descriptions of all functionality desired in the product. When applying Scrum, it's not necessary to start a project with a lengthy, upfront effort to document all requirements.

What are the 4 major categories of items in product backlog? ›

  • What Are the Types of Product Backlog Items? The product backlog lists all the tasks that must be completed to deliver a product to the customer. ...
  • Features. ...
  • Defects. ...
  • Technical work. ...
  • Knowledge acquisition/research.

What are the characteristics of good product backlog? ›

DEEP: The 4 Characteristics of a Good Product Backlog
  • Detailed appropriately.
  • Estimated.
  • Emergent.
  • Prioritized.

What is backlog in Scrum cycle? ›

In the simplest definition the Scrum Product Backlog is simply a list of all things that needs to be done within the project. It replaces the traditional requirements specification artifacts. These items can have a technical nature or can be user-centric e.g. in the form of user stories.

Is backlog same as roadmap? ›

A roadmap is mainly for the executive team and other stakeholders. Whereas a product backlog is primarily for the development teams. A roadmap intends to communicate the overall strategy to different stakeholders, while a backlog communicates the task details and steps to execute the plan.

Is sprint a backlog? ›

A sprint backlog is a list of work items your team plans to complete during a project sprint. These items are usually pulled from the product backlog during the sprint planning session. A clear sprint backlog prevents scope creep by clarifying exactly what your team will be doing—and not doing—during each sprint.

Is Scrum Master responsible for backlog? ›

The Scrum master helps the product owner find techniques to effectively define the product goal and better manage the product backlog.

Does the Scrum Master manage the product backlog? ›

The Scrum Master helps the Product Owner to prioritize and groom the Product backlog, imparts a clear understanding of product planning, and facilitates Scrum events as required by the Product Owner. He or she acts smoothens communications between the team and the Product owner.

Does Scrum Master maintain product backlog? ›

A Scrum Master coaches the Development Team and the Product Owner about managing the Product Backlog to facilitate empiricism-based product planning and arranging the items so that the order can maximize overall value.

Who owns or is responsible for backlog priorities? ›

"The Product Owner is the sole person responsible for managing the Product Backlog." It also has this to say about the product owner: "The Product Owner is one person, not a committee.

Who owns the board in Scrum? ›

Scrum board is always owned by one Scrum team (and typically run by a leader called a Scrum Master). A Scrum team is a cross-functional group of employees whose background contains all the skills required for successful completion of all the tasks during this Sprint.

Who owns what in Scrum? ›

If you follow the Scrum Guide that should be very simple. Product Backlog: is owned by the Product Owner, it his/her responsibility to keep it organised and ordered by value. Sprint Backlog: is owned by the Developers, it is their responsibility to keep it organised and representing the most recent state of the work.

Who runs sprint planning in scrum? ›

A scrum master or coach typically facilitates sprint planning in order to ensure that the discussion is effective and that there is agreement to the sprint goal and that the appropriate product backlog items are included in the sprint backlog.

Who runs the demo in agile? ›

Product Managers and Product Owners, who are usually responsible for running the demo. One or more members of the System Team, who are often responsible for setting up the demo in the staging environment. Business Owners, executive sponsors, customers, and customer proxies.

Who owns the sprint goal in scrum? ›

The sprint goal is a mandatory part of the Scrum framework. It is collaboratively created by the Scrum team during the sprint planning meeting. Its creation is typically guided by the product owner with the development team then deciding which functionality and technology it will implement to fulfil the goal.

Which scrum role owns the product backlog? ›

Scrum product owners understand the customer and business requirements, then create and manage the product backlog based on those requirements.

Does Scrum Master gather the product backlog from product owner? ›

It is the product owner's responsibility to create and maintain the product backlog, which keeps changing based on current status of the work and development needs. The Scrum Master helps the product owner refine and maintain the backlog by using information gathered from standup meetings.

Can product owner and Scrum Master be the same person? ›

No, it should be 2 different individuals. This would seem to naturally indicate 2 separate individuals for Scrum Master and Product Owner. They each have a different focus and scope.

Who owns and prioritizes the product backlog? ›

The product manager is responsible for creating, prioritizing, and maintaining a product backlog. Requests for backlog items come from various sources: sales, the QA team, customer support, and product stakeholders.

Who owns portfolio backlog? ›

There are usually more product owners than product managers. The management of the portfolio backlog is the domain of the product manager; the management of the team backlog is the domain of the product owner. The two roles need to collaborate to avoid the emergence of handovers and delays.

Can Scrum Master add items to the product backlog? ›

In practice most Scrum Teams will allow unsized items onto a Product Backlog with the understanding that estimates will be provided (and the items discussed) in the next refinement session.

Does product backlog contain user stories? ›

As PBIs become a higher priority in the product backlog, they are broken down into user stories. This is very common as backlogs get larger and agile teams need to organize the items in the backlog.

Can one person play 2 roles in Scrum? ›

Yes, Scrum Roles Can Be Merged

I've led many Scrum projects here at Entrance over the past 2 and a half years. Some of the projects have been successful despite one person taking on multiple roles. For instance, as the ScrumMaster, I often contribute to the development effort when the team needs it.

Who is higher Scrum Master or Product Owner? ›

A Scrum Master leads the Agile development team and supports the Product Owner by relaying updates to relevant employees. Product Owners manage the product backlog and ensure the company gains maximum value from the product.

Can Product Owner attend daily scrum? ›

Product Owners should be at the Daily Scrum as they are a member of the team who has critical information to share. They do need to remember that their presence can be beneficial or detrimental and it's up to them to embody behaviors that promote team agility and not derail necessary conversations.


1. Agile| Scrum |How to conduct a Product Backlog Refinement Meeting?
(Business Analysis Guide)
2. Essential Product Owner Skills 2021
(Product HQ)
3. Product Backlog - Best Practices & some tools
(Growth Vikings | Nastasha Velasco)
4. Dismantling Barriers to a New Museum CMS
5. Product Backlog Anti-Patterns — An Introduction to Forensic Analysis
6. How to Prioritize a Product Backlog as a First Time Product Manager
(Product Gym)
Top Articles
Latest Posts
Article information

Author: Kimberely Baumbach CPA

Last Updated: 04/25/2023

Views: 5731

Rating: 4 / 5 (61 voted)

Reviews: 92% of readers found this page helpful

Author information

Name: Kimberely Baumbach CPA

Birthday: 1996-01-14

Address: 8381 Boyce Course, Imeldachester, ND 74681

Phone: +3571286597580

Job: Product Banking Analyst

Hobby: Cosplaying, Inline skating, Amateur radio, Baton twirling, Mountaineering, Flying, Archery

Introduction: My name is Kimberely Baumbach CPA, I am a gorgeous, bright, charming, encouraging, zealous, lively, good person who loves writing and wants to share my knowledge and understanding with you.