MENU
A team member has written a full user guide about a feature that has not yet been developed. Shortly before delivery is to start, the feature is dropped. What did the team member forget to value highly?
Suggested Answer: C
Get Premium IIBA-AAC Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
33 comments · newest first
FE
Fernanda
11 months ago
I disagree, detailed processes are important too!
NI
Nieves
11 months ago
Wait, how did they not see this coming?
MA
Martina
12 months ago
I think they were just following the plan too strictly.
YA
Yan
12 months ago
I can't believe they wrote a guide for a feature that doesn't exist!
AY
Ayesha
1 year ago
Definitely D, working solutions should come first!
LA
Laurel
1 year ago
I feel like it could be about fixed iterations too. If the feature was dropped, they should have adjusted their focus to what was actually being delivered.
EM
Emeline
1 year ago
This seems similar to that case study we did on Agile principles. Maybe they focused too much on following the plan instead of adapting?
YO
Yolando
1 year ago
I'm not entirely sure, but I remember something about prioritizing deliverables over documentation in our last practice question.
LO
Loise
1 year ago
I think the team member forgot to value working solutions. If the feature wasn't developed, why spend time on a guide?
JA
Jacqueline
1 year ago
I think the key here is that the feature was dropped shortly before delivery was supposed to start. That suggests the team member focused too much on following the plan and documentation, rather than making sure the actual feature was built and ready to ship. I'm going with A for this one.
DE
Delsie
1 year ago
I'm a bit confused by this question. I'm not sure if it's asking about what the team member should have valued, or what they actually did value. The wording is a bit ambiguous to me.
TI
Tiara
1 year ago
The answer has to be D - working solutions. The team member wasted time on documentation for a feature that never materialized, so they clearly didn't value actually delivering a working product.
ER
Ernest
1 year ago
Hmm, I'm a little unsure about this one. I think it could be about valuing the detailed processes, since the user guide was written without the feature actually being developed. But I'm not totally sure.
AL
Alfreda
1 year ago
This one seems pretty straightforward. The team member should have valued the actual working solution over just documenting a feature that never got built.
HA
Haydee
1 year ago
This question seems straightforward, I think the answer is B - unpaid invoice.
TA
Tamar
1 year ago
I've got a good handle on private blockchains, so I'm confident I can tackle this. The main focus is on eliminating intermediaries and creating a distributed database for CRUD operations.
OZ
Ozell
1 year ago
I think the pXGrid Controller is the node that enables Cisco ISE to share contextual information with Cisco Stealthwatch. That's my best guess.
WH
Whitney
1 year ago
I bet the team member who wrote that user guide also enjoys wrapping presents for a living. Hey, at least they'll have plenty of time to practice their origami skills now that the feature got dropped!
AN
Angella
1 year ago
Following the plan is important, but not as crucial as actually delivering a working product. This question is a no-brainer - D) Working solutions is the way to go.
MU
Muriel
1 year ago
C: Definitely, detailed processes are great, but without a working solution, it's all just theory.
HU
Hubert
1 year ago
B: Yeah, following the plan is important, but without a working product, it's all for nothing.
LE
Leota
1 year ago
A: I agree, working solutions are what really matter in the end.
RO
Rodrigo
2 years ago
Detailed processes are great, but if the feature gets dropped, all that effort was for nothing. D) Working solutions is the obvious answer here.
BE
Benedict
1 year ago
C: Definitely, following the plan is important but having a working solution is crucial in the end.
GL
Glenn
1 year ago
B: Yeah, it's disappointing when all that effort goes to waste because the feature gets dropped.
JE
Jesusa
1 year ago
A: I agree, having a working solution is more important than detailed processes.
TO
Tommy
2 years ago
The team member clearly forgot to value 'Working solutions' - that's the entire purpose of software development, not just documenting features that don't exist! What a waste of time.
LI
Lisha
1 year ago
C) Fixed iterations
BE
Becky
1 year ago
B) Detailed processes
AN
Anabel
1 year ago
A) Following the plan
JE
Jessenia
2 years ago
But maybe following the plan could have prevented this issue.
IL
Ilene
2 years ago
I agree with Ramonita, working solutions should be the priority.
RA
Ramonita
2 years ago
The team member forgot to value working solutions.