Assignments-Mba Sem-Ii: Subject Code: MB0033
Assignments-Mba Sem-Ii: Subject Code: MB0033
Assignments-Mba Sem-Ii: Subject Code: MB0033
ASSIGNMENTS- MBA
SEM-II
Subject code: MB0033
Subject Name: PROJECT MANAGEMENT
Set 1& Set 2
Submitted By:
Mr. Mithesh Kumar
Reg. No. 520930668
948-000-9987
Kumar.mithesh@gmail.com
Q.1:- Define project management, resource, process and project cycle. Explain
the life-cycle of a project.
Resource : We discussed earlier that the most important step to arrive at the
relationship between the four constraints is to make an accurate assessment of the
resources required, and the costs thereof. At this stage, we shall broadly classify the
resources required under four categories.
Manpower refers to all the man hours required from various personnel
working directly or indirectly on the project.
Materials refer to all materials that become part of the project. In the
case of a building this will include cement, steel, aggregates, doors &
isolation from another process group, and the processes have inherent interactions
between themselves throughout the implementation of a project. We will briefly
define these process groups as under, while a more detailed explanation of each
process group follows subsequently.
Broadly, the process groups tend to be deployed in the sequence listed as the
project progresses. In the event that a project goes off-course, re-planning comes into
play, and if a project is found to be in serious trouble, it may have to go all the way
back to the initiating process to be restarted.
Process Groups in a Phase Also, though these process groups are presented
above as discrete, one-time events; these events overlap and take place at different
levels of activity across each phase in the project life cycle.
Project Life cycle: Collectively, the project phases are known as the project
life cycle. Thus the project life cycle serves to define the beginning and end of the
project. For example, when an organization identifies an opportunity, it will conduct
or authorize a feasibility study to decide if it should undertake the project. The project
life cycle definition will determine whether the feasibility report is treated as the first
project phase, or as a separate standalone project. The phase sequence defined by
most project life cycles generally involves transfer of deliverables (or technology)
such as:
Requirements to design
Design to production or construction
Production to distribution
Construction to operation
Deliverables from preceding phase are usually approved before work starts on
the next phase. The requirement of speedy completion of the total project will often
necessitate overlapping of phases i.e. a subsequent phase is begun prior to approval of
the previous phase deliverables, when the risks involved are deemed acceptable. This
overlapping is termed fast tracking.
Life cycle of a project manager overlaps with the development life cycle in the
middle.
The project manager conducts the analysis of the problem and submits a
detailed report to the top management. The report should consist of what the
problem is, ways of solving the problem, the objectives to be achieved, and the
success rate of achieving the goal.
The project manager and the project team to complete projects on schedule
within budgeted cost and in full accordance with project specifications. At the same
time, they help achieve the other goals of the organization, such as productivity,
quality and cost effectiveness. Hence the objective of project management is to
optimize project cost, time and performance (includes quality).
Today large and small organizations recognize that project management, with
its structured approach to planning and controlling of projects, is a necessary core
competency for success. Like general management, project management also involves
all aspects of planning, organizing, implementing and controlling .However, it has its
own techniques like work breakdown structure, critical path analysis, PERT (Program
evaluation & review technique), which will be discussed in later units.
Issues are made clear by the project manager to avoid as many surprises as
possible. Bottom-up project management can also be viewed as a way of coping with
the increasing gap between the information necessary to manage knowledge workers
and the ability of managers to acquire and apply this information.
Team members very often have read-only access to the project plan and
cannot make any contributions or changes. The employees send their updates to the
project manager in disconnected files via e-mail. The project manager then has to
collect all the data and put the information manually into the project plan. After that,
he or she has to communicate the changes to the corporate executives. All these
routine procedures lead to a situation where the project manager's talents often are
buried by the routine work. The huge amount of mechanical control/synchronization
work often leaves little very time for leadership from the project manager.
The project manager is the one to conduct the work of his team and choose the
right direction for the project development, based on the information received from
the individual employees. Thus, the role the project manager plays in the project
changes.
Project managers should be familiar with, and be able to use or direct the
project team, to use the appropriate tools to ensure that estimates provided during the
planning process are reliable. Estimation tools are driven by historical data and many
can serve as a parametric model which can be scalable based on the size of the
project.
Once the Project Management Review has been conducted, follow up with
program/project managers on any issues or concerns requiring attention, the status of
open items from the review, and CIO reporting actions, e.g., reports to the CIO
Council. The CIO may also recommend quality assurance analysis be conducted.
The project manager is responsible for raising issues or concerns that require
assistance or guidance to the attention of the CIO. These items should be
communicated whenever they become known, and not held to the next Project
Management Review. The CIO will assign appropriate OCIO staff available to help
resolve open items. The program / project manager should communicate the status of
these items in each quarterly review until the items are resolved / closed.
The program/project manager is responsible for tracking the open items from
the review and communicating the status in each quarterly review until the items are
closed. The supporting the scheduling of reviews will coordinate with the
program/project manager after the quarterly reviews to help ensure that new items
have been captured for tracking and action by the program/project manager.
An experienced project manager and his team may manage more than one
project at a time. The project team is responsible for ensuring that the project upon
completion shall deliver the gain in the business for which it is intended for. The
project team has to properly coordinate with each other working on different aspects
of the project. The team members are responsible for the completion of the project as
per the plans of the project.
Q.3:- Explain the various steps in the identification process of a project. What
are the tools used in project planning?
Planning Tools: The tools which may be necessary for coordinating a project
successfully are as follows:-
a) Project organization:
b) Project structure:
Development plan, project tracking and oversight
Initiate Planning
SDP
c) Project Key Personnel: Identify those business areas that are within the
scope or directly interface with the scope boundary and list them in the
“Business area” column of the project assignment worksheet identify the key
personnel for each area and list them in the “Person” column of the project
assignment worksheet.
f) Stage teams :
Identify appropriate personnel required for the stage, define the team
structure and appoint team leaders.
Document the time commitment and responsibilities to be performed
by the team members.
g) Key resources
Individuals assigned to a key resource role may work towards
gathering “Business key resources” and “Technical key resources”.
They are project coordinators and team invitees.
Risk Management: Risks are those events or conditions that may occur and
whose occurrence has a harmful or negative impact on a project. Risk management
aims to identify the risks and then take actions to minimize their effect on the project.
Risk management entails additional cost. Hence risk management can be considered
cost effective only if the cost of risk management is considerably less than the cost
incurred if the risk materializes.
There are different types of risk involved in a project. The main types are as :-
a) Project risks : It is the risk arising out of a change in the scope of the project,
changes in the work quantities, changes in the resource requirements,
estimation error or unexpected developments in a project.
b) Market risks: It is the risk arising out of a change in any of the following
marketing parameter – price change, changes in market regulations, economic
changes, competition, competitors product changes, etc.
c) Industry risk: It is the risk arising out of a change in scientific instruments
used in business activity, changes in company’s policies because of changes in
the industry.
d) Social and political risk: It arises out of changes in labour situation,
labour laws, environment law, etc.
A good PMIS is possible to be developed from the team members and not
from the systems administrators of the company. Organizations tend to allocate such
responsibility by rotation among members with a well designed and structured data
entry and analytical format.
Q.6:- List out the macro issues in project management and explain each.
Macro issues
This step is most difficult since junior members have to respond and
resist to being pushed through sheer innovation and performance – this is how
future leaders would emerge. The PDM process is made scientific through:
i. Earned value management system (EVMS)
ii. Budgeted cost of work scheduled (BCWS)
iii. Budgeted cost of work performed (BCWP)
iv. Actual cost of work performed(ACWP)
iii. Plan Systematically : Success doesn't just happen. Goals and objectives
should be set, problems targeted and rank ordered, reporting and monitoring
requirements developed, and feedback channels established.
vi. Measure and Analyze: This is the technical key to success for a PIP.
Productivity must be defined, formulas and worksheets developed, sources of
data identified, benchmark studies performed, and personnel assigned.
Measuring productivity can be a highly complex task. The goal, however, is to
keep it as simple as possible without distorting and depreciating the data.
Measurement is so critical to success; a more detailed analysis is helpful.
vii. Quality Control: This is very important in any project. Quality control is
possible if the project members follow the quality charts and norms very
strictly.
viii. Schedule Quality Review: It is recommended that quality review be
scheduled at the beginning of the stage and also ending of every stage.
ix. Agenda for quality review: Create and distribute a quality review agenda
specifying the objectives, products, logistics, roles, responsibilities and time
frame.
xi. Follow up: QR complete product status revised from ‘In Progress’ to ‘QR
Complete’.Follow up the actions planned in strict manner which ensures confo
rmity to the standards.
This is the technique to analyze the content of work and cost by breaking it
down into its component parts.
Project key stages form the highest level of the WBS, which is then used to
show the details at the lower levels of the project. Each key stage comprises many
tasks identified at the start of planning and later this list will have to be validated.
WBS is produced by identifying the key elements, breaking each element
down into component parts and continuing to breakdown until manageable work
packages have been identified. These can then be allocated to the appropriate person.
The WBS does not show dependencies other than a grouping under the key stages. It
is not time based- there is no timescale o the drawing.
The Global Delivery Model (GDM): is adopted by an Industry or Business
such that it has a capability to plan design, deliver and serve to any Customers or
Clients Worldwide with Speed, Accuracy, Economy and Reliability.
Adoption of a Combination of the Greatest Common Multiple and the Least Common
Factor of a Large Mass of Microbial Components:
a) Standardization – Ingenious Design and Development of Components and
Features which are like to be accepted by 90% of World-wide Customers.
Global Standards of Design focusing on highly standardized Methods and
Processes of manufacture or Development. Adopt Plug-and-socket Concepts
with minimum adaptable joints or Connections.
b) Modularization – Product or Solution split up into smallest possible
individual Identifiable Entities, with limited Individual Functioning Capability
but powerful and robust in Combination with other Modules.
preferable to 4 one week, 7 the next, 2 the next and so on. Even if there is no limit to
the amount of any one resource available, it is still desirable that resource usage is as
smooth as possible. Given that the resource requirements of those activities on the
critical path are fixed, some order or priority needs to be established for selecting
which activity and which particular resource associated with this activity should be
given priority in the smoothing process. In determining which activity should be
given priority, a subjective judgment should be made about the type of resource (or
resources) associated with each activity; priority should be given to the activities
whose resources are considered to be most important. Beyond this consideration,
activities should be ranked in order of total work content and total float or slack
available for that activity. A useful device for prioritizing is to consider the ratio of
total work content/total float remaining and give priority to activities with the highest
value of this ratio.
ROI may include the benefits associated with improved mission performance,
reduced cost, increased quality, speed, or flexibility, and increased customer and
employee satisfaction. ROI should reflect such risk factors as the project’s technical
complexity, the agency’s management capacity, the likelihood of cost overruns, and
the consequences of under or nonperformance. Where appropriate, ROI should reflect
actual returns observed through pilot projects and prototypes.
may occur earlier. In either case, the information is important for decision making
based on the value of the investment throughout the project lifecycle. Any project that
has developed a business case is expected to refresh the ROI at each key project
decision point (i.e., stage exit) or at least yearly.
Some of the major benefits experienced by sites that installed the information
system that would be important to include in the memorandum are:
In each case above, identify the specific site, systems, and labour involved in
determining the cited benefit. Identify any costs or dollar savings that are known or
have been estimated. The memorandum will be used as tool for responding to any
future audit inquiries on project ROI.
avionics and software problems underscore the need to demonstrate the aircraft's
capabilities before committing to production.
Ideally, ERP delivers a single database that contains all data for the software
modules, which would include:
Manufacturing :
Engineering, bills of material, scheduling, capacity, workflow
management, quality control, cost management, manufacturing
process, manufacturing projects, manufacturing flow.
Supply Chain Management :
Inventory, order entry, purchasing, product configuration, supply chain
planning, supplier scheduling, inspection of goods, claim processing,
commission calculation.
Financials :
General ledger, cash management, accounts payable, accounts
receivable, fixed assets.
Projects :
Costing, billing, time and expense, activity management.
Human Resources :
Human resources, payroll, training, time & attendance, benefits.
Customer Relationship Management :
Sales and marketing, commissions, service, customer contact and call
center support.
Data Warehouse :
And various self-service interfaces for customers, auppliers, and
employees.
ERP Improves Productivity Before ERP systems, each department in an organizatio
n would most likely have their own computer
system, data and database. Unfortunately, many of these systems would
not be able to communicate with one another or need to store or rewrite data to
make it possible for cross computer system communication.
For instance, the financials of a company were on a separate computer system than
the HR system, making it more intensive
and complicated to process certain functions.
b) Mapping of Structures: - a) high shortage risk and effect, long lead and
reaction times, high total inventory cost, frequent engineering changes.
Significance of Documentation
The content of the process Documentation System includes the area supply
chain management from the Odette supply chain Management Group. The
system includes graphical process documentation, in the form of process
chains, as well as the entire range of documentation related to the processes.
The entry point in the documentation system is the model “Process Overview
SCMo”. This model is the starting point for the navigation to other models.
Project Outputs
1. Best practice and policy guides for the use of persistent identifiers in
Australian e-learning, e-research, and e-science communities.
2. Use cases describing community requirements for identifiers and business
process analysis relating to these use cases.
3. E-Framework representations of persistent identifier management services that
support the business requirements for identifiers.
4. A “pilot” shared persistent identifier management infrastructure usable by the
project stakeholders over the lifetime of the project. The pilot infrastructure
will include services for creating, accessing and managing persistent digital
identifiers over their lifetime. The pilot infrastructure will interoperate with
other DEST funded systemic infrastructure. The development phase of the
pilot will use an agile development methodology that will allow the inclusion
of “value-added” services for managing resources using persistent identifiers
to be included in the development program if resources permit.
5. Software tools to help applications use the shared persistent identifier
infrastructure more easily.
6. Report on options and proposals for sustaining, supporting (including
outreach) and governing shared persistent identifier management
infrastructure.