Web prioritization

KCTCS Web Services Prioritization Process for Web Application Development

These are the required steps when you have an idea for new web tools or content. These are intended to help you understand how to move existing tools or content into the KCTCS Web Services model.

Summary

If the need for a web-related project arises, it will follow these steps.

1. Determine if your project should be handled locally (updates and minor work) or through the Web Services Model (new purchases, new sites, new applications, migration of existing tools or sites).
2. If it is not a local issue, make a project request.
3. The request must be approved by a college president or member of the KCTCS Cabinet prior to review by Web Services.
4. Web Services will review the request, score it according to the PLT's priority scoring model, and with your help will make a recommendation to leadership.
5. Leadership will approve and prioritize the project, or will reject it.
6. Approved projects will be formally project-managed by the WSPT, with appropriate sign-offs by Leadership and project sponsors.

Detailed Process

1. Is your project:

   • A change to existing text or images on a limited number of web pages?
     This is a content issue, and can be handled directly by your local Web Services staff.
   • A new section of an existing web site that requires only text, images, or simple web forms?
     This is a content issue, and can be handled directly by your local Web Services staff if no significant web development is required.
   • A suggested purchase of a web-based system?
     This is a purchasing issue, and Web Services must be involved. Go to step 2.
   • A new web site for a KCTCS entity without a current site?
     Unless it is a small web site with very limited requirements for development and there is an urgent need for the site to be built right away, this is a development issue. Go to step 2.
   • A new web-based tool?
     This is a development issue. Go to step 2.
   • An existing web-based tool requiring migration or enhancement?
     This is a development issue. All KCTCS-developed web content or applications will be moved to the new Web Services Model. Go to step 2.

      

2. Prioritization

   1. First, make your project request online, including approval by a college president or member of the KCTCS Cabinet.
   2. Your request will be evaluated and scored according to the PLT's priority scoring model, and a recommendation will be made to leadership regarding your requested project.
   3. Leadership will consider the recommendation and decide whether to approve the project. If approved, the project will be placed on the official priority list by Leadership and the impact on other projects will be communicated. Go to step 4.
   4. If the project is not approved, it will be placed on hold for 180 days, at which time it may be eligible for review. Start over at step 1.
   5. If the decision is to investigate the purchase of a product or service, go to step 3.
   6. If the decision is to develop a KCTCS solution, go to step 4.
       

3. Purchasing

   • All web-related purchases must follow proper business procedures and comply with all relevant policies.
   • A purchasing committee may be formed if an RFP or other formal bidding process is required. This committee will comprise the person who originally submitted the request (or a delegate), a member of the Web Services Peer Team assigned by the System Director of Web Services, and a System Office Purchasing agent. Other committee members may be assigned as necessary.
   • The role of the Web Services Peer Team member on these committees is to ensure selected products and services comply with KCTCS, legal, and technical standards as well as being suitably compliant with KCTCS Web Services environments.
   • Once a service or product is selected, the project moves into the implementation phase. Go to step 4.
      

4. Development/Implementation

   • If the project is assigned for development, or a purchase is made and assigned for implementation, it will be undertaken in priority list order. ALL priority list projects will be formally project-managed by employees with project management training and experience.
   • If a project is to be developed by consultants, the System Director of Web Services will assign resources and budget according to Leadership instructions.
   • If a project is to be developed internally, it will follow the Web Services Peer Team’s web development procedures. These procedures include provisions for participation by college developers who:
     • Have completed required certification criteria (if the employee is to work in the formal development environment)
     • May help create proofs-of-concept outside the formal development environment (but still as part of the formally project-managed process)
     • Have been released by their college president to work on the project
     • Will report, for the purposes of the project only, to a project manager who is authorized to make assignments to the developer for the approved project only.
   • Development projects will have formal change control, testing, approvals, and release plans as specified in the project charter. Every project will have an approved project charter prior to development of the project plan.