MOC EXAM 25Q Agile 68% 101->125

Question 1

You are leading a coaching session with your project team on the additional Agile and Lean frameworks that have contributed to the Agile way of work. What frameworks will you share with the team?

• Project Management Plan, Project Charter
• Scaled Agile Framework, Large Scale Scrum
• Working Group Meetings, Project Post Mortems
• Flow Charting, Affinity Diagrams

Answer 1

Agile and lean frameworks include:
- Scaled Agile Framework (SAFe),
- Large Scale Scrum (LeSS),
- Scrum of Scrums,
- Dynamic Systems Development Method,
- along with the more common Kanban, eXtreme programming and Scrum.

The Agile Practice Guide (2017), p110

Question 2

You are working on a project in the role of Scrum Master, and have set a meeting with the team and the product owner to refine the product backlog. What should the team do in this meeting?

• Estimate and refine the work items
• Prioritize the work items
• Add features to the project backlog
• Identify fixes

Answer 2

The Product Owner adjusts the priority of product backlog items.

The team is responsible for elaborating on and then estimating the effort for their work items.
Each time the team refines their estimates with a higher level of detail.

Question 3

You are working with a team who would like to become Agile. The functional manager asks you what the difference between Kanban and Scrum is. What will you tell them?
* Kanban teams plan their work in sprints or iterations.
* There are no WIP limits in Kanban.
* Kanban teams work on a project as a whole.
* Kanban teams employ a pull system.

Answer 3

The main difference between Scrum and Kanban is that Kanban teams employ a pull system. This means when an item of work is completed, it triggers someone to “pull” the next item in the queue onto the board to work on. Kanban teams work off a Kanban board that displays each task, and have a limit to how much work in progress (WIP) can be in place.

Question 4

For Agile life-cycles, two kinds of planning occur, release planning and iteration planning. In release planning, business representatives establish and prioritize the user stories for the release, in collaboration with the team, refining larger user stories into a collection of smaller stories. What is the INCORRECT description below regarding iteration planning and backlog preparation?

• The backlog is the ordered list of all the work, presented in “story” form, for a team.
• The project coach encourages the team to work alone, so no one bothers them.
• The facilitator encourages the team to work in triads of a developer, tester, and product owner/business analyst.
• The triad discuss, write, and then place enough stories into an iteration, and enough features for a first release.

Answer 4

Answers A, C and D are correct in describing Backlog Preparation for Iteration Planning. The Agile Practice Guide (2017), p53, 5.2.3

Question 5

Behaviour-driven development (BDD) allows a developer to focus on testing the code based on the expected behaviour of the software and is a method of writing user stories. What is the correct description regarding BDD acceptance-based criteria?

• Make, Buy, Do
• Tell, Show, Repeat
• Find, Create, Perform
• Given, When, Then

Answer 5

Given, When, Then is the way BDD is used, particularly when outlining user Story Cards for your iteration. It highlights :
“Given” a certain situation, “When” something happens, “Then” we want this to happen.

Question 6

Every project has characteristics around requirements, delivery, change and goals. Understanding the different types of life cycle will allow you to choose the right one for the circumstances of your project. What is the correct description for an “Iterative” project approach?

• Dynamic requirements, repeated until correct, in multiple deliveries.
• Dynamic requirements, repeated until correct, in a single delivery.
• Fixed requirements, repeated until incorrect, in a single delivery.
• Fixed requirements, performed once for a given increment, in a single delivery.

Answer 6

💡 “Iterative” methods have dynamic requirements, repeated with feedback until they are correct, but delivered only once. The Agile Practice Guide (2017), p18, Table 3-1.**

Question 7

Every project has characteristics around requirements, delivery, change and goals. Understanding the different types of life cycle will allow you to choose the right one for the circumstances of your project. What is the correct description for an “Incremental” project management approach?

• Fixed requirements, activities performed once, in multiple deliveries.
• Dynamic requirements, activities repeated until correct, in one large delivery.
• Dynamic requirements, performed once for a given increment, in frequent smaller deliveries.
• Fixed requirements, performed once for a given increment, in frequent smaller deliveries.

Answer 7

💡 Incremental project management approach includes dynamic requirements, performed once for a given increment, with frequent smaller deliveries.
The Agile Practice Guide (2017), p18, Table 3-1.

Question 8

You are working with a team that is new to Agile and are using Scrum to manage the project. The business representative is confused about the difference between a “sprint review” and a “sprint retrospective”. What will you tell them?

• Sprint reviews demonstrate the work completed in the sprint. Sprint retrospectives look at all the work completed in the project.
• Sprint reviews discuss what is worked on in the sprint. Sprint retrospectives are done at the end of the project for a lessons learned opportunity.
• Sprint reviews review the lessons learned. Sprint retrospectives look at the history of the product retrospectively.
• Sprint reviews are for product demonstrations. Sprint retrospectives are for lessons learned.

Answer 8

💡 Sprint Reviews are for product demonstrations.
Sprint Retrospectives are for lessons learned, where we ask “What went well, what didn’t go well, what did I learn?”

Question 9

While meeting with the customers or business owners, they introduce several pieces of new functionality into the product backlog list. The deadline for the product cannot be changed. What will you do next?

• Tell the team to work overtime in order to deliver the project
• Stand by your team and tell the customers the project will not be delivered on time
• Be sure the customers understand that lower priority features may not be completed at all
• Place the new features in a “parking lot” that can be completed if time allows

Answer 9

An Agile project can accept changes even late in development. But while the competing constraints of cost, quality and schedule are often fixed, in Agile the scope can vary. This means some features may need to drop off, as others become prioritised. A maintainable pace of work is required too - project managers must not overwork the project team to increase the pace of the project work.