3 ms·
I think you're missing a few steps in your development process, or at least one. Normally it goes like this: problem->solution->implementation->testing. Each st
by koonsolo 6y ago
I think you're missing a few steps in your development process, or at least one. Normally it goes like this: problem->solution->implementation->testing. Each step has a role associated with this: user->analyst->coder->tester.
If you go straight from problem to coder, you shouldn't be surprised that you don't have a proper solution, because nobody really made a proper solution. That's like building a house without an architect. Hire an analyst.
- hulitu 6y agoTesting is hard. That's why they let it to the user.
- _pmf_ 6y agoIf I know that the user changes what he originally wanted, damn right I give the thing to the user instead of wasting effort on perfection and edge cases that get thrown out.
- tonyedgecombe 6y agoI don't know. The projects I got involved in that had an analyst involved tended to have reams of documentation for the obvious features, completely missed the non-obvious features and was wildly wrong in parts. This is what agile was created to solve. It was an acceptance of the reality and an attempt to live with that rather than trying to bend it to your will.
- koonsolo 6y agoEven agile teams need someone who analyses the solution. If there is nobody who specifies the solution, you get what OP describes. Agile does not exclude different roles, on the contrary.
- 411111111111111 6y agoMost corporations aren't big enough to warrant dedicated personal for these roles. And if they are, it often ends with impossible to implement/maintain designs.
- koonsolo 6y agoSo 5 developers don't need a tester and business analyst? WTF.
- 411111111111111 6y agoMost developers can write tests and architect software just fine.
- koonsolo 6y agoDevelopers are terrible testers, because they have the opposite mindset. Plus, they are more expensive. So you pay more to get less. Do you think business analysis is about software architecture? Oh boy.
- webmaven 6y ago> Do you think business analysis is about software architecture? Oh boy. Given the tendency for software architectures to mirror org-charts, the two aren't as disparate as you think.
- marcosdumay 6y ago> Each step has a role associated with this: user->analyst->coder->tester. Have you ever played that telephone game?
- koonsolo 6y agoThese are the steps, not the communication channels. Look at any agile team and all parties should be represented in 1 meeting.
- webmaven 6y ago> I think you're missing a few steps in your development process, or at least one. Normally it goes like this: problem->solution->implementation->testing. There should actually be testing associated with every step: Is X a real problem worth solving (severity or cost x frequency)? Would Y be an appropriate solution (test a mockup, prototype, or stub UI)? Does the Z implementation work (as in, not just does the problem get solved when Z is used, but does Z actually get used to solve the problem)?