Timeline for Development solution rushed prior to agreement on requirements - is this a healthy project management?
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 10, 2018 at 3:19 | comment | added | Vicki Laidler | To chime in on the "design before code" question: there's an agile slogan, "Build the wrong thing fast" (I would add, "and cheaply"). The idea is that the first thing you build will inevitably be not quite right, and that it's more cost effective overall to build something quickly that people can actually use and give meaningful feedback on, so that the next iteration will be closer to what they want. | |
| Nov 5, 2018 at 8:02 | comment | added | Barnaby Golden | There is nothing wrong with doing some up-front design. However, it is important to realise that people are usually much better at giving feedback on a working application than they are on a design. The trick is to find the right balance for your team - enough up front design to get started, but then also allowing room for changes resulting from feedback once the client sees the application. This is what agile is all about - anticipating and adapting to change. | |
| Nov 5, 2018 at 2:05 | comment | added | VincentPzc | I've also suggested to the PM to let the developers take more ownership of development, e.g: let them decide/plan how the functions/database should work since they know what's the best for it. But the PM seems to be doubting their capabilities and would made the team to design based on the PM suggestion. Sometimes, I do feel that the PM is crossing the line by being micro-managing the technicalities aspects. Occasionally, the dev. team solutions seems complicated (they wanted to ensure the base coding has scalability in future), but the PM would insists to make things simple. | |
| Nov 5, 2018 at 1:04 | comment | added | VincentPzc | Hi Barnaby! Thanks for your valuable information! I agreed with implementation for design. But isn't it better if we draft the solutions and present to client before the developers begin the coding? I'm not sure if this is applicable in agile. Hope you could advice me! | |
| Nov 4, 2018 at 22:33 | history | edited | Barnaby Golden | CC BY-SA 4.0 |
added 2 characters in body
|
| Nov 3, 2018 at 12:03 | history | answered | Barnaby Golden | CC BY-SA 4.0 |