4 ms·
A good thing about waterfall is the documentation it generates. We switched to Agile 10 years ago, didn't manage the outsourcing all that well and now we are in
by sgt101 8y ago
A good thing about waterfall is the documentation it generates. We switched to Agile 10 years ago, didn't manage the outsourcing all that well and now we are in the same position as then but without the documentation. More and more I wonder how we can get teams to write about what they are doing and teach the next team how everything works... sadly people suspect that such efforts will be used to outsource and offshore, but without them it's impossible to pick apart what's happened and rationally work out where to go next.
- ___alt 8y agoThinking that "Working software over comprehensive documentation" means "don't write documentation" is one of the biggest misunderstandings about agile and I feel your pain.
- Murk 8y agoI've seen this a number of times. People (management and team alike) have said to me things along the lines of: "We don't have documentation, we are agile." Which, of course is not what the agile manifesto says, but is how some people have taken it. Other sayings are "The spec is in the tickets, there is no user manual." "We have unit tests." and so on. All this makes trouble - Especially when you consider in order to change a thing, you should aim to understand it's salient parts in the first place - but perhaps that is not agile or the scrum way according to some.