Tag Info

New answers tagged

0

Ultimately, user stories translate into software requirements, and so do features. All high-level descriptions of software should ultimately translate into individual software requirements that are Specific, Measurable, Assignable, Realistic, and Timely. If you get this right, then you're doing it "correctly," assuming your requirements gathering process ...


3

It appears to me that you have a fundamental problem with your components. C should do what C needs to do, and be tested, documented and designed to do just that. When you have a situation where C is designed to "do what B wants" you have an abusive relationship, one that becomes very clear when A arrives and wants C to do something slightly different. ...



Top 50 recent answers are included