Geek Answers Handbook

Identify New Features

I'm curious how other development teams describe new features. The team I just moved with has no real specification process. I just implemented the proper development process with CI, automatically deploying and logging all errors using Trac, and now I'm moving on to the changes.

I have a list of about 20 changes to our product that you made over the next 2 months. Usually I just talked about each change detailing what needs to be done, but I'm curious how other teams do it. Any suggestions?

+5
source share
2 answers

I think that we had a successful approach at my last job, as we delivered the project on time and with only a few problems found in the workplace. However, only 3 people worked on the product, so I'm not quite sure how it will scale for larger teams.

We have written specifications for the entire product, but without going into details and with emphasis on the user interface. This was a means for us to understand what should be done, and for the scope of the project.

- , ( - - ). ( ). , , .

, , . , ( ).

+1

, . , , , , , , , . , , , ?

+1

More articles:


All Articles