PSM SCRUM
In the middle of the sprint the customer decided that there are 2 new features needed. How can the product owner handle this?
1. Ask the developers to consider whether they can add these features to the current sprint 2. add them to the product backlog for next sprint Ex: The developers are accountable for the sprint backlog. If they feel like the new features cannot be completed in this sprint the product owner should put them in the product backlog to consider them for the next sprint
The definition of "done" is used to...
1. Increase transparency 2. guide the developers on how many product backlog items can be completed in this sprint 3. created a shared understanding of when work is complete Ex: The dod is a formal description of the state of the increment when It meets the quality measures required for the product. the sprint ends when the time runs out
What are 3 advantages of a product owner with a clear and well communicated product goal
1. It gives clear direction so sprints do not feel like isolated pieces of work 2. It is easier to inspect incremental progress at the sprint review 3. It provides the big picture helping the scrum team to keep focus. they can check any decision against It. ex: a product goal is mandatory in scrum. a product backlog does not become finished unless the product is fully discontinued. if the product exists a product backlog exists. The product goal is the product backlog. the rest of the product backlog emerges to define "what" will fulfill the product goal
a done increment is valuable if
1. It is likely to increase customer satisfaction 2. It reduces long-term operational costs
Select 2 statements that explain what "done" means
1. There is no work left from the definition of done 2. all work to create software that is ready to be released to end users Trick question. In this case done means there is no work left from the definition of done. if It is done and therefore has met the definition of done then It is ready to be released. The moment a product backlog item meets the definition of done, an increment is born. If a product backlog item does not meet the definition of done, It cannot be released or even presented at the sprint review. Instead, It returns to the product backlog for future consideration.
a scrum master manages a list of impediments, but It is growing and only a small portion are currently capable of being resolved. which techniques would be most helpful in this situation?
1. alert management to the impediments and their impact 2. consult with the developers 3. help the scrum team to prioritize the list and work on them in order Ex: the SM is accountable for causing the removal of impediments to the scrum team's progress. The SM should consult with the developers to find solutions and help the scrum team to prioritize the list based on priority and dependency. if it's possible and becoming a problem the SM must alert management including the product owner
what should be done if the po is unavailable
1. during the sprint, the developers make the best decisions possible to assure progress toward the sprint goal, re-aligning with the po once available again 2. if permanently unavailable, a new po needs to be appointed. a po is essential to scrum Ex: the po is responsible for maximizing the value of this particular product and needed on the scrum team.
What two things should happen to a product backlog item, if at the end of a sprint the item does not meet the definition of "done"
1. put It back on the product backlog for the product owner to decide what to do with it 2. do not include the item in the increment this sprint ex: trick question. the dod is there to maintain standards, an item cannot be partly done and cannot be partly released. the item needs to be discussed in the sprint retrospective to understand why It could not be done and go back onto the product backlog.
Which statements are true regarding the product backlog
1. ready product backlog items are sized appropriately, and no one item is bigger than a sprint 2. the product backlog is the best place to gain the most actual insights Ex: The product backlog is an emergent, ordered list of what is needed to improve the product. product backlog refinement is a constant process and can happen at any time, and should not be blocked by waiting for a sprint event. It is the single piece of work undertaken by the scrum team and best place to gain insights about the product. popular choices use the Fibonacci sequence (1, 2, 3, 5, 8) and small, medium and large
What helps the Product Owner manage the value of a product? Choose the 2 best answers
1. the order of the product backlog 2. validating assumptions of value through frequent releases Remember Planning Poker is a good technique but it is not part of Scrum. Also The Product Owner is the person who understands the market and the product value, asking the developers to estimate value based on Planning Poker would be wrong. The Product Owner orders the Product Backlog to ensure high priority items are developed and delivered. The Product Owner also needs to be reviewing the market, engaging with stakeholders and measuring the value of the product consistently and after each iteration and release through the key value measures.
when trying to decide on the sprint length, which to factors are best to take into account?
1. the risk of being disconnected from the stakeholders 2. the level of uncertainty over the technology to be used ex: sprints enable predictability by ensuring inspection and adaptation of progress toward a product goal at least every calendar month. shorter sprints give the opportunity to regularly inspect and adapt to factors such as the technology being used.
which of the following are true roles the scrum master takes
1. the scrum master helps those outside the scrum team to interact with the scrum team 2. the scrum master teaches the developers to keep their daily scrum meeting to their time-box sm is a true leader who serves the scrum team in many ways including: ensuring that all scrum events take place and are positive, productive, and kept within the time box. facilitating stakeholder collaboration as requested or needed
which are not topics that are best place for discussion in a sprint retrospective
1. the value of work currently represented in the product backlog 2. sprint backlog for the next sprint Ex: the sprint retrospective is a chance for the team to plan ways to increase quality and effectiveness. the scrum team inspects how the last sprint went with regards to individuals, interactions, processes, tools and their dod. the chance to discuss the value of the product backlog comes at backlog refinement and sprint reviews.
how can a product owner establish that value is being delivered
1. time to market 2. customer satisfaction ex: 4 key values: unrealized value, a ability to innovate, current value, time to market. customer satisfaction is part of the current value area. time to market is a value area. velocity leads to a quick time to market but ultimately the better metric
The Product Owner must monitor and share progress of Product Backlog through:
Any projective practice based on trends of work completed and upcoming work There are many ways to monitor and share the progress of the Product Backlog. Scrum does not prescribe any specific method. It is up to the Product Owner's discretion as to what method is used.
It is mandatory that at least one product increment be released to production at the end of each Sprint.
False "The heart of Scrum is a Sprint, a time-box of one month or less during which a "Done", useable, and POTENTIALLY releasable product Increment is created". "This Increment is useable, so a Product Owner may choose to immediately release it." - Scrum Guide 2017. "Multiple Increments may be created within a Sprint. The sum of the Increments is presented at the Sprint Review thus supporting empiricism. However, an Increment may be delivered to stakeholders prior to the end of the Sprint. The Sprint Review should never be considered a gate to releasing value." Scrum Guide 2020. It is not mandatory that an increment is released at the end of every Sprint but it is expected that the Sprint yields one or more releasable increments. If it does not this should be discussed at the Sprint Retrospective.
Which is true about technical debt
It creates uncertainty because problems exist and build up as more code is added and the complexity increases. This will slow development down. (Correct) It creates false assumptions about the state of the product if unknown problems exist (Correct) Technical debt incurs due to inadequate design and architecture which can happen when developing gradually in a reactive environment. Refactoring might be needed to improve the Product's design and robustness. Failure to refactor and remove technical dept will result in development becoming harder and harder due to the complexity and number of problems. Development Progress will slow.
in sprint 6 the environment in which a product will be used changes. what is the effect on the product backlog
It evolves to reflect what the product needs to be most valuable Ex: During the sprint review, the scrum team and stakeholders review what was accomplished in the sprint and what has changed in their environment
Why do developers require a sprint goal
It helps the developers to become more focused with a common and specific goal Ex: the sprint goal is the single objective for the sprint. also creates coherence and focus. the sprint goal is created during the sprint planning event and then added to the sprint backlog. if the work turns out to be different they collaborate with the po to negotiate the scope of the sprint backlog within the sprint without affecting the sprint goal.
Which of the following is a requirement of Scrum
Sprint Retrospective Ex: The sprint retrospective is a scrum event required by scrum as outlined in the scrum guide
Who is responsible for tracking the remaining work of the Sprint to predict if the Sprint Goal will be met by the end of the Sprint?
The developers The Developers create a plan for the Sprint and the Spring Backlog and adapt that plan to meet the Sprint Goal. They also hold each other accountable as professionals. The Developers meet daily at the Daily Scrum to discuss progress toward the Sprint Goal and adapt the Sprint Backlog as necessary, adjusting the upcoming planned work.
A new developer is having continuing conflicts with the existing Developers and creating a hostile environment. If necessary, who is responsible for removing the team member?
The scrum team is responsible, and may need help from the scrum master Scrum Teams are Self-managed, meaning they internally decide who does what, when, and how. As a self-managed team they need to adapt to the situation, adaptation becomes more difficult when the people involved are not empowered or self-managing. A Scrum Team is expected to adapt the moment it learns anything new through inspection. The Scrum Master is accountable for coaching the team members in self-management and cross-functionality. It is up to the Scrum Team to find a solution to the issue
who can do much of the gathering of marketplace data for the product owner
anyone Ex: the po may or may not be the one doing the bulk of gathering the marketplace data. the po may do the work or may delegate the responsibility to others. regardless, the po remains accountable so the po has to be aware of the data/research
which of the following is not a pillar of scrum
empiricism Ex: the three pillars of scrum are adaptation, inspection and transparency. scrum is based on empiricism but it's not one of the pillars.
cross-functional teams are optimized to work on a specific part of the product (GUI, database, middle tier, design contacts)
false Ex: a cross functional team is a group of people with different functional expertise working toward a common goal. It may include people from finance, marketing, operations and Human Resources departments.
why must the po be at the daily scrum
he/she doesn't need to be there
the scrum master's role in the daily scrum is to
teach the developers to keep the daily scrum within the 15 minute time-box Ex: to reduce complexity the daily scrum is 15 minutes. if the po and sm are actively working on items in the sprint backlog, they participate as developers. otherwise the sm only needs to make sure the meeting goes ahead and helps the developers to keep It within the 15 minute time box
Who must attend the daily scrum
the developers if the po or sm are actively working on items in the sprint backlog, they participate as developers
Who is accountable for estimating the effort the complete the product owner's product backlog items?
the developers. they will be doing the work and should have a complete view of the work needed to transform product backlog items into increments of product ex: developers are best placed to make judgements on the amount of effort needed to complete an item as they are the ones doing the work
Every scrum team must have a product owner
true. outcomes are affected by their participation and availability scrum team: SM, PO D. They don't need to be 100% dedicated to that team but they do need to be available to meet the needs of the team. Some scrum masters and product owners may be involved in more than one scrum team
what do burn-down charts track via visualizing progress
work remaining across time
should the po be aware of the marketplace for the product
yes Ex: It is the po role to maximize the value of the product. can only be done by knowing the marketplace, the key stakeholders, the users, etc. the po needs to constantly be gathering information and feedback regarding the marketplace and the product.
can the first sprint begin before the product owner has a fully complete product backlog?
yes Ex: scrum requires no more than a product owner with enough ideas for a first sprint, developers to implement those ideas and a scrum master to help guide the process. the product backlog is added to and improved always - It is never fully complete
You are a new Scrum Master and have been asked to take a lead in the development of a new product. Seven teams new to Scrum will build this product. You have the beginnings of a Product Backlog from gathering requirements. How would you minimize dependencies between the Scrum Teams?
you work with the developers on how to best analyze and break apart the work The Developers are closest to the work and are the best source to consult with regarding dependencies, they can refine the backlog and decompose the items to best break the work apart. You as the Scrum Master are not the best person to identify all dependencies and the responsibility for organising the Product Backlog lies with the Product Owner.
