project plan for web startup1

7/28/2019 Project Plan for Web Startup1

1/61

eVisionfor Texas Workforce Network

Project Name

Workplan

Startup

Project Startup

Resp.

PartyStatus

Hours

To

Date

Est.

Hrs to

Comp

Begin

Date

Sched.

Comp.

Date

Actual

Comp.

Date

Pri-

orityComments

Staff ing

Determine skill sets required for management and staff

Determine number of technical and program resourcesrequired

Identify or hire full-time project managerIdentify or hire TWC analysts/programmersRequest program project manager, steering committee

members and signatoriesRequest program or functional expert resources

Identify administrative support staff and supply channels

Develop project organization chart with accompanying list ofroles and responsibilities

Develop project contact listDevelop/collect orientation materials for all staff

Staff Training in Tools and Proc edures

Standards and ResourcesConduct training on project vision & objectives

Conduct training on team member roles & responsibilities

Conduct training on all standards and templates, includingwriting standards

Ensure all project team members are following workplaceguidelines and have PC set up correctlyProject management software

Version control softwareDefect tracking software

Flow charting/diagramming software

Programming Standards and ToolsTWC Web Development StandardsVisual Age for Java or WSAD

CVSDB2

R:\Inet_Global\Project Management\Project Plans\148859296.xls.ms_office\Startup

Page 15/31/2013 3:07 AM


2/61


Project Name

Workplan

Startup

Resp.

PartyStatus

Hours

To

Date

Est.

Hrs to

Comp

Begin

Date

Sched.

Comp.

Date

Actual

Comp.

Date

Pri-

orityComments

Provide copy of File-AID for DB2 Reference Manual, if

neededDetailed design/ spec pack standards and templates

Websphere Studio (for team leads)

Web Foundation

GASS

Migration standards and proceduresVersion control

Bugzilla - defect tracking

Application code & comment standards

Expeditor for COBOL programs, if applicable

Faci l i t ies

Determine appropriate location for project team - co-locate

development and program staffIdentify furniture needs and order from warehouse

Purchase or move PCs and set up

Place work orders to move TWC staff as required

Request LAN cabling (cat 5) for PCs and printers

Place telephone ordersOrder or assign copier

Order or assign fax

Order or assign printers

Order basic supplies, whiteboards, etc.System Requi rements

Determine shared directory requirements for project and

request directory creation

Determine global e-mail distribution list requirements andrequest creation if needed

Request appropriate LAN access for all project staff

Request Outlook and other system access for project staff

Establish basic folders within project directory according tostandards

Create development, system test, training and production

coding environments


Page 25/31/2013 3:07 AM


3/61


Project Name

Workplan

Startup

Resp.

PartyStatus

Hours

To

Date

Est.

Hrs to

Comp

Begin

Date

Sched.

Comp.

Date

Actual

Comp.

Date

Pri-

orityComments

Create development, system test, training and production

database environmentsSet up code repository

Request view owner (creator ID) for database - e-mail Joe

Olivarez the basic description of your application and the

department it falls under, DBAs assign by business

area/subject area

Submit the mainframe DASD (disc) requests to Data

Processing (Lara Coffer) for all new projects

Kick -Off Meeting

Determine project start date

Determine participants

Schedule meeting room

Send invitationsCreate agendas

Assign speaking roles

Conduct meeting


Page 35/31/2013 3:07 AM


4/61


Project Name

Workplan

Procurement

Procurement

Resp.

PartyStatus

Hours

To

Date

Est.

Hrs to

Comp

Begin

Date

Sched.

Comp.

Date

Actual

Comp.

Date

Pri-

ority

Budget and Planning

Prepare project worksheet with estimated budget and staff

time

Submit project worksheet to Technology & Facilities Planning

Submit Biennial Operating Plan (BOP) information to DIRDetermine if project is Rider 1 capital and ensure proper

budget allocationRequest unique project/function code to separate project

funds from operating budget

VendorConduct initial meeting with program staffDraft RFO - samples in resource directory

Draft scoring matrixObtain feedback/approval from program, IT, purchasing,

Legal, division directors, Boards, and commission offices asappropriate

Identify evaluation team members

Review vendor list and determine whether to send to somespecifically

Send RFO and F99 to purchasing for posting

Send P19 to purchasing before award madeHave Purchasing screen responses for minimumqualifications

Have Finance screen responses for financial stability (iffinancials requested)

Conduct evaluation kick-off meeting, explain non-disclosurerules and scoring matrix/process

Collect signed non-disclosure agreements then distributequalified responses

Evaluate responses

R:\Inet_Global\Project Management\Project Plans\148859296.xls.ms_office\Procurement

Page 45/31/2013 3:07 AM


5/61


Project Name

Workplan

Procurement

Resp.

PartyStatus

Hours

To

Date

Est.

Hrs to

Comp

Begin

Date

Sched.

Comp.

Date

Actual

Comp.

Date

Pri-

ority

Resolve vendor questions in writing during evaluation - project

