Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

IIBA-AAC Exam - Topic 10 Question 59 Discussion

Actual exam question for IIBA's IIBA-AAC exam
Question #: 59
Topic #: 10
[All IIBA-AAC Questions]

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?

Show Suggested Answer Hide Answer

Contribute your Thoughts:

0/2000 characters
Fernanda
4 months ago
I disagree, detailed processes are important too!
upvoted 0 times
...
Nieves
4 months ago
Wait, how did they not see this coming?
upvoted 0 times
...
Martina
4 months ago
I think they were just following the plan too strictly.
upvoted 0 times
...
Yan
4 months ago
I can't believe they wrote a guide for a feature that doesn't exist!
upvoted 0 times
...
Ayesha
5 months ago
Definitely D, working solutions should come first!
upvoted 0 times
...
Laurel
5 months 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.
upvoted 0 times
...
Emeline
5 months 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?
upvoted 0 times
...
Yolando
5 months ago
I'm not entirely sure, but I remember something about prioritizing deliverables over documentation in our last practice question.
upvoted 0 times
...
Loise
5 months ago
I think the team member forgot to value working solutions. If the feature wasn't developed, why spend time on a guide?
upvoted 0 times
...
Jacqueline
5 months 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.
upvoted 0 times
...
Delsie
5 months 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.
upvoted 0 times
...
Tiara
5 months 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.
upvoted 0 times
...
Ernest
5 months 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.
upvoted 0 times
...
Alfreda
6 months 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.
upvoted 0 times
...
Haydee
6 months ago
This question seems straightforward, I think the answer is B - unpaid invoice.
upvoted 0 times
...
Tamar
6 months 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.
upvoted 0 times
...
Ozell
6 months 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.
upvoted 0 times
...
Whitney
10 months 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!
upvoted 0 times
...
Angella
10 months 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.
upvoted 0 times
Muriel
9 months ago
C: Definitely, detailed processes are great, but without a working solution, it's all just theory.
upvoted 0 times
...
Hubert
9 months ago
B: Yeah, following the plan is important, but without a working product, it's all for nothing.
upvoted 0 times
...
Leota
9 months ago
A: I agree, working solutions are what really matter in the end.
upvoted 0 times
...
...
Rodrigo
11 months 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.
upvoted 0 times
Benedict
9 months ago
C: Definitely, following the plan is important but having a working solution is crucial in the end.
upvoted 0 times
...
Glenn
10 months ago
B: Yeah, it's disappointing when all that effort goes to waste because the feature gets dropped.
upvoted 0 times
...
Jesusa
10 months ago
A: I agree, having a working solution is more important than detailed processes.
upvoted 0 times
...
...
Tommy
11 months 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.
upvoted 0 times
Lisha
10 months ago
C) Fixed iterations
upvoted 0 times
...
Becky
10 months ago
B) Detailed processes
upvoted 0 times
...
Anabel
10 months ago
A) Following the plan
upvoted 0 times
...
...
Jessenia
11 months ago
But maybe following the plan could have prevented this issue.
upvoted 0 times
...
Ilene
11 months ago
I agree with Ramonita, working solutions should be the priority.
upvoted 0 times
...
Ramonita
12 months ago
The team member forgot to value working solutions.
upvoted 0 times
...

Save Cancel