Best IT Documents.com Blog


What your Project Manager should be doing for you

Posted in Projects (400) by Guest on the December 27th, 2007

Responsible for overall coordination, status reporting and stability of complex and cross-functional project oriented work efforts. 

Manages multiple projects simultaneously, establish and implement project management processes and methodologies for the IT community to ensure project more years managing projects and requires prior management, supervisory, or team leader experience. 

Plans and tracks resources, shapes priorities, coordinates interactions with the project customers and users 

  • Builds & manages the project schedule, reports project status, manages project scope and specifications, raises overall critical trade-off decisions to keep the project team focused on the right goal.
    • Projects are all about Deliverables, Cost, Management of Resources and Communications.
  • Defines and manages project dependencies, interacts with the program management team and other project teams for external team dependencies
    • A Project office provides guidance and help to manage expectations with financial and stakeholders.
      • Setup Budget and charge codes
      • Manage Financials
      • Report overall Status
      • Coordinate projects and dependencies
      • Manages escalations
      • Established some levels of priorities
  • Follows a set of practices to ensure the integrity and quality of project deliverables and follows the standard development methodology.
    • Most organizations have a Technology such as Clarity, Enterprise Microsoft Project or RPM, for managing process project schedules.
      • Start with a corporate standard project wbs
      • Build work-streams based on major and key milestones and deliverables.
  • Responsible for plans to transition the project deliverables to the user community, as appropriate, to be defined project by project
    • Daily project tracking rolled into a weekly or bi-weekly project reports
    •  Scheduled meetings with resources (tower leads, SME’s and subk project members)
  • Responsible for budget, schedule and quality for assigned work
    • Negotiates priorities
    • Communicates status
    • Tracking wbs tasks, subtasks, milestones
    • Schedules meetings, assign tasks and tracks progress
    • Performs escalations when needed
  • Facilitates resource assignments and ensures resource optimization
    • Adjusts resources for maximum results
  • In conjunction with Program Manager, facilitates kick-off meetings with Business Program Manager or delegate
    • Review related contracts, SOWs / OLAs
    • Review Scope, Requirements, Dependencies, Risk
  • Develops integrated schedule for all impacted parties; manages Clarity plan and metrics
    • Start with a corporate standard project wbs
    • Build work-streams based on major and key milestones and deliverables.
  • Tracks and manages project risks and issues, removes roadblocks; develops risk management plan for project
    • Document dependencies in wbs
    • Document track risk owners
    • Report status to PO and stakeholders
  • Escalation point for issues
    • Understand issue
    • Document issues
    • Suggest remediation options
    • Document risk of no-action / impact
  • Manages contingency plans
    • Understand issue
    • Document issues
    • Suggest remediation options
    • Document risk of no-action / impact 
  • Manages Change Control requests
    • Understand Change Control requirements
    • Document  change needed
    • Document backout plan
    • Document successful and failed change (RCA)
  • Assists in implementing corrective action
    • Debug conference calls
    • Document attendance
    • Document roles
    • Document assigned tasks
    • Track / report progress
    • Update appropriate departments based on events
  • Reviews and validates status reports
    • Accurately track and report status to PO and Stakeholders
  • Prepares status reports
    • User corporate tracking report venues
    • Accurately track and report status to PO and Stakeholders
  • Implementation planning and execution
    • Execute
  • Approves Go / No-go decisions
    • Test / validation
    • KT
    • Turn-over checklist
    • Acceptance / signoff
  • Coordinates with each Process Owner regarding issues and standards related to that Functional area as well as with the Program Manager
    • Execute
  • Facilitates lessons learned meetings
    • Closeout / exit criteria
  • Provides performance review input for Application Managers, Downstream System Managers and Project Team Members
      • Best to use gap analysis
      • KT
      • Turn over checklists

http://www.bestitdocuments.com/Services.html

 

Comments Off on What your Project Manager should be doing for you

Information Technology Requirements

Posted in Compliances (1300),Security (1500) by Guest on the December 21st, 2007

The objectives of this activity are to:

o Identify and document functional requirements related to potential systems,

o Identify and document data requirements related to potential systems,

o Identify and document technical requirements related to potential systems,

o Identify and document integration requirements related to potential systems,

o Identify and document communications requirements related to potential systems,

o Prioritize the new requirements, identifying strategic opportunities.  

Tips and Hints

Some requirements will have been identified as part of the current information technology assessment. These requirements must be understood and documented.

o Emphasize what the organization needs, not what currently exists. Keep the analysis at a high level, focusing on the processes that must be supported to meet the business objectives. Do not try to re-engineer the business process itself within the scope of the study. Identify where the processes are more likely to be reshaped and streamlined, and the requirements that could flow from the reshaping. 

Activity – Identify Technology Requirements

Identify the requirements that will affect the selection of the technology components for the solution.

Review the corporate technical direction. Assess the current technology in use. Consider the likely future direction (e.g., industry direction, technology trends). Consider specific requirements such as disaster recovery and network and systems management. 

Activity – Confirm Coverage of Requirements

To assemble the traceability matrix sections for both the application and the technical architecture and confirm that the stated requirements are met. 

Activity – Model Technical Requirements

This activity defines the technical requirements of the data warehousing project. Specific objectives are to:

o Define user access needs,

o Define storage requirements,

o Define system availability and performance requirements,

o Define data management and load strategies,

o Define data and process placement strategies,

o Define new requirements and/or upgrades to the technical platform and SME,

o Define access control and security requirements,

o Present the technical requirements to the Acceptor and obtain approval to continue. 

An evaluation of current data infrastructure including the following:

o Data Infrastructure Overview 

Prepare a brief description of the key entities (e.g., the current databases) for the organization. Provide the following:

o Name of the data component,

o Type of data (e.g., input, output, file, database),

o Where data is used (e.g., source/destination of data),

o Medium used to store or transmit the data,

o Location of the data,

o A brief description of the data.

o Strengths, Weaknesses, and Opportunities

Present observations addressing problems, strengths, requested improvements, and opportunities to be explored. Indicate the urgency of any changes. 

If there are any recommendations that can be made at this point in time on the future of the data, present the recommendation. For example, if the data is of high quality, extremely valuable to the organization and recently implemented at a significant cost to the organization, it may be prudent to document this here and recommend that the data component be included “as-is” in the future data architecture.  

Size and Format

Prepare the following:

o A one to two page overview of the current data infrastructure,

o A one page conceptual model, identifying which applications access the data and where the data is located,

o A one to two page summary table, organized around a functional view of the data, detailing strengths, weaknesses, and new requirements,

o A one page list of recommendations.  

Tips and Hints

Document only the highlights that are key to understanding the scope of the new system. Data models and process models are typically not necessary to document the observations. A single page conceptual model showing data location is recommended.

http://bestitdocuments.com/Services.html

 

Comments Off on Information Technology Requirements

Sample – Mindmap Core Directory Service Agent

Posted in Mindmap (100) by Guest on the December 18th, 2007
Comments Off on Sample – Mindmap Core Directory Service Agent

Sample Information Security Project Plan

Posted in Projects (400),Security (1500) by Guest on the December 3rd, 2007

Sample Information Security Project Plan Planning & Organization

Define a Strategic IT Plan

Define the Information Architecture

Determine the Technological Direction

Define the IT Organization and Relationships

Manage the IT Investment

Communicate Management Aims and Direction

Manage Human Resources

Ensure Compliance with External Requirements

Assess Risks

Manage Projects

Manage Quality

 

Acquisition & Implementation

Identify Solutions

Acquire and Maintain Technology Architecture

Acquire and Maintain Application Software

Develop and Maintain IT Procedures

Install and Accredited Systems

Manage and track changes

Delivery & Support

Define Service Levels

Manage Third-Party Services

Manage Performance and Capacity

Ensure Continuous Service

Ensure Systems Security

Identify and Attribute Costs

Educate and Train Users

Assist and Advise IT Customers

Manage the Configuration

Manage Problems and Incidents

Manage Data

Manage Facilities

Manage Operations

 

Monitoring

Monitor the Processes

Assess Internal Control Adequacy

Obtain Independent Assurance

Provide for Independent Audit

Comments Off on Sample Information Security Project Plan