manager collect questions from team, purchasing submitquestions to vendors

Apply cost factor to top technical solutions, then select final

cut

Best and Final Offer processes - demos, questions,negotiations

Rescore evaluations in BAFO if final selection is not the

original top scorer

Negotiate contract with finalistIf unable to negotiate contract with finalist, begin negotiations

with #2

Contract Programming or An alyst Staf f

Determine selection team or individualDetermine skill sets and number of staff required for design

analysts and programmers

Prepare F99Ps and F99s for positions

Prepare P19 for projectDevelop screening mechanism, interview questions and rating

matrix

Review resumes from contract staff list

Interview top candidates

Make selections and offersMonitor contracts per the Contract Administration Standards

Manual (CASM)Enter time into UA01

Monitor expenses vs. budget, based on project progress

Asset Management

Report all software development projects over $50,000 to

Asset Management. Report whether TWC will own the sourcecode or pay licensing costs when complete.

Report all software enhancements, which total more than 25%

of the original cost, for software products already covered by

Asset Management.


Page 55/31/2013 3:07 AM


6/61


Project Name

Workplan

Procurement

Comments


Page 65/31/2013 3:07 AM


7/61


8/61


Project Name

Workplan

Project Mgmt

Project Management

Resp.

PartyStatus

Hours

To

Date

Est.

Hrs to

Comp

Begin

Date

Sched.

Comp.

Date

Actual

Comp.

Date

Pri-

orityComments

Prel iminary Planning

Establish and document project objectives

Identify policy decisions required for project and assign early

Identify organizational enablers (from eStrat Plan) requiredand assign/plan

Identify technical enablers required, obtain status andassign/plan

Planning & Schedul ing

Create project management plan (Word PMP)

Identify all tasks in work breakdown structurePrepare milestone schedule - with program, vendor and ITstaff inputPrepare detailed project schedule - with program, vendor and

IT staff input - in Excel or MS ProjectPlan early presentation to TAR Committee on project

background, with later presentation on architectureIdentify and mark critical pathMonitor schedule and budget

Develop action plan for variances

Communicat ion

Develop status report format & templateWeekly team meetingsWeekly team status reports to PM

Weekly cross-team meetings for all eVision PMs

Weekly project status reports to eVision PM and stakeholdersTwo-week eVision status reports to executivesMonthly Steering Committee meetings

Milestone review meetingsConduct frequent checks with team members to ensurecomfortable in roles and responsibilities & identify

training/review needs

R:\Inet_Global\Project Management\Project Plans\148859296.xls.ms_office\Project Mgmt

Page 85/31/2013 3:07 AM


9/61


Project Name

Workplan

Project Mgmt

Resp.

PartyStatus

Hours

To

Date

Est.

Hrs to

Comp

Begin

Date

Sched.

Comp.

Date

Actual

Comp.

Date

Pri-

orityComments

Notify eVision PM of any PM training needs or other needsDeliverable and Paymen t Tracking

Create spreadsheet with deliverables and related pricing

structure

Add dates of deliverable acceptance, invoice approval,

payment

Track progress and variances

Risk Management

Identify risks by reviewing project plan with experts

Identify risks by reviewing list of typical risk categories

Quantify risks by assessing probability, impact and level of

controlPlan management approach to risks - avoid, mitigate or

accept

Move necessary steps into detailed project planTrack risks

Issue Resolut io n

Use formal issue resolution process and format

Establish escalation pathEstablish and maintain issue log

Qual ity A ssurance

Determine review and sign-off teams for each projectdeliverable

Document expectations, including acceptance criteria, foreach deliverable's format and content before work begins

Document acceptance criteria for each deliverable

Ensure all appropriate feedback and review complete before

deliverable acceptanceDocument terms required for full system acceptance; keep

separate from any deliverable

Document the warranty process, adding procedural detail to

the contractual terms


Page 95/31/2013 3:07 AM


10/61


Project Name

Workplan

Project Mgmt

Resp.

PartyStatus

Hours

To

Date

Est.

Hrs to

Comp

Begin

Date

Sched.

Comp.

Date

Actual

Comp.

Date

Pri-

orityComments

Assess for QAT potential and ensure appropriate

documentation ready for DIR


Page 105/31/2013 3:07 AM


11/61


Project Name

Workplan

Communication

Communication

Resp.

PartyStatus

Hours

To

Date

Est.

Hrs to

Comp

Begin

Date

Sched.

Comp.

Date

Actual

Comp.

Date

Pri-

ority

Commun icat ion Plan

Identify the major stakeholder groups, including management,steering committee, vendors, and end users

Determine the communication needs of each stakeholdergroup - a combination of what they want to know and what the

project team wants to tell themDetermine the timing/ frequency of communication for each

stakeholder or key messageReview the Marketing and Communication Enablers in Section

II of the eStrategy Plan

Review the communication vehicles in Appendices D & E ofthe eStrategy PlanDetermine the best medium to communicate to each group

Prioritize the communication ideas so that the least costly with

