Project Management in Multicultural Environment: Difference between revisions

From Wikistudy.ByJuho.fi
No edit summary
(+ notice: moved to develop.consumerium.org)
 
(8 intermediate revisions by the same user not shown)
Line 1: Line 1:
<big>'''This page has permanently moved to the [https://develop.consumerium.org/wiki/User:Jukeboksi/BBA_studies/Project_Management_in_Multicultural_Environment Consumerium.org development wiki]'''</big>
Teacher: Pekka Käyhkö
Teacher: Pekka Käyhkö


Line 25: Line 28:


== Project Management in Multicultural Environment - Session 2 ==
== Project Management in Multicultural Environment - Session 2 ==
Instructions for making the project plan for the case company:
'''Six Phases of a Project'''
# Enthusiasm
# Disillusionment
# Panic
# Search for the guilty
# Punishment of the innocent
# Praise and honors for the non-participants ( Teacher )
 
 
'''Instructions for making the project plan for the case company''':
* Understand the case
* Understand the case
* Think of the whole  
* Think of the whole  
* Know the environment
* Know the environment
* Structure should be clear and cover all required areas
* Structure should be clear and cover all required areas ( Teacher )
 
'''Steps in a project''':
 
: 0. Decision - Understand the field. Do we need a project or not ?
 
# [[w:Goal|Goal]]s - Set project goals ( customers, users, project mgr )
# Deliverables - Based on goals, create a list (when/how) project should deliver things
# [[w:Schedule|Schedule]] - Based on deliverables, create a list of tasks (days, resources)
# [[w:HR|HR]] plan
# [[w:Communication|Communication]] plan
# [[w:Risk management|Risk management]] plan
# Ending
 
----
Tasks during lessons:
# Get a good understanding of case 1
# What is the purpose of a project plan?
# Evaluate a project plan taken from the Internet - Can you use it as a plan template?
# Find some templates you can use
# Define
## A process
## A change
 
 
== Project Management in Multicultural Environment - Session 3 ==
* In [[w:New product development|product development]] and [[w:process optimization|process optimization]], a '''[[w:requirement|requirement]]''' is a singular documented physical and functional need that a particular design, product or process must be able to perform. ( Wikipedia )
 
* A '''[[w:work breakdown structure|work breakdown structure]] (WBS)''', in [[w:project management|project management]] and [[w:systems engineering|systems engineering]], is a deliverable-oriented decomposition  of a project into smaller components.
::: A work breakdown structure element may be a [[w:Product (business)|product]], [[w:data|data]], [[w:Service (economics)|service]], or any combination thereof. A WBS also provides the necessary framework for detailed cost estimating and control along with providing guidance for schedule development and control.<ref name="BAH">Booz, Allen & Hamilton [http://science.energy.gov/~/media/opa/powerpoint/Final_Module_2.ppt Earned Value Management Tutorial Module 2: Work Breakdown Structure], [http://science.energy.gov/opa/project-management/tools-and-resources/ Office of Science, Tools & Resources for Project Management], science.energy.gov. Accessed 27. Dec 2011.</ref> ( Wikipedia )
 
* A '''[[w:statement of work|statement of work]]''' ('''SOW''') is a formal document that captures and defines the work activities, [[w:deliverable|deliverable]]s, and timeline a vendor must execute in performance of specified work for a client.
::: The SOW usually includes detailed requirements and pricing, with standard regulatory and governance terms and conditions. It thus overlaps in concept with a [[w:contract|contract]], and indeed SOWs are often legally equivalent to contracts. ( Wikipedia )


== Project management softwares ==
== Project management softwares ==

Latest revision as of 19:46, 2 April 2020

This page has permanently moved to the Consumerium.org development wiki


Teacher: Pekka Käyhkö

Type of course: Free choice studies, toolbox courses in ICT

Code: TOO8LF001

Tools covered: w:Microsoft Project and using w:Microsoft Excel for project management purposes

Project Management in Multicultural Environment - Session 1

  • A project is a temporary endeavor designed to produce a unique product, service or result with a defined beginning and end (usually time-constrained, and often constrained by funding or deliverables), undertaken to meet unique goals and objectives, typically to bring about beneficial change or added value. ( Wikipedia on project management )
  • In contemporary business and science a project is defined as a collaborative enterprise, involving research or design, that is carefully planned to achieve a particular aim ( Wikipedia on projects )
  • Project Management is the process and activity of planning, organizing, motivating, and controlling resources, procedures and protocols to achieve specific goals in scientific or daily problems. ( Wikipedia )
"...a formal, approved document used to guide both project execution and project control. The primary uses of the project plan are to document planning assumptions and decisions, facilitate communication among stakeholders, and document approved scope, cost, and schedule baselines. A project plan may be summarized or detailed.".[2] ( Wikipedia )
  • Usual project progression: Preparing -> Planning -> Implementing -> Closing ( Teacher's PPs )
  • Preparation and planning is often the most crucial phase in a project ( Teacher's PPs )

There are lot of competitors in the area of project management software. See Wikipedia list of project management software.

Project Management in Multicultural Environment - Session 2

Six Phases of a Project

  1. Enthusiasm
  2. Disillusionment
  3. Panic
  4. Search for the guilty
  5. Punishment of the innocent
  6. Praise and honors for the non-participants ( Teacher )


Instructions for making the project plan for the case company:

  • Understand the case
  • Think of the whole
  • Know the environment
  • Structure should be clear and cover all required areas ( Teacher )

Steps in a project:

0. Decision - Understand the field. Do we need a project or not ?
  1. Goals - Set project goals ( customers, users, project mgr )
  2. Deliverables - Based on goals, create a list (when/how) project should deliver things
  3. Schedule - Based on deliverables, create a list of tasks (days, resources)
  4. HR plan
  5. Communication plan
  6. Risk management plan
  7. Ending

Tasks during lessons:

  1. Get a good understanding of case 1
  2. What is the purpose of a project plan?
  3. Evaluate a project plan taken from the Internet - Can you use it as a plan template?
  4. Find some templates you can use
  5. Define
    1. A process
    2. A change


Project Management in Multicultural Environment - Session 3

A work breakdown structure element may be a product, data, service, or any combination thereof. A WBS also provides the necessary framework for detailed cost estimating and control along with providing guidance for schedule development and control.[3] ( Wikipedia )
  • A statement of work (SOW) is a formal document that captures and defines the work activities, deliverables, and timeline a vendor must execute in performance of specified work for a client.
The SOW usually includes detailed requirements and pricing, with standard regulatory and governance terms and conditions. It thus overlaps in concept with a contract, and indeed SOWs are often legally equivalent to contracts. ( Wikipedia )

Project management softwares

Microsoft Project is a project management software program, developed and sold by Microsoft, which is designed to assist a project manager in developing a plan, assigning resources to tasks, tracking progress, managing the budget, and analyzing workloads. ( Wikipedia )

References

  1. Harold Kerzner (2003). Project Management: A Systems Approach to Planning, Scheduling, and Controlling (8th Ed. ed.). Wiley. ISBN 0-471-22577-0. 
  2. PMBOK, 2000 Edition
  3. Booz, Allen & Hamilton Earned Value Management Tutorial Module 2: Work Breakdown Structure, Office of Science, Tools & Resources for Project Management, science.energy.gov. Accessed 27. Dec 2011.