Professional Documents
Culture Documents
Mit 3414 Assignment Ii
Mit 3414 Assignment Ii
(JKUAT)
ASSIGNMENT II
a) First determine an objective for a project and then such for financiers and
b) First determine a donor and then the objective for a project. In what cases
procedure 1 (procedure 2) will work better?
PROJECT CHARTER
Description:
This project will implement policies, procedures, service modifications and
documentation in support of accessibility capabilities and compliance for ICT
equipment, systems and services on the JKUAT campus. This project will specifically
implement those actions described in a resolution proposal document in response to
addressing barriers to University services, programs and activities by students with
disabilities, including students with vision impairments. The primary ICT services to be
remediated include Google Apps, Digital Textbooks, Digital Signs, Portals, websites for
homework and course-related content, and online placement and diagnostic exams. In
the process of addressing these areas, other opportunities and actions may be pursued
that support these objectives and benefit the campus. As they are identified, they will
be reviewed for approval and incorporation into the project scope
Clients/Customers
JKUAT campus associates using supported ICT services and applications in
a context that requires accommodation or accessibility services, features
or capabilities. This includes students with disabilities and
faculty/instructors teaching courses that may have students with
disabilities enrolled.
Customer Benefits/Outcomes
Enhanced ability of students with disabilities to utilize supported ICT
services and applications in JKUAT in fulfillment of academic pursuits.
Improved knowledge and understanding by faculty on appropriate uses of
technology for teaching and available accommodations for disabled
students.
Enhanced usability of supported ICT applications and services for all
campus associates.
Increased and enhanced usage of supported ICT applications and services
by all campus associates, including those with disabilities.
The 100% Rule: The Work Breakdown Structure (WBS) should define the total scope of the
project. If it doesn’t do this then the plans you create from the WBS will by inference have gaps
and missing components.
Mutual Exclusivity: there should be no overlap between any two elements in a The Work
Breakdown Structure (WBS). If there are, then you run the risk of duplicating work in the project
execution
Include Deliverables, Not Actions: do not provide more details than necessary, this is one of the
best ways to stick to the 100% rule
Use Common Sense: as mentioned previously, don’t go into too much detail. What you’re
looking for is enough detail so you can plan, manage and control the project.
4. In composing the time-table there are the following two general methodologies:
2. The time-table can consist activities as. Arguments for the case 1): a)
concrete methodologies, procedures etc are assumed in determining activities; this
suppresses creativity and innovation; b) Composition of time-table and
determination of dependencies are different processes and therefore these
processes should not be mixed up. Arguments for the case 2): a) Relations between
activities and dependencies describe the fact that the outcome of the predeceasing
activity is needed for the subsequent activity; b) The outcomes of activities can be
arranged according the hierarchy of activities. It is generally accepted that the
project manager has to decide about the content and type of the time-table.
Although PMBOK Guide defines time-table as "deliverables-oriented hierarchy”,
this should not be interpreted as "hierarchy of deliverables”; often lower-level
elements are described by activities and identified by a concrete person/group,
upper level elements by outcomes. What is your position in this?
SOLUTION
One major factor that has been identified as reasons for cost overrun in most
projects is design errors. It is important to note that proper representation of
client’s requirement and the blue print to achieving good technical input to
project execution are usually mapped out base on project designs. Thus a
design with errors practically means wrong or insufficient representation of
project deliverables.
Delay and cost overrun in project could be as a result of scope change. Scope
is the term that defines the entire deliverables that is expected at the end of a
project. Therefore, logically, it can be said that all project plans, estimation,
schedule, quality and base lines are usually designed base in the initial project
scope. Thus, any change in the project scope during execution will mean that
the entire initial project plan will have to be reviewed such that a reviewed
budget, schedule and quality will have to be developed. This means more time
and resources will be needed as against the initial baseline.
Another major reason for cost overrun and delay in project is inappropriate
and inadequate procurement and faulty contractual management system.
Contracts read out virtually every aspect of a business correlation, including
payment terms, pricing, and service levels. Therefore a contract that has not
highlighted the entire project scenario may lead to dispute in the contract
system.
REFERENCE
1. http://www.edutopia.org/stw-maine-project-based-learning-six-steps-planning
2. https://en.wikipedia.org/wiki/Work_breakdown_structure
3. http://www.academia.edu/14469072/Two_solutions_to_the_general_timetable_proble
m_using_evolutionary_methods
4. Lecture notes
5. https://www.linkedin.com/pulse/five-causes-project-delay-cost-overrun-mitigation-
measures-buys