the most value are included in the final communication plan

Place the details of the communication plan into the projectworkplan - determine who is responsible for carrying out the

communication plan and assign dates for the completion ofeach phase of the plan

Meet with Communications Department regardingcommunication plan, materials review, etc.

In t ranet Commun icat ion

Create project summary page for Intranet project status

sectionCreate project status summary page for Intranet

Assign project feedback e-mail address - [email protected]

Maintain project status summary page for Intranet

Auto mated Mail ings

Write IT1 to write extract program, then program and generate

notices

R:\Inet_Global\Project Management\Project Plans\148859296.xls.ms_office\Communication

Page 115/31/2013 3:07 AM


12/61


Project Name

Workplan

Communication

Resp.

PartyStatus

Hours

To

Date

Est.

Hrs to

Comp

Begin

Date

Sched.

Comp.

Date

Actual

Comp.

Date

Pri-

ority

Determine selection criteria for employers or job seekers to

extract from databaseTest extract program

Draft notice (overview, benefits, procedures, contact

information) and obtain management approval

Notify Output Control of the number of notices, method of

mailing and approximate date to be mailed

If correspondence > 500, go through mailstream - get withAD&MTranslate letter in Spanish if neededCreate form, program form and variable text

Develop program to generate notices

Test programProvide copy of notices to appropriate state office and field

staff

Execute program to generate notices

Print and mail notices


Page 125/31/2013 3:07 AM


13/61


Project Name

Workplan

Communication

Comments


Page 135/31/2013 3:07 AM


14/61


Project Name

Workplan

Communication

Comments


Page 145/31/2013 3:07 AM


15/61


Project Name

Workplan

Program Issues

Program Issues

Resp.

PartyStatus

Hours

To

Date

Est.

Hrs to

Comp

Begin

Date

Sched.

Comp.

Date

Actual

Comp.

Date

Pri-

ority

Issue Identi f icat ionIdentify organizational enablers (from eStrat Plan) requiredand assign/plan

Identify technical enablers required, obtain status andassign/plan

Langu age Issues

Assess current practices for the business function -English

only or multi-lingual?Consult with Legal about Spanish language requirements

Consult with Legal about court-certified interpreterrequirementsFinalize decisions about languages to support in Internet

applicationIf decision is to support more than English, determine timing

and budget of additional languages

Signature Issues

Identify processes to be automated that currently requireoriginal signatures

Research law and policy to determine signature requirementsource

Develop options

Present to Legal Department for rulingPresent to Commission if policy change required

Security Issues

Review global security designs and identify unique businessrequirements for application

Determine if new logons will be automatically authorized orreviewed by staff (Ex: new employer account for Hire Texas

with no tax account)Determine logon methods for transaction specific access (Ex:

employer response to notice of claim requires unique logonwith notice)

Determine password reset procedures and contacts

R:\Inet_Global\Project Management\Project Plans\148859296.xls.ms_office\Program Issues

Page 155/31/2013 3:07 AM


16/61


Project Name

Workplan

Program Issues

Resp.

PartyStatus

Hours

To

Date

Est.

Hrs to

Comp

Begin

Date

Sched.

Comp.

Date

Actual

Comp.

Date

Pri-

ority

Procedural Issues

Identify procedural changes required by automation projectAssess other programs and divisions that might refer

customers to services, and how their procedures/information

might need to change

Develop options and get appropriate approvalDevelop written procedures in appropriate format-WD Letter,

Manual update, etc.

Issue proceduresProvide training if needed - move into training plan

Organizational Issues

Identify possible organizational issues

Assess customer support services to determine if additionalcustomer service staff or organization required

Determine method for Internet customers to contact help and

plan for appropriate e-mail groups, toll-free numbers, ACD

functionality, etc. and to give the Help Desk contacts &numbers to the Unisys Help Desk

Assess job duties and determine if duties, job descriptions,

and performance measures must changeCoordinate changes with program management and HR

Performance Measurem ent

Assess automation features to determine possible impacts on

required program performance measuresEnsure design covers required performance measures or finds

new methods to accomplish the same

Assess opportunities for new performance measures that willhelp identify efficiencies or customer service opportunities -

look for customer-focused or outcome-driven metrics

Customer Input

Assess all possible methods of customer involvement

Web survey

Focus groups


Page 165/31/2013 3:07 AM


17/61


Project Name

Workplan

Program Issues

Resp.

PartyStatus

Hours

To

Date

Est.

Hrs to

Comp

Begin

Date

Sched.

Comp.

Date

Actual

Comp.

Date

Pri-

ority

Usability testing

Survey staff with frequent customer contactSurvey TWC ombudsman

Survey WebmasterSurvey customer service representatives

Ensure site is designed for the customer's point of view, not

the agency's

Materials Review

Assess all forms and correspondence to customers for

potential revisions (including agency or Commissioner

publications)

Initiate appropriate methods to draft and effect changes

Process Redesign

Map current and redesigned business processes before

