Timeline for What to do about manager who does not want to give detailed requirements?
Current License: CC BY-SA 3.0
16 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 23, 2018 at 8:28 | comment | added | user48276 | Two words that will dramatically change your life: Acceptance Criteria. | |
| Mar 22, 2018 at 13:20 | answer | added | WendyG | timeline score: 1 | |
| Mar 22, 2018 at 12:56 | vote | accept | Sh4d0wsPlyr | ||
| Mar 22, 2018 at 5:30 | history | tweeted | twitter.com/StackWorkplace/status/976692572713349120 | ||
| Mar 21, 2018 at 23:20 | comment | added | Fattie | This is the single most common question on this site. "Surprisingly, software development is a shambles." It has been discussed so often there's nothing more to say. | |
| Mar 21, 2018 at 19:51 | history | edited | Sh4d0wsPlyr | CC BY-SA 3.0 |
added 52 characters in body
|
| Mar 21, 2018 at 19:49 | comment | added | Sh4d0wsPlyr | @tima The owner would be the final say, possibly my manager depending on the situation (since it is signed off by manager as completed before the owner sees it). However my manager is in a similar situation to myself (with the added advantage of being at the company for 10+ years and having developed the product). | |
| Mar 21, 2018 at 19:31 | comment | added | user69461 | so what happens if in your example you only changed the column in the X report and didn't change it in the other reports? Who decides that this is a mistake? And is the given requirement ignored? | |
| Mar 21, 2018 at 19:26 | comment | added | Sh4d0wsPlyr | @tima One additional thought - the flow changes are also outside specialty. I'll pick an example (randomly) but our software deals with "Medical" supplies, and as a developer I do not understand how certain supplies might be used, handled, etc. | |
| Mar 21, 2018 at 19:25 | comment | added | Sh4d0wsPlyr | @tima Sorry, this is not specifically a code change only. These happen of course and are a mistake, but not the real cause of frustration. Specifically, these would be things like business practices or workflow. A quick example might be "We have one report called X that shows this column, please change it to show (something different)". However there is actually X, Y, and Z reports (all unique) but have that same column presented in different ways. We might only change the one mentioned in the request and not look at the others. | |
| Mar 21, 2018 at 18:48 | comment | added | user69461 |
...we tend to make mistakes. We will see a place something was implemented and do the same thing, but not realize an entirely different section of code needs the same change. Or we will be asked to implement a feature, but not realize the implications across the application in other areas. These mistakes are your (dev team) fault. I would expect you to know the codebase and know how a change in one area affects another area. Why would your boss know this?
|
|
| Mar 21, 2018 at 15:27 | answer | added | dwizum | timeline score: 2 | |
| Mar 21, 2018 at 15:21 | answer | added | Daniel | timeline score: 10 | |
| Mar 21, 2018 at 15:20 | answer | added | Isaiah3015 | timeline score: 8 | |
| Mar 21, 2018 at 15:15 | answer | added | Jim Horn | timeline score: 2 | |
| Mar 21, 2018 at 14:59 | history | asked | Sh4d0wsPlyr | CC BY-SA 3.0 |