Writing good requirements takes time and practice, and even with all the new tools designed to help you, it will not happen overnight. You need a clear and organized mind, excellent communication skills and good people skills.
With over 70% of project failures being attributed to requirements gathering, why are we still using the same techniques and expecting different results? Requirements need to be discovered before they can be "gathered"--and this requires a robust approach to analyzing the business needs.
The practices presented in this article--to build a requirements tree, create and use a requirements traceability matrix, and manage to requirements baselines--will make a significant difference in an organization’s success rate and promote improved partnership and standing within the enterprise.
Are you making the same mistakes over and over again? Managing the requirements well is critical for project success. Do this, and you will succeed. Fail to do this, and you'll suffer the consequences.
An agile architecture and design should be right-sized to fit the scope of the release plan and no more. This is true whether the architecture is created in a traditional top-down or agile bottom-up style. This means that an agile architecture and design can be visualized within the initial release planning phase when a lightweight plan is created--and the most business value to a customer is achievable. Here are some of the practices for agile architecture and design.