beginning requirements definition - improves business

processes, ensures early issue identification and streamlines

requirements gathering

Review current business processes to determine opportunities

for greater efficiency

Identify duplication of effort and processes that do not addvalue

Assess customer needs first, then overlay state/local

requirements


Page 175/31/2013 3:07 AM


18/61


Project Name

Workplan

Program Issues

Comments


Page 185/31/2013 3:07 AM


19/61


Project Name

Workplan

Program Issues

Comments


Page 195/31/2013 3:07 AM


20/61


Project Name

Workplan

Program Issues

Comments


Page 205/31/2013 3:07 AM


21/61


Project Name

Workplan

Training

Training

Resp.

PartyStatus

Hours

To

Date

Est.

Hrs to

Comp

Begin

Date

Sched.

Comp.

Date

Actual

Comp.

Date

Pri-

orityComments

Training Plan

Determine participant groups and number of sessions required

Determine locations available for hands-on training

Assign train-the-trainer staffAssign training facilitators

Assign training content developersAssign training content reviewers

Training Developm ent

Develop course objectives and outlines for trainingDevelop format for participant and facilitator guidebooks

Develop participant guidebookDevelop facilitator guidebook

Develop training evaluation forms

Training Preparat ion

Conduct train-the-trainer sessions

Order binders for participant guidebooks

Prepare Y-85s and hand deliver training materials to print

shop/graphics or make copies locallySecure direct billing services for facilitators

Process F-70's for all travel

Deliver training materials direct to training siteDeliver training equipment, including flip charts, projection

screen, trng supplies, etc.Deliver binders direct to training siteSchedule participants

Send participants confirmation of training schedule and

locationTraining

Conduct training

Collect evaluation formsAssess evaluations after each session, modify training if

needed

R:\Inet_Global\Project Management\Project Plans\148859296.xls.ms_office\Training

Page 215/31/2013 3:07 AM


22/61


Project Name

Workplan

Training

Resp.

PartyStatus

Hours

To

Date

Est.

Hrs to

Comp

Begin

Date

Sched.

Comp.

Date

Actual

Comp.

Date

Pri-

orityComments

Summarize training experience, best practices and lessons

learned

R:\Inet_Global\Project Management\Project Plans\148859296.xls.ms_office\Training

Page 225/31/2013 3:07 AM

P j t N


23/61


Project Name

Workplan

Prelim Design

Preliminary Design/ Requirements

Resp.

PartyStatus

Hours

To

Date

Est.

Hrs to

Comp

Begin

Date

Sched.

Comp.

Date

Actual

Comp.

Date

Pri-

ority

User RequirementsAssess customer and business environmentIdentify future business strategy (BPR recommendede)Conduct focus groups, site visits, interviews as appropriateHelp customers to define their needs as clearly as possibleQuery and research all aspects of the need

Document the need of each user category as accurately aspossible, in plain language that the customer will understandDocument business rules

Ask customers to respond to the documentation and revise it

accordinglyDevelop written statement of work or scope statement basedon functionality included

System Requirements

Gather current forms, reports, screensDocument and assess current systemEnsure no current functionality lost in new system, unless nolonger needed with process redesignDetermine major system components/ required systemmodificationsDefine interface requirements & impact on legacy systemsDetermine system architecture and operating environment

Present proposed architecture to TAR Committee for approvalBegin database design (logical and physical)Determine types and estimated number of screens, reports,and forms

Prel iminary Design Docum entat ion

Prepare expectations document and get signatures agreeingupon deliverable contents, standards/templates, and

acceptance criteria

R:\Inet_Global\Project Management\Project Plans\148859296.xls.ms_office\Prelim Design

Page 235/31/2013 3:07 AM

Project Name


24/61


Project Name

Workplan

Prelim Design

Resp.

PartyStatus

Hours

To

Date

Est.

Hrs to

Comp

Begin

Date

Sched.

Comp.

Date

Actual

Comp.

Date

Pri-

ority

Develop distribution list early and verify availability of or order

suppliesDocument functional requirements in a traceability matrix

Develop process and/or screen dialogue flows

Develop detailed screen and report layouts (prototype) to

confirm functional requirements

Develop preliminary data model based on known elements

Map preliminary design back to user requirements (SOW) to

ensure everything covered

Revise based on customer/stakeholder feedback

Obtain user, vendor and IT signatures at acceptance

Life-Cycle Cost Worksheet

Develop 5-year cost forecastItemize all costs, including maintenance, enhancements,

upgrades and software subscriptions/licensing fees


Page 245/31/2013 3:07 AM

Vi i Project Name


25/61


Project Name

Workplan

Prelim Design

Comments


Page 255/31/2013 3:07 AM

Vi i Project Name


26/61


Project Name

Workplan

Prelim Design

Comments


Page 265/31/2013 3:07 AM

eVision Project Name


27/61


j

Workplan

Detailed Design

Detailed Design

Resp.

PartyStatus

Hours

To

Date

Est.

Hrs to

Comp

