March 2006
Beginner to intermediate
618 pages
15h 20m
English
Content preview from Effective Software Project Management
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.
The Volere Process
Perhaps the most documented and complete approach to requirements gathering is found in the Volere Process. You can use it as a base for the process that I recommend to gather requirements.
Gathering Customer Requirements
Simply put, IS teams who make a concerted effort to manage customer requirements do so because they want to satisfy their customer needs by having their projects succeed. Research studies find that the majority of project failures are related in some way to changing customer requirements.
This section is based on a modified Volere Requirements Process and its associated Specification Template. I have found this to be a best practice. Originally designed for use in systems application development, the process is a generic requirements gathering and specification process whose principles can be applied to small and large projects across varied industries. These processes are discussed in detail in the next section. Before I get into those details, I need to put a few definitions in place.
What Are Requirements?
Requirements are the things that you should discover before starting to fully design, build, or execute a project. Discovering the requirements during execution/construction is inefficient and detrimental.
A requirement exists either because the type of product demands certain functions or qualities, or the client wants the requirements to be part of the product/ project delivery.
Project requirements start with what the customer really ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access
More than 5,000 organizations count on O’Reilly
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.Julian F.
I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.Addison B.
I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.Amir M.
I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.