Summarize at-a-glance the purpose and approach for undertaking an application development project, for the benefit of your senior level management as well as your customer.
If you and your team have a bunch of application development tools to evaluate, use this form to make the job easier.
The purpose of this document is to develop a project inventory matrix which includes the major projects. The matrix would further help document the planned application architecture and facilitate the design of the future IT and application landscape.
Function points are a measure of the size of a software system. To convert function points into levels of effort, the productivity of the enterprise's development teams must be known or estimated. This three-for-one zipped deliverable includes a document explaining function point analysis, instructions on how to apply a function point analysis and a worksheet set up for an Albrecht function point analysis.
These tips from the trenches offer valuable advice for any project team about to implement an application package.
Know the technical foundation on which you will be setting up your application package -- do a gap assessment of the existing and new technical environment.
A necessary step in both selecting and implementing a package is detailing the technical requirements required to run the application. Identify the hardware/software environment, interfacing systems, operational and backup procedures, and other key technical requirements.
This is not a typical request for information that goes on forever in boring text, putting you and your potential vendors in a coma. It is a useful matrix that succinctly itemizes nearly every criterion for selecting an application vendor.
When will the project start? Who's in charge? This memo template will help you tell it like it is. Remember, inquiring minds need to know!
When there's a whole lot of welding going on, you need to know who is doing it, how and where. Use this form.
|
"It's kind of fun to do the impossible." - Walt Disney |