Begin

Date

Sched.

Comp.

Date

Actual

Comp.

Date

Pri-

ority

Design Documentat ionTrack design by modulePrepare expectations document and get signatures agreeingupon deliverable contents, standards/templates, and

acceptance criteriaEstablish detailed design format and requirements - review

vendor and TWC templates and develop best of breedAdd new elements to the TWC design template based on

vendor design documentAdd new elements to the TWC templates based on vendor

improvements

Include all applicable program types in design: conversion,archive, batch, interface, online, etc.Structure detailed design deliverable to ensure it contains

Table of Contents, introductory section, and flow charts orsome anchor before each section, all detailed design packets,data model, data dictionary, etc.

Develop deliverable distribution list early and verify availabilityof or order supplies

Design Developm ent

Determine applicable use of Web Foundation, Global AccessSecurity System and other global application tools

Conduct separate design session to apply the webdevelopment standards to the application

Develop Global design document (start with standard one) forstandards applying to all screens/pages early in design

processDevelop detailed design packet for style of application pages -

look & feel, navigation

Develop detailed design packet for each program or module

R:\Inet_Global\Project Management\Project Plans\148859296.xls.ms_office\Detailed Design

Page 275/31/2013 3:07 AM



28/61


j

Workplan

Detailed Design

Resp.

PartyStatus

Hours

To

Date

Est.

Hrs to

Comp

Begin

Date

Sched.

Comp.

Date

Actual

Comp.

Date

Pri-

ority

Conduct detailed design review meetings with users

throughout development

Confirm detailed design meets the functional requirements

map back to traceability matrix

Include online help links and wording in the design

Develop separate security specification for overall application

Develop interface specifications

Develop batch process specifications

Arrange for correspondence/page language reviews byCommunicatons or Customer Outreach & Relations

Conduct 'human factors' review for flow, language and button

placementObtain signatures for each packet during reviews, then overall

deliverable acceptanceFinalize data model and complete data dictionary according to

TWC standards

Address the following design issues

Design standards / consistency

Logical and physical databases

Business transactions

Screens/reports/formsApplication software components

Security and access controlsData conversion map

Development, test, and construction environments

Review processChange control

Quality assurance

Retention/archive strategy

Backups

Restart logicError reports

Reprint/regeneration capability


Page 285/31/2013 3:07 AM



29/61


Workplan

Detailed Design

Resp.

PartyStatus

Hours

To

Date

Est.

Hrs to

Comp

Begin

Date

Sched.

Comp.

Date

Actual

Comp.

Date

Pri-

ority

Keywords and meta tags for HTML pages & application home page

Change Procedures

Begin change control process to record and determine

approval of design or requirements changes

Assign change control board

Assign escalation path for unresolved requests

Communicate change process and its importance in

controlling scope

Assess impact of requested change on functionality, budget

and schedule

Track change request and status - accepted, unaccepted,

deferred

Update detailed design documents with addendums forapproved changes


Page 295/31/2013 3:07 AM



30/61


Workplan

Detailed Design

Comments


Page 305/31/2013 3:07 AM



31/61


Workplan

Detailed Design

Comments


Page 315/31/2013 3:07 AM

eVision Project NameW k l


32/61


Workplan

Detailed Design

Comments


Page 325/31/2013 3:07 AM

eVision Project NameW k l


33/61


Workplan

SpecList

Spec List for Detailed DesignProgram

ID

Difficulty Est'd

HoursResp.

PartyStatus

Hours

To

Date

Est.

Hrs to

Comp

Begin

Date

Sched.

Comp.

Date

Actual

Comp.

Date

SignoffPri-

orityComments

Modules

R:\Inet_Global\Project Management\Project Plans\148859296.xls.ms_office\SpecList

Page 335/31/2013 3:07 AM

eVision Project NameWorkplan


34/61

for Texas Workforce NetworkWorkplan

Build

Build and Unit Test

Resp.

PartyStatus

Hours

To

Date

Est.

Hrs to

Comp

Begin

Date

Sched.

Comp.

Date

Actual

Comp.

Date

Pri-

ority

PreparationReview appropriate environments, code migration and versioncontrol processes

Prepare expectations document and get signatures agreeing

upon deliverable contents - may just be one copy of final codereview, unit test and any amended detailed designsPrepare expectations document and get signatures agreeing

upon deliverable contents, standards/templates, andacceptance criteriaDevelop distribution list early and verify availability of or order

suppliesCode

Build skeleton program/ proof of concept as template

Code according to design specs and technical standardsRaise issues to project management, user and technicalgroups as needed - use formal issue resolution process if

unable to resolve through discussionDocument design amendments throughout process and getsignatures

Include archive programsInclude conversion programs (detail on next sheet)

Include backup filesWrite production JCL, if applicable

Code Review

Use code review checklist - include SQL review by DBAs for

efficiencyGet user and technical review and sign off of checklist formatand process

Determine responsibility for code review - include TWCtechnical staff and vendor staffConduct code reviews

