Much has been written about techniques and tools that improve the definition and management of software business requirements-techniques such as planning games, user stories, and use cases, and tools such as UML, and traceability matrices. Over the years, many practitioners have used these tools to achieve major improvements in requirements definition and management.
While honing these techniques, however, many practitioners have overlooked another critical area of the underlying business process elements that knit together these different tools and techniques in a coherent manner across the software organization.
Elements such as decision-making, process work flows, roles and responsibilities, and metrics ensure that the impact of these requirements techniques are felt and sustained across the broader software organization. The following case study illustrates how one software organization achieved significant improvements in software product development costs and effectiveness by putting in place key business process elements that tie together proven requirements techniques.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment