Software Development Request Management System

Major Business Objects

Example Document (page 3) -- Measurement Criteria & Scope Sign-off   Software Development Request Management System Goal and Objective Measurement Criteria   O-0001: Make a profit.[1] O-0002: Minimize costs. MC-0001: The request backlog is reduced without increasing development costs.   O-0003: Maximize revenue.   O-0004: Be a market leader.   O-0005: Provide a good work environment. DO-0001: Track software development requests. MC-0002: Zero complaints received concerning our having forgotten a request. DO-0002: Provide request status to the organization as needed. MC-0003: The status of a request can be determined by looking it up in the system. DO-0003: Initiate all software development requests in a uniform manner. MC-0004: All software development requests are immediately placed in the request management system. DO-0004: Have software developers be able to grab requests to work on in between other assigned tasks. MC-0005: Developers evaluate and/or implement requests on their own initiative. DO-0005: Group software development requests for maximum development efficiency. MC-0006: The majority of enhancement or maintenance projects are composed of more than one request. DO-0006: (MC-0007): No approved requests wait for action for more than 1 month.[2] DO-0007: (MC-0008): Requests are evaluated and approved or rejected within 1 month. G-0001: (MC-0009): Deploy an Internet/Intranet software request management tool that meets all objectives by 01-Mar-2000. G-0002: Provide statistical measures of the quality of the project deliverables. MC-0010: The PSP and TSP statistical measurements will be collected and included in an appendix. G-0003: Learn and use the Personal and Team Software Processes (PSP and TSP) for the project deliverables. MC-0011: One team member will be appointed as the process manager. They will monitor whether the PSP and TSP method is followed and report weekly progress to the team. G-0004: Develop web-based technology skills. MC-0012: The tool is successfully built and works as designed. IG-0001: Establish our credentials in business rules-based and web-based software development. MC-0013: The book is well received by those who review it and our employers give us a raise. Project Scope Document Sign-off[3]   I understand that development will proceed based upon the information listed in this document. Failure to include or exclude a relevant item within the project scope will adversely affect the project Role Name Signature Date Project Sponsor Project Manager Business Line Expert   Page 3 of 4 [1] By shading this objective, we are noting that measuring it is out of scope of this project. [return] [2] Enough said. It is measurable as stated. [return] [3] The sooner you get a written, formal buy-in, the better. If they won’t agree to the project scope at this point, it’s better to find out now rather than later! [return] (c)2000, Stonebridge Technologies, Inc. Permission to reprint granted to BRSolutions.com