Scribd
Upload
6 views2 pages

Agile Answers

Agile_answers

Uploaded by

Ramesh Kumar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
6 views2 pages

Agile Answers

Agile_answers

Uploaded by

Ramesh Kumar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

Answers:

1. (B). Developing a persona for a project helps the team understand what the users of their solution
needs and how the solution will be used in real life situations. A persona is not a communication
tool, or a discussion of requirements, rather it is a tool to help understand why a solution is required.

2. (B). A generalizing specialist is a person that is skilled in multiple disciplines. Having this type of
team can share the workload and avoid bottlenecks that many project encounter. A coder that also
has the skills to interview an end user of the product a handoff can avoided from the interviewer to
the coder which will avoid a misinterpretation and save time and money.

3. (‘C). Without limits on WIP, a project team may undertake too many different tasks at once.
Although, this may be done to keep people busy and utilize everyone’s availability, but the problem
is it becomes difficult to identify any roadblocks in processing requests. Tasks may end up sitting
without being worked on and accumulating. This makes it difficult to identify where the roadblock
has occurred because everyone looks so busy.

4. (C). One part of system thinking includes classifying projects in term of their complexity in two
areas: project requirements and the technological approach. Complex projects have some
uncertainty with requirements and technology, so are well suited for the out of the box agile
methodology. Project that has a low or simple complexity can tailor some of the agile methods to
suit the project.

5. (B). Avoiding potential downsides in a project.

6. (A). Agile planning is based on value-based analysis meaning the business value of the deliverables
are analyzed and delivered first.

7. (A). Working software

8. (D). Scrum teams value focus because even a small number of interruptions every week can cause
significant delays, and the frustration from interruptions can seriously demotivate the team. As a
servant leader, the scrum master needs to pay attention to anything that demotivates the team in
order to keep morale high and the team productive. So, while a servant leader typically does not
have the authority to grant permission to skip meetings called by the manager, it is absolutely within
the scrum master’s role to approach that manager and find ways to keep the interruptions to a
minimum.
9. (C). Determining the root cause of a quality problem is an important first step to fixing a problem,
and an Ishikawa (or fishbone) diagram is an effective tool for doing root cause analysis.

10. (C). Agile teams handle maintenance and operations work exactly the same way that they handle
any other work. If bug fixes are critical, the team will work on them at the next opportunity. And the
next opportunity, in most cases, is the start of the next iteration. Note: Stopping work immediately
to change directions introduces chaos and is not an effective way to change priorities. Agile teams
use iterations so that they can respond to change quickly without letting their projects spin out of
control.

11. (C). Agile team members work hard to identify their projects business stakeholders and make
sure that everyone on the team has a good understanding about what they need and expect from
the project. But requiring stakeholders to attend planning meetings and requiring a sign-off on the
plan does the opposite, it will make them feel less engaged, and create bureaucratic hurdles that
prevent the team from responding to change. Note: read every question carefully, and especially
watch out for, which-is-not questions.

12. (C). One of the most important jobs that a product owner has a SCRUM team is making sure that
new stakeholders are appropriately engaged in the project. Ideally, all stakeholders will attend every
sprint review. However, there is no rule that says that every stakeholder must attend them or are in
another time zone that makes it difficult for them to attend, or simply don’t want to. It’s the product
owner’s job to do whatever it takes to make sure those stakeholders are involved, using whatever
manner works best for them.

You might also like