Académique Documents
Professionnel Documents
Culture Documents
Situational Interview
Questions
www.mountaingoatsoftware.com
Scope creep
The boss is at a trade show and needs two new
unplanned features by tomorrow. Last week when this
happened, you just put in a little overtime and
wedged it in. Same thing the time before. If you dont
come through, it will cost you sales and your boss will
be mad.
2
Unready stories
In the retrospective, it came up that the stories just
werent really ready for development. Instead of
getting down and coding, the team had to spend
several days going back and forth with the product
owner, analyzing what should happen. Youve pretty
much heard that complaint for three months in a row.
Nothing seems to be helping.
3
Blah retrospective
Our retrospective is so blah! Nobodys willing to
speak up about the real problems.
4
Six months of architecture
Star developer Tom is worried and makes sure the
boss knows it. Theres nothing incremental about this
rst part; no way to divide that into month-sized
chunks. We need at least six months for architecture
only. Really, theres no reason to do sprints: the
product owner cant help. The Scrum meetings are
overhead; lets hold them once a week. Maybe once
the architecture is done we can try the sprint stuff, but
if we do that now, were doomed.
5
Resistant product owner
The product owner says, Theres no point in doing
just parts of these stories just so theyll t into a sprint.
These features arent useful unless theyre all
completely there. And please quit bugging me about
priority. Theyre all equally important. Theyre called
requirements because theyre required!
6
Never time to fix problems
The product owner always picks new functionality and
never picks bug xes. In the end, the crashes and
data corruption have to be xed. Those problems are
already slowing down testing.
7
The frustrated manager
Your manager stops in. Im not happy with the way
the team is working. Youve insisted outsiders cant
change the sprint backlog, and thats hurt us with
Marketing in a big way. Were no longer perceived as
team players. Youve insisted on a lot of early testing;
we're spending way more on that than ever. And
people are complaining that they have to waste time
on the Scrum meeting every single day.
8
Unintegrated work
Three teams are working together on a product.
9
The assigning ScrumMaster
The ScrumMaster on a team manages all task assign-
ments.
10
Overcommitting
The team has over-committed. Team members are
cutting corners on the acceptance tests (well do that
one manually too), and you suspect the unit tests
arent up to their past levels.
11
Automation troubles
The team isnt sure what to do about automating the
acceptance tests. Some people say, It costs so much,
and it hardly nds bugs.
Others are willing to try, but after the rst few days of
experimentation, they dont have anything working.
12
Fixes arent prioritized
The programmers say, We didnt break that during
this sprint. If you want it xed, you have to get the
product owner to prioritize it.
13