Apply Yourself | ||||||||||||
 |
|
|
|
|
|
|
|
|
|
|
|
|
 |
||||||||||||
 |
[ Login/Subscribe ] | |||||||||||
 |
||||||||||||
 |
 |
 |
 |
 |
 |
 |
|
 |
||||
 |
||||||||||||
Features
Departments
Executive
Resources
|
Home > Departments > Methods & Means
Requirements have been finalized, the development cycle is underway and stakeholders are ready to wait until the application is released for user acceptance testing. Not so fast. Here are six neglected supporting activities that will increase the chances of success on application development projects.
In any software development project, the business user community needs to be heavily involved in the concept and requirements stages of the application to ensure that the product solves the problem it is intended to solve. From the initial concept and business justification phase, it is paramount that the project manager takes all steps necessary to ensure consistent and committed buy-in from the business user group and top management.
You may believe that having business users participate in requirements meetings is sufficient, but it is also your job to show them what’s in it for them and how the project will relieve day-to-day burdens. This engagement should be continued throughout all phases of the project and requires a hands-on, nurturing approach as the software is being developed.
In overseeing many software development projects, I have identified six key areas that should be given attention concurrently with the actual coding of the system.
Please login/register to read the entire article.
| |||||||||||||||||
|
Privacy Policy Contact Us User Agreement