Tag Info

Hot answers tagged

5

Is this acceptable in agile scrum? Define "acceptable". In some environments, it's fine. In most, it is prohibitively problematic. That problem is that most Business Analysts are horrrrrible. Even when they understand the product well, and even when they can define and scope features, they rarely understand much of the implications of the feature to ...


4

I believe the problem is not about what documentation you should ask for. It is about how you can check that it is valid and will actually help new developer to pick up where previous left. It is easy for you to check if actual feature works, but not easy to check the documentation, no matter what kind of documentation you will request. This is how I would ...


3

I think the chances are that you do NOT want any code documentation from the programmers. The reason you state that you think you might want documentation is : "Can the new programmers do a good job of taking over when there's no report or documentation, etc" So the documentation isn't for you to read, its not a manual for the product, It dosnt give you ...


1

You want a high-level design document that describes the big blocks and their interaction and then functional design that describe how these blocks were implemented. Read up on UML for the main design concepts (but do not make them deliver UML docs, please - they go into too much detail, you only want the overviews) Often the documentation can be sufficient ...


1

You can use annotations: @javax.annotation.concurrent.Immutable from JSR-305 or @net.jcip.annotations.Immutable from Java Concurrency In Practice



Only top voted, non community-wiki answers of a minimum length are eligible