Timeline for Agile - What we doing wrong?
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 7, 2018 at 16:53 | comment | added | Bryan Oakley | @Erik: excellent comment. That's why I originally wrote _"to come to an understanding of what they need" rather than "... they want". I can see, however, that that's not emphasized much. I'll add a bit more emphasis and explanation. Thanks for the comment. | |
| Jul 7, 2018 at 16:53 | history | edited | Bryan Oakley | CC BY-SA 4.0 |
added 160 characters in body
|
| Jul 7, 2018 at 5:56 | comment | added | Erik | When working with the client, make sure you figure out what they need, not what they say they want. Pretty much any client will pick the cheapest and fastest solution to every problem, it's the engineering team's job to figure out what the cheapest option is that still covers all the things they really need. | |
| Jul 6, 2018 at 16:59 | history | edited | Bryan Oakley | CC BY-SA 4.0 |
added 492 characters in body
|
| Jul 6, 2018 at 16:33 | history | answered | Bryan Oakley | CC BY-SA 4.0 |