MENU
In lean software development extra features should be identified as
Suggested Answer: B
Get Premium CSQE Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
In a concurrent development environment, when a problem is identified in an earlier version (Version 1) that originated in a later version (Version 2), the appropriate action involves managing the code versions effectively. Branching the Version 2 codeline is the most appropriate first step because:
Isolation of Changes: Branching allows for the isolation of the problematic code in Version 2, enabling targeted fixes without affecting ongoing development in other versions.
Concurrent Development: This approach supports concurrent development activities, allowing different teams to work on fixing the issue in Version 2 while continuing development on other versions.
30 comments · newest first
EV
Evangelina
10 months ago
Wait, are we sure they’re just waste? Sounds too simple.
VA
Van
11 months ago
Totally agree, waste is the right term here.
DE
Deeanna
11 months ago
No way, they’re just defects in the process.
SH
Sherell
11 months ago
I think they can be potential re-use elements!
KE
Keva
11 months ago
Extra features are definitely waste in lean.
SH
Sheridan
12 months ago
I'm confused; I thought defects were related to bugs, not extra features. Could it be potential re-use elements instead?
MI
Micah
12 months ago
Waste seems to be the right answer since lean focuses on eliminating unnecessary features.
SI
Simona
12 months ago
I remember a practice question that mentioned internal costs of quality, but I feel like that doesn't quite fit here.
AR
Arminda
1 year ago
I think extra features are considered waste in lean development, but I'm not entirely sure.
FR
Francoise
1 year ago
Okay, let me see here. Extra features could potentially be reused, so A is a possibility. But lean is also about quality, so B could work too. I'm going to have to weigh the options carefully before making a decision.
NI
Nicolette
1 year ago
Ah, I think I've got this one. In lean, extra features that don't directly provide value to the customer are considered waste, so the correct answer must be D. Gotta keep that focus on delivering only what the customer needs.
IR
Irma
1 year ago
Hmm, I'm a bit unsure about this one. I know lean is all about minimizing waste, but I'm not totally clear on how that applies to extra features. I'll have to think it through and see if I can eliminate any of the options.
AR
Armando
1 year ago
This seems like a straightforward question about lean software development principles. I'll carefully read through the options and think about which one best fits the description of "extra features" in a lean context.
NA
Nan
1 year ago
I'm no expert, but I'd have to say D) waste. Lean is all about cutting the fat, and extra features are just padding, am I right?
GE
Gertude
1 year ago
Absolutely, extra features that are not necessary for the core functionality are seen as waste in lean principles.
TR
Tracey
1 year ago
That's correct. Lean focuses on delivering value to the customer and eliminating anything that doesn't contribute to that.
OS
Osvaldo
1 year ago
Yes, you're right. Extra features are considered waste in lean software development.
MI
Miles
1 year ago
I feel like the correct answer is D) waste. Lean is about minimizing anything that doesn't directly contribute to the final product.
TH
Thurman
1 year ago
I'd go with A) potential re-use elements. Sometimes those extra features can be repurposed for other projects, so they're not always a waste.
BE
Benedict
1 year ago
Hmm, I was leaning towards B) an internal cost of quality. Extra features can add complexity and make it harder to maintain the codebase.
SA
Sang
1 year ago
D) waste
LA
Latia
1 year ago
C) defects
YV
Yvonne
1 year ago
B) an internal cost of quality
EL
Eladia
1 year ago
A) potential re-use elements
JA
Jani
1 year ago
I'm pretty sure the answer is D) waste. Lean software development is all about eliminating unnecessary features and focusing on what's truly valuable to the customer.
RO
Rory
1 year ago
Yes, focusing on eliminating waste helps improve efficiency and deliver value to the customer.
LU
Ludivina
1 year ago
I agree, extra features are considered waste in lean software development.
HY
Hyun
2 years ago
But what if they can be potential re-use elements in the future?
ZO
Zona
2 years ago
I agree with Sarina, they add unnecessary complexity.
SA
Sarina
2 years ago
I think extra features should be identified as waste.