GETTING SYSTEM FOR

THE NEXT FISCAL YEAR.

JEFFERY FELIX BROWN AUGUST 13, 2013

American Intercontinental University

Inspire Others

Work Smart

Exceptional Results

THE CORE VALUES

This Introduction main Goal is to get the Company with 30,000 Employees to get their system Up so that it will be Running for the Next Fiscal Year.

PROJECT MANAGER HIGH RISKS

Missing Requirements: These requirements is needed by the System to be

developed to meet the Company Goals and Objectives of the project.

Key and Critical Resources: Are lost to the project with a potential impact of

losing resources for any given period of Time will go beyond the will become

critical.

Missing or Incomplete Skills Sets: This results in Risks events will remain

the same as the results in a bad estimate.

CUSTOMERS HIGH RISKS

Requirements are only partly known at the beginning of the project. The Customers

may not allocate the sufficient resources when exploring these requirements. These

customers may not accept the delivery of the system, when it really doesn’t meet

the goals. As Project Team should always update these regularly and reviewed by

customers from Time to Time.

ARCHITECT HIGH RISKS

There are Two Levels of Risks that is considered:

1. Initial Level of Risk – This risk is categorized for prior in determine and

inadquated the Mitigating actions.

2. Residual Level of Risk – In this type of risk is also categorized after

implemented of mitigating actions “if any”.

THE OUTLINE PART ONE:

Plan:

• Identify Participants.

• Establish Guidelines and Procedures.

• Assign all Roles.

• Establish entry Criteria and then exit the Criteria base on the event-

driven Schedule.

Familiarize:

• Always have an overview of the Company vision within your

meetings.

THE OUTLINE PART TWO

Pre – Review:

• Location 1 Examine Data

• Location 2 Analyze Data.

• Location 3 Tracking

every document for

analysis.

Click on the globe to start

“Always Give You As Project Manager and Team enough

Time to Review your Project Plan!” ~Jeffery F. Brown, Author, Atlanta, Georgia

THE OUTLINE OF THREEReview:Examine all data and analysis, make sure to Record to classify findings.

An Address key issues to identify any pre-review activity.

Give asses of Security of Problems within the review.

Then recognized all of the action Items.

Resolve:Give Each the Assign Responsibility

OUTLINE PART FOUR

Follow Ups:

• Track Action Items and Issues

• Track Action Items for Completion Trends

• In every Document and Distribution of all

results. This will help in the Planning,

Familiarize, Pre-review, Review, and

Resolve.

Plan

ReviewFamiliarize

SUMMARY OF WEEK 4 INDIVIDUAL PROJECT

Within this Scenario the IT Project Plan, the Company gave a task to come up with a System

that meets the Four Companies in other States Vision. The Issues that will arise for this Project

Team, is base on collecting all necessary Data to be able to gather enough information to

begin. If you look at the First Constraint “Time” is will be off if these Companies doesn’t deliver

the requirements. Next in the Constraint you have the “Cost” where the risk can easily go

higher than what the Budget was set by Company Financial Board. And not least but last on the

Constraint is your “Scope” that if these other Four Companies start sending information that

going to be used within the Project Plan; if you try to alter the plan you can cause the 3

Constraint “known as the Triangle”; this would make this IT Project Plan to go in another

Direction. What I call going “Offline” Meaning taking the Project Plan from what the Company

vision set to accomplish.

REFERENCE:

• Nielson, D. (2008, November 06). Identifying risks to software projects. Retrieved from http://ezinearticles.com/?Identifying-Risks-to-Software-Projects&id=2671133

• Robbins, J. (2004). Risk management during requirements. Retrieved from http://readyset.tigris.org/nonav/templates/risks.html

• TOGAF information web site. (2011). 7 phase a: Architecture vision. Retrieved from http://pubs.opengroup.org/architecture/togaf9-doc/arch/chap07.html

• Cantoria, C. S., & Gundlach, M. (2011, February 28). Risk mitigation strategies and risk mitigation plan. Retrieved from http://www.brighthubpm.com/risk-management/47934-risk-mitigation-strategies-and-risk-mitigation-plan/

WE ARE DEDICATED TO MAINTAINING A SYSTEM, FOR YOUR FOUR COMPANIES IN A SAFE ENVIRONMENT…

Thanks For Having Me As Your IT Project ManagerThroughout This Important Entrusted Leadership!!!