You know, I was leaning towards B at first, but now I'm actually thinking D might be the best answer. Having a clear, stable set of requirements is key to delivering value efficiently in Lean, isn't it?
Haha, poor requirements and scope creep? That's always a pain, no matter what development approach you're using. But I'd say A is the way to go here - Work in Process and bugs are the bane of any Lean project.
I'm not so sure about that. I think C is also a strong contender - getting rid of defects and low-value features seems crucial in a Lean environment. You want to laser-focus on the high-impact stuff, you know?
Hmm, this is a tricky one. I think the obvious answer is B - eliminating delays and building what's not needed. That's the core tenet of Lean, right? Minimizing waste and optimizing the flow of value.
upvoted 0 times
...
Log in to Pass4Success
Sign in:
Report Comment
Is the comment made by USERNAME spam or abusive?
Commenting
In order to participate in the comments you need to be logged-in.
You can sign-up or
login
Broderick
8 months agoMalcolm
8 months agoCarissa
8 months agoCatarina
8 months agoAlton
8 months agoNorah
8 months agoBenton
8 months ago