Obtain signatures for each packet during reviews

R:\Inet_Global\Project Management\Project Plans\148859296.xls.ms_office\Build

Page 345/31/2013 3:07 AM



35/61


Build

Resp.

PartyStatus

Hours

To

Date

Est.

Hrs to

Comp

Begin

Date

Sched.

Comp.

Date

Actual

Comp.

Date

Pri-

ority

Unit Test

Create unit test checklists

Get user and technical review and sign off of checklist formatand process

Determine responsibility for unit test review and process -

include TWC user and technical staff and vendor staff

Conduct unit test in both IE and Netscape and document

results

String test related components

Review unit test results in meetings

Obtain signatures for each packet during reviews


Page 355/31/2013 3:07 AM



36/61


Build

Comments


Page 365/31/2013 3:07 AM



37/61

for Texas Workforce Networkp

Build

Comments


Page 375/31/2013 3:07 AM

eVisionf T W kf N t k

Project Name

Workplan


38/61

for Texas Workforce Network Conversion

Conversion

Resp.

PartyStatus

Hours

To

Date

Est.

Hrs to

Comp

Begin

Date

Sched.

Comp.

Date

Actual

Comp.

Date

Pri-

ority

Definit ion and Planning

Document conversion activities in the deliverables for theappropriate stage, such as detailed design and system test

Identify and document all data sources and elements to be

converted, including historical or archived dataIdentify any data cleaning issues

Document number of records involved in the conversionAnalyze the existing data to understand any implicit or explicit

relationships and dependencies, and how those attributescorrespond to the new system

Map each data element to the corresponding new element

Determine how to address new data elements that don't havecorresponding old data elements - calculate based on existing

information, perform manual conversion process, leave blankDetermine if alert mechanism is required to notify users of

partially converted records requiring research and additional

dataDevelop conversion plan and identify all methods required for

automated and manual conversionDetermine if additional test environment is required for

conversion testing and create if neededDetermine all responsible parties for conversion programming,

testing, data verificationPrepare detailed schedule for conversion tasks to address

task dependencies

Convers ion Coding

Code all conversion scriptsWrite procedures for manual conversions and develop

templates if needed

Conversion Testing

Run all conversion scripts

R:\Inet_Global\Project Management\Project Plans\148859296.xls.ms_office\Conversion

Page 385/31/2013 3:07 AM

eVisionf T W kf N t k

Project Name

Workplan


39/61


Resp.

PartyStatus

Hours

To

Date

Est.

Hrs to

Comp

Begin

Date

Sched.

Comp.

Date

Actual

Comp.

Date

Pri-

ority

Perform at least partial manual conversionsConduct data review with users and technical team

Document all discrepencies, review code, determine action,fix, and retest

Other Test Coordinat ion

Run mock conversions before other test phases to fullyexercise converted data


Page 395/31/2013 3:07 AM

eVisionfor Te as Workforce Net ork

Project Name

Workplan


40/61


Comments


Page 405/31/2013 3:07 AM


Project Name

Workplan

C i


41/61


Comments


Page 415/31/2013 3:07 AM


Project Name

Workplan

Testing


42/61

for Texas Workforce Network Testing

Testing

Resp.

PartyStatus

Hours

To

Date

Est.

Hrs to

Comp

Begin

Date

Sched.

Comp.

Date

Actual

Comp.

Date

Pri-

ority

Definit ion and Planning

Determine types of testing included in project scope

Determine relative timing of each testing phasePrepare expectations document and get signatures agreeing

upon deliverable contents, standards/templates, and

acceptance criteria for each separate testing phase

Defect Tracking

Implement defect tracking processesDocument and log all problem reports

Determine if problem is application error, data error, or

enhancement

Determine severity/priority for all errors and enhancementsAssign errors for data or code fixAssess enhancements for possible implementation/change

order

Usabil i ty Test

Determine scope of test - level of functionality and web pages

to be included in prototypeDevelop the test scenarios and tasks to be tested

Prep data if needed

Assign facilitator, observers and technical support staffDetermine customer groups and number of sessions

Send invitations to participantsPrepare test area

Execute tests and collect observations

Debrief participants and observersAnalyze findings

Fix errorsLog enhancements and prioritize for immediate or future

development

System Test Plan

R:\Inet_Global\Project Management\Project Plans\148859296.xls.ms_office\Testing

Page 425/31/2013 3:07 AM


Project Name

Workplan

Testing


43/61

Testing

Resp.

PartyStatus

Hours

To

Date

Est.

Hrs to

Comp

Begin

Date

Sched.

Comp.

Date

Actual

Comp.

Date

Pri-

ority

Develop written test plan with resources, roles &

responsibilities, defect tracking procedures, data prep

requirements, converted data requirements, and testingmethodologies

Define the testing tools needed for each testing level

Identify dependencies or risks that may impact the schedule

Develop test cycles, subcycles and get sign off

Develop test conditions, test scripts and expected results andget sign off

Create a results column for each browser tested - IE and

