MENU
Your customer has a small-scale implementation with a tight timeline. Which release strategy best suits this scenario?
29 comments · newest first
GL
Glynda
7 months ago
I agree with B. It’s safer for tight deadlines.
BR
Brittani
7 months ago
B balances speed and control. Less stress!
SY
Sylvie
7 months ago
D is great for speed, but may overwhelm the team.
ME
Merilyn
8 months ago
C is good for testing, but might delay the timeline.
JE
Jestine
8 months ago
A seems risky. Too many features at once!
GW
Gwen
8 months ago
I think B is the best choice. It allows for adjustments.
DO
Dominic
9 months ago
Not sure if any of these will meet the tight deadline honestly.
DI
Diane
9 months ago
Wait, can you really do a pilot deployment in such a short time?
MA
Marsha
9 months ago
B) Phased approach with incremental releases and controlled rollouts. Slow and steady wins the race.
GE
Germaine
9 months ago
D) Continuous integration and continuous delivery (CI/CD) for rapid iterative updates. Ain't nobody got time for big bang deployments!
SA
Sabra
9 months ago
C) Pilot deployment with a limited user group for initial testing and feedback. Gotta get that user input before a full release!
MA
Marget
9 months ago
I feel like pilot deployment could be useful for gathering feedback, but it might delay the overall timeline too much.
CA
Carman
10 months ago
CI/CD sounds appealing for rapid updates, but I wonder if it’s too complex for a small-scale implementation.
NA
Nathan
10 months ago
I remember a practice question where the big bang deployment caused issues. It seems risky for a tight timeline.
MA
Margarita
10 months ago
Easy choice - phased approach all the way. Tight timeline means we can't afford a big bang or pilot, and CI/CD might be overkill. Incremental releases are the way to go here.
SH
Sharee
10 months ago
I'm a bit confused here. The phased approach seems like the safest bet, but the CI/CD option could be really useful for rapid iterations. I'll have to weigh the pros and cons of each approach.
BR
Brittni
10 months ago
Definitely going with the phased approach on this one. Incremental releases will let us get features out quickly while minimizing risk. The other options just don't seem as well-suited for a small project with tight timelines.
DE
Dell
10 months ago
B) Phased approach with incremental releases and controlled rollouts. This allows for gradual rollout and feedback gathering.
AP
Apolonia
11 months ago
Big bang deployment sounds risky for a small-scale project.
AB
Abraham
11 months ago
I think the phased approach might be the best fit since it allows for controlled rollouts, but I'm not entirely sure.
JE
Jerrod
11 months ago
I think CI/CD could work if they have the right setup.
CA
Catherin
11 months ago
Phased approach is usually safer for tight timelines.
SH
Shenika
11 months ago
Hmm, this is a tricky one. I'm leaning towards the phased approach, but the CI/CD option also seems promising for rapid updates. I'll need to think this through carefully.
LO
Louvenia
12 months ago
I think the phased approach with incremental releases would be best here. Tight timelines mean we can't do a big bang, and a pilot would take too long. CI/CD could work but might be overkill for a small-scale project.
GL
Glory
6 months ago
Incremental releases keep it manageable and efficient.
BR
Brittni
6 months ago
A pilot could slow us down too much.
SH
Shawnna
7 months ago
CI/CD might complicate things for a small project.
FR
Franklyn
7 months ago
Definitely! Big bang could lead to chaos.
LE
Leota
7 months ago
I agree, the phased approach makes sense. Less risk.