SOLUTIONS RATED A+
✔✔Risk Register - ✔✔risk exposure = likelihood of it happening x impact if it does
happen. Value to red, amber green (RAG)
✔✔Discovery - ✔✔The correct product for the correct problem
1. Define the problem
2. Find Solutions
3. Choose solution to build
4. Plan how to build the solution
5. Create a prototype of MVP
6. Test solution
7. Evaluate
8. Refine and repeat
✔✔Product vision - ✔✔High level strategy of the goals of your product (not focused to a
specific release)
Good product vision will have the following:
1. What the product will do
2. Who is the product for
3. Why the product will do what it does
✔✔product backlog - ✔✔A prioritized list of user stories, showing both short- and long-
term goals of a software development team.
✔✔Defining the problem - ✔✔the most important step in the marketing research
process
if you don't clearly define the problem the solutions you create won't solve the real
problem. So think of the problem longer than you think of the solution . Really have to
find the root of the problem to think about the solution.
✔✔For a new product, 10 developers and the Product Owner have been assigned. As
the Scrum Master how should you advise they be divided into teams? Choose all
applicable options: - ✔✔2 teams of 6 and 4 people (after a short meeting the developers
decided this is the best option)
3 teams of 4, 3 and 3 people (each team is cross functional)
✔✔Explanation for Scrum Team Size - ✔✔The Scrum Team is small enough to remain
nimble and large enough to complete significant work within a Sprint, typically 10 or
fewer people. In general, we have found that smaller teams communicate better and are
more productive. If Scrum Teams become too large, they should consider reorganizing
, into multiple cohesive Scrum Teams, each focused on the same product. Therefore,
they should share the same Product Goal, Product Backlog, and Product Owner.
✔✔As a Manager, the Product Owner should tell the Developers how to decompose
Product Backlog items into smaller work items of one day or less.
T/F - ✔✔False
For each selected Product Backlog item, the Developers plan the work necessary to
create an Increment that meets the Definition of Done. This is often done by
decomposing Product Backlog items into smaller work items of one day or less. How
this is done is at the sole discretion of the Developers. No one else tells them how to
turn Product Backlog items into Increments of value.
✔✔The Scrum Master is responsible for promoting and supporting Scrum as defined in
the Scrum Guide, how does he or she serve the Organisation? Select the most
appropriate answers. - ✔✔Planning and advising Scrum implementation within the
organization
Removing barriers between stakeholders and Scrum Teams
Helping employees and stakeholders understand an enact an empirical approach for
complex work
leading, training and coaching the organization in its Scrum adoption
✔✔What makes up Scrum - ✔✔- Rules
- Artifacts
- Roles
- Events
The Scrum framework consists of Scrum Teams and their associated roles, events,
artifacts, and rules. Each component within the framework serves a specific purpose
and is essential to Scrum's success and usage. The rules of Scrum bind together the
events, roles, and artifacts, governing the relationships and interaction between them.
✔✔How frequently should Scrum artifacts and progress toward a Sprint Goal be
inspected? - ✔✔Frequently and diligently to enable adaption.
The Scrum artifacts and the progress toward agreed goals must be inspected frequently
and diligently to detect potentially undesirable variances or problems.
✔✔All the Scrum Teams working on the same product should have the same Sprint
length. True or false? - ✔✔False. Scrum does not require having aligned Sprints for
multiple teams.