Netscape both required

Ensure test conditions will test results with both converted andnew data

Develop detailed system test schedule

System Test Preparat ion

Book room and equipment needed for system test - ensuredifferent browsers and operating systems available

Schedule all required participants

Convert dataComplete data prep for specific test conditions and tests

against new data

System Test Execution

Execute test scripts in both IE and NetscapeDocument errors and enhancement comments

Fix errors

Retest and close errors

Plan and conduct regression testSign off system test

Acceptan ce Test

Determine objectives of acceptance testConsider training pilot for the acceptance test participants -

will help prepare the test participants and will test the training

approach and materials


Page 435/31/2013 3:07 AM


Project Name

Workplan

Testing


44/61

Testing

Resp.

PartyStatus

Hours

To

Date

Est.

Hrs to

Comp

Begin

Date

Sched.

Comp.

Date

Actual

Comp.

Date

Pri-

ority

Develop test scripts or select subset of system test scripts

Identify and schedule test facilitator, participants and technicalsupport

Convert data

Complete data prep for specific test conditions and tests

against new data

Execute test scriptsDocument errors and enhancement comments

Fix errors

Retest and close errors

Sign off acceptance test

Performance/Stress Test

Set requirements for average and maximum response times

Determine number of simultaneous users required to stress

systemDetermine different connection types and speeds required for

test

Determine method of testing - software or human driven or

combinationWrite test scr ipts and develop test logs

Conduct tests

Analyze results, including hardware assessment, anddetermine corrective action plan if needed

Pilot Test

Determine pilot objectives

Identify diverse group of pilot participants with characteristics

to achieve objectives

Determine pilot environment - parallel system or production

Determine how to limit access to the pilot site

Develop written pilot plan and get sign off


Page 445/31/2013 3:07 AM


Project Name

Workplan

Testing


45/61

g

Resp.

PartyStatus

Hours

To

Date

Est.

Hrs to

Comp

Begin

Date

Sched.

Comp.

Date

Actual

Comp.

Date

Pri-

ority

Develop and distribute appropriate correspondence tocustomers or user group

Convert data appropriate for pilot depending on environmentConduct pilot and debrief participants

Analyze results and determine corrective action plan if neededAssess implementation readiness based on pilot resultsSign off pilot test


Page 455/31/2013 3:07 AM


Project Name

Workplan

Testing


46/61

g

Comments


Page 465/31/2013 3:07 AM


Project Name

Workplan

Testing


47/61

g

Comments


Page 475/31/2013 3:07 AM


Project Name

Workplan

Testing


48/61

Comments


Page 485/31/2013 3:07 AM


Project Name

Workplan

Testing


49/61

Comments


Page 495/31/2013 3:07 AM


Project Name

Workplan

Implementation


50/61

Implementation

Resp.

PartyStatus

Hours

To

Date

Est.

Hrs to

Comp

Begin

Date

Sched.

Comp.

Date

Actual

Comp.

Date

Pri-

ority

Implementat ion Criteria

Set formal implementation criteria well before implementation

Ensure all implementation criteria have been met

Hold go/no go meeting with primary stakeholder

representativesImplementat ion Plan

Prepare expectations document and get signatures agreeingupon deliverable contents, standards/templates, and

acceptance criteria

Develop formal, detailed implementation plan with all tasks

and due dates required for successful implementationincluding technical, program, and communication stepsIdentify risks and develop contingency plansCarry out planned method for Internet customers to contacthelp, implement appropriate e-mail groups, toll-free numbers,

ACD functionality, etc., and give the Help Desk contacts &numbers to the Unisys Help Desk

Determine if temporary web pages are required duringimplementation process to notify customers

Coordinate implementation plan and conversion plan tasksEmail new FTP info to Output Control (Laura Hernandez) to

update the Outgoing/Incoming Cartridges, Tapes and FTPsspreadsheetIdentify all roles and responsibilities

Conduct implementation meeting with all necessary parties

and review schedule and tasksCreate and distribute contact lists with contact roles andmultiple contact methods

Schedule technical support staffSchedule customer support staff

Arrange for building and room access for non-traditionalbusiness hours

R:\Inet_Global\Project Management\Project Plans\148859296.xls.ms_office\Implementation

Page 505/31/2013 3:07 AM


Project Name

Workplan

Implementation


51/61

Resp.

PartyStatus

Hours

To

Date

Est.

Hrs to

Comp

Begin

Date

Sched.

Comp.

Date

Actual

Comp.

Date

Pri-

ority

Web Site Integrat ion

Have program staff review existing web pages to determine

necessary content changes to reflect newfunctionality/processes

Review web site to determine all changes required to existing

linksDetermine placement and labels of new links to site

Set length of shakedown period before highlighting new

application as featured link

Determine applicable customer group home pages forfeatured links and draft language

Schedule timing for each change

Implement changes

Test search results, check ranking for application home page

and other key pages, and change keywords if needed

System Acceptance

Set formal system acceptance criteria well before

implementationEnsure all acceptance criteria have been met

Authorize final payment


Page 515/31/2013 3:07 AM


Project Name

Workplan

Implementation


52/61

Comments


Page 525/31/2013 3:07 AM


53/61


Project Name

Workplan

Transition

T iti


54/61

Transition

Resp.

PartyStatus

Hours

To

Date

Est.

Hrs to

Comp

Begin

Date

Sched.

Comp.

Date

Actual

Comp.

Date

Pri-

ority

System Docum entation

Develop technical support information - include informationabout the hardware and software configuration, the databasestrucure and maintenance processes

Develop application source code documentation

Develop system configuration documentationPrint and distribute the documentation and place on shared

LAN directory

Knowledge Transfer

Identify all system maintenance staff well in advance andinvolve them whenever possible

Schedule maintenance staff from all areas, not just applicationmaintenance, to attend knowledge transfer sessions

Application Functionality Overview

Application Architecture Overview

Deliverable OverviewData Model Overview

Server OverviewDirectory Structure Overview

Automated Server Password Maintenance OverviewProblem Report Overview

Enhancement List OverviewCurrent Roles and Responsibilities

System Acceptance and Warranty Work ChecklistWarranty Period

Put warranty process and procedures in writing

Clarify that document is process only and does negate ormodify contract warranty information, and include summary of

warranty terms

Identify processes used to determine if item covered underwarranty, to report the error to the vendor, to escalate issues

R:\Inet_Global\Project Management\Project Plans\148859296.xls.ms_office\Transition

Page 545/31/2013 3:07 AM


Project Name

Workplan

Transition

Hours Est Sched Actual


55/61

Resp.

PartyStatus

Hours

To

Date

Est.

Hrs to

Comp

Begin

Date

Sched.

Comp.

Date

Actual

Comp.

Date

Pri-

ority

Confirm location and security access for warranty work andagree upon migration coordination

Determine length of time TWC has to test the fix before it isaccepted by default

Clarify warranty ending date - no new problems reported after

end date but ongoing break/fix work to continue until resolved

Obtain signatures from vendor and agency representativesConduct meeting or conference call with vendor, user,

technical and testing staff to ensure everyone understands

roles, responsibilities and procedures

Execute warranty processesMaintenance

Establish the current IT1 problem report and enhancementrequest processes for regular maintenance

Notify users of any changes in procedure from the system

development and warranty work processes

Encourage users and technical staff to work together closely

during transition for system background, error recreation, etc.


Page 555/31/2013 3:07 AM


Project Name

Workplan

Transition


56/61

Comments


Page 565/31/2013 3:07 AM


Project Name

Workplan

Transition


57/61

Comments


Page 575/31/2013 3:07 AM


Project Name

Workplan

Closeout

Closeout


58/61

Closeout

Resp.

PartyStatus

Hours

To

Date

Est.

Hrs to

Comp

Begin

Date

Sched.

Comp.

Date

Actual

Comp.

Date

Pri-

ority

Evaluation

Conduct assessment of how well application meets customerneedsConduct lessons learned/ best practices brainstorming

exercise

Document lessons learned and best practices

Assess project products as possible resources for otherprojects - add to Resources folder in Inet_Global if appropriate

Update current project processes based on evaluation

Complete PIER review for DIR if required

Contract Closeout

Monitor final acceptance criteria and warranty work

Track final payments to vendorsPerform project end QA activities

Asset Management

Follow up with Asset Management for projects over $50,000.

Inform them software development complete and whether

TWC owns the source code or pays licensing costs. Providethe property number of the server that the application resides

on.Follow up with Asset Management for enhancements over

25% of the original cost, if software product already coveredby Asset Management.

Project Records Cleanup

Update project management plan with final information

Verify all deliverables on LAN

Verify hardcopy of all deliverables for project recordsSeparate final deliverables from working files

Password protect final deliverables for modificationDelete files no longer needed

Provide electronic files to other areas as neededBurn CDs of project directory

R:\Inet_Global\Project Management\Project Plans\148859296.xls.ms_office\Closeout

Page 585/31/2013 3:07 AM


Project Name

Workplan

Closeout

RespHours Est.

BeginSched. Actual

Pri-


59/61

Resp.

PartyStatus To

Date

Hrs to

Comp

Begin

DateComp.

Date

Comp.

Date

Pri-

ority

Review paper files from project and discard or storeReassignment of Personnel

Transfer TWC programmer/analysts to maintenance or newproject roleReassign Project ManagerClarify user's ongoing roles as they transition back to programarea

Reassignm ent of Material Resour ces

Inventory remaining supplies and equipmentAssess needs of future or existing projects, ongoingmaintenance, etc.Transfer resources


Page 595/31/2013 3:07 AM


Project Name

Workplan

Closeout


60/61

Comments


Page 605/31/2013 3:07 AM


Project Name

Workplan

Closeout


61/61

Comments


Page 615/31/2013 3:07 AM

project plan for web startup1

Documents