Page: 1...... 28 29 30 31 32 33 <prev
Project managers must constantly clarify the requirements behind the faster-cheaper-better mandate, and negotiate their relative importance to the project. Here is a framework of inquiry, applied to three seemingly straightforward initiatives, that calls out the non-obvious contradictions in this ubiquitous mandate. On your real-world projects, this exercise could prove to be a "better" way to meet expectations.
The secret to rapidly capturing requirements lays in understanding the business processes that the application is suppose to leverage and support. And it is in the gap between how things work today and how they need to work to achieve core business objectives that the fruit of the requirements tree can be harvested.
The secret to rapidly capturing requirements lays in understanding the business processes that the application is suppose to leverage and support. And it is in the gap between how things work today and how they need to work to achieve core business objectives that the fruit of the requirements tree can be harvested.
On software projects, nonfunctional technical requirements such as performance, security and reliability must be considered throughout the development lifecycle, regardless of the methodology you follow. Here is a primer on defining these requirements, and best practices for avoiding some common pitfalls.
One of the most difficult phases in project management is gathering business requirements. Many stakeholders simply don't know how to articulate what they want, or why they want it. Project managers who build trust will get better results.
Page: 1...... 28 29 30 31 32 33 <prev
|
"Seriousness is the only refuge of the shallow." - Oscar Wilde |
