Is the strategy template based primarily on what will be changes in the software?
1) So, in today's environment, what if the change is completely unknown and unpredictable. At this point, the strategy template will not be appropriate for adding (at this point)?
2) What to do if the Program Manager wants to do this in 2 days or as soon as possible, or the faster you complete it, the better you look and the better you will conduct a performance review. If you write it without using a strategy template, you can complete it within 2 days, otherwise PM may underestimate the delay and attribute poor performance to it. In this case, how do you balance implementation speed and maintainability?
3) the same applies to contract programming - for 2 months or 3 months. Wouldn't any programmer or previous programmer on a task just ignore maintainability just to get it done as soon as possible? Do managers really care that the project is 100% functional, as indicated in the specification, does it also have the ability to service?
source
share