Difference between revisions of "Project Parties and Roles"

From CNM Wiki
Jump to: navigation, search
 
(60 intermediate revisions by 2 users not shown)
Line 1: Line 1:
−
[[File:Cnm-digital.png|400px|thumb|right|[[CNM Cyber suite]]s]][[Sides of Project Work]] (hereinafter, the ''Lectio'') is the [[lectio|lesson part]] of '''[[Project Work Essentials]]''' [[lesson]] that introduces its participants to [[project management]] concepts. This ''lesson'' belongs to the ''CNMCT Entrance'' section of the [[CNM Cyber Placement]].
+
[[File:Cnm-digital.png|400px|thumb|right|[[CNMCyber suite]]s]][[Project Parties and Roles]] (hereinafter, the ''Lectio'') is the [[lectio|lesson part]] of '''[[Project Work Essentials]]''' [[lesson]] that introduces its participants to [[project management]] concepts. This ''lesson'' belongs to the ''CNMCT Entrance'' section of [[CNMCyber Bootcamps]].
  
  
 
==Content==
 
==Content==
−
The predecessor [[lectio]] is [[Developments at the Wiki]].
+
The predecessor [[lectio]] is [[What Project Work Is]].
  
 
===Script===
 
===Script===
−
:Any development of a unique [[work product]] can be defined as a [[project]]. An adjective, ''unique'', means one-of-a-kind and indicates something that this developer has never created before. Landing a new job, modification of a [[business]], and re-designing a [[website]] could serve as examples of projects.
+
:No doubts; no one has to hire a helper to buy a bicycle. Work on bigger and costlier [[project]]s commonly involves two [[project party|parties]]. [[Development administration]] is one party; this person or people order and finance [[work product]]s. [[Project management]] is another party; that person or people deliver the ordered ''products''.
  
−
:Developments of those ''work products'' that this developer has already created are called [[operations]]. Production of thousands of smartphones of the same model is an ''operation''. Launching a new model of a smartphone is a ''project''.
+
:Both parties may belong to one [[organization]]. Otherwise, the organization that orders the ''project'' is called a [[project customer]]. The organization that delivers project results is called is a [[project owner]].
  
−
:In real life, each of us has worked on various projects even without realizing that. Have you ever bought something that lasts for long time? Let say, a bicycle? That was a ''project.'' Have you ever sold your old bike? Unless you work as a seller in a used bike store, that was a ''project'' as well.
+
:The ''project owner'' is responsible for ''project management''. To direct, monitor, and/or support [[project personnel]], the owner may set up a [[project management office]], often abbreviated as [[PMO]].
  
−
:In the [[corporate world]], ''projects'' usually involve several people; some of them last many years. Work on big and costly ''projects'' commonly has two sides.
+
:In management of [[Waterfall project]]s, a [[project manager]] is the key role. These managers concentrate on development of approved products at approved budgets and on approved schedules.
  
−
:[[Enterprise administration]] is one of them. That mostly involves deciding what needs to be developed and allocating some budget for the project work. The paying [[customer]] is the mandatory role on that side. The ''customer'' may hire a [[product owner]], [[project sponsor]], or other people whose [[area of responsibility]] is making sure that the ''customer's'' money are spent on the product that the ''customer'' looks for and that is delivered on time.
+
:A ''project manager'' leads [[project planning]] until [[project baseline|baseline]]s are approved, [[project executing]] until [[deliverable]]s are validated, and [[project closing]]. For the ''planning stage'', a ''manager'' may hire [[business analyst]]s to collect [[requirement]]s and [[systems engineer]]s to design a [[system]] as a [[solution]]. Those developers that directly create [[deliverable]]s are hired only for the ''executing'' stage.
  
−
:Another side is [[project management]], which involves actually spending the ''customer's'' money on the product and product delivery that the ''customer'' looks for.
+
:If [[project personnel]] is fewer than 5-9 people and the [[project schedule|schedule]] is not compressed, the ''manager'' is rarely a dedicated role. One of developers or someone else may act as the ''project manager'' in addition to other responsibilities.
  
−
:If the project work is or can be predicted, the [[project manager]] plans the development, discusses the plan with the ''customer's'' representative, and executes the approved plan.
+
:In ''Agile'', ''management'' functions are distributed between several roles. For instance, developers define work based on [[solution requirement]]s such as [[user stories]].
  
−
:If the project work cannot be predicted, manager's opportunities to plan are limited. [[Agile methodology|Agile methodologi]]es address that issue. Developers usually work in iterations and, as soon as new increments are developed and new data is discovered, discuss the future product and its delivery with the ''customer's'' representative. [[Scrum Master]]s or similar ceremonial roles control the development process.
+
:In the ''planning stage'', some coordinator, for instance, an [[account manager]] working for [[PMO]], hires members of the planning team in addition to the ''product owner''. This team conducts [[Sprint Zero]] or a similar activity undertaken to create a [[product backlog]].
  
−
:''Project managers'' control the development of the right product at the right budget and on the right schedule. ''Scrum Masters'' don't deal with work products and deliveries; instead, ''Scrum Masters'' make sure that the development goes according to the agreed rules.
+
:The development team is hired for the ''executing stage''. Besides the ''product owner'', that team consists of developers, and, possibly, a ceremonial role such as a [[Scrum Master]]. Developers usually work in iterations and, as soon as new increments are developed and new data is discovered, discuss the future product and its delivery with the ''product owner''. ''Scrum Masters'' don't deal with work products and deliveries; instead, ''Scrum Masters'' make sure that the development goes according to the agreed rules.
  
−
:Building a new house is an example of the project that needs a project manager. The humanity has been building houses for thousands of years. The process is well-known -- the builders should lay the foundation first, put the walls second, and so on. The cost of labor, cost of material, the timeline can be predicted. So, a ''project manager'' would be busy with hiring right workers, ordering right materials, and directing the construction. If we hire a ''Scrum Master'' and a dozen of construction workers and ask them to do their best without any manager, most likely, we would get a mess.
+
:Unlike ''project management'', ''development administration'' is often distributed between two organizations if two organizations are involved in one project.
  
−
:On another side, [[CNM Cyber]] development is a ''mess''. No one has created ''CNM Cyber'' before -- we cannot predict how it will look like, let say, 2 years from now. Volunteers lead developments in which they are interested in and when their time allows. However, this ''mess'' is controlled; to do so, the [[CNM Cyber Team]] has developed its own [[CNM Agile]] framework.
+
:The [[project customer]] identifies a [[business need]], which is a [[problem]] to be solved, initiates a [[project]] to create a [[solution]], and provides the budget for the ''project''.
  
−
:In [[CNM Agile]], a [[project manager]] is rarely a dedicated role; ''project management'' is distributed and ''projects'' are managed at a micro-level.
+
:The [[project owner]], consequently, hires someone who acts on behalf of the ''customer'' while approving solution requirements, [[project baseline]]s, and/or assessing whether the work product meets [[acceptance criteria]].
 +
 
 +
:In ''Waterfall projects'', this administrative role is called [[project sponsor]]. ''Baselines'' is not a feature of ''Agile projects'', so the administration concentrates on product requirements only.
 +
 +
:A [[product owner]] is the key administrative role in [[Agile project]]s. This person concentrates on envisioning of the right product, describing that product usually using [[user story|user stories]], and prioritizing the [[product backlog]]. ''Product owners'' do not deal with budgets, schedules, as well as other management functions such as hiring and procurement. The [[area of responsibility]] of ''product owner'' is making sure that the ''customer's'' money are spent on the product that the ''customer'' looks for.
  
 
===Key terms===
 
===Key terms===
−
:[[Enterprise administration]], [[project management]], [[project sponsor]], [[product owner]], [[project manager]]
+
:[[Project party]], [[development administration]], [[project management]], [[project customer]], [[project owner]], [[project personnel]], [[project management office]] ([[PMO]]), [[project manager]], [[project baseline]], [[business analyst]], [[systems engineer]], [[Scrum Master]], [[business need]], [[project sponsor]], [[product owner]]
  
 
===Closing===
 
===Closing===
−
:
+
::Write True or False:
 +
::[[Project owner]] refers to direct customer who owns and finances the project.
 +
 
  
−
The successor [[lectio]] is '''[[What Project Work Is]]'''.
+
The successor [[learning activity]] is '''[[CNMCT Entrance Exam]]'''.
  
 
==Presentations==
 
==Presentations==

Latest revision as of 02:57, 21 October 2023

CNMCyber suites

Project Parties and Roles (hereinafter, the Lectio) is the lesson part of Project Work Essentials lesson that introduces its participants to project management concepts. This lesson belongs to the CNMCT Entrance section of CNMCyber Bootcamps.


Content

The predecessor lectio is What Project Work Is.

Script

No doubts; no one has to hire a helper to buy a bicycle. Work on bigger and costlier projects commonly involves two parties. Development administration is one party; this person or people order and finance work products. Project management is another party; that person or people deliver the ordered products.
Both parties may belong to one organization. Otherwise, the organization that orders the project is called a project customer. The organization that delivers project results is called is a project owner.
The project owner is responsible for project management. To direct, monitor, and/or support project personnel, the owner may set up a project management office, often abbreviated as PMO.
In management of Waterfall projects, a project manager is the key role. These managers concentrate on development of approved products at approved budgets and on approved schedules.
A project manager leads project planning until baselines are approved, project executing until deliverables are validated, and project closing. For the planning stage, a manager may hire business analysts to collect requirements and systems engineers to design a system as a solution. Those developers that directly create deliverables are hired only for the executing stage.
If project personnel is fewer than 5-9 people and the schedule is not compressed, the manager is rarely a dedicated role. One of developers or someone else may act as the project manager in addition to other responsibilities.
In Agile, management functions are distributed between several roles. For instance, developers define work based on solution requirements such as user stories.
In the planning stage, some coordinator, for instance, an account manager working for PMO, hires members of the planning team in addition to the product owner. This team conducts Sprint Zero or a similar activity undertaken to create a product backlog.
The development team is hired for the executing stage. Besides the product owner, that team consists of developers, and, possibly, a ceremonial role such as a Scrum Master. Developers usually work in iterations and, as soon as new increments are developed and new data is discovered, discuss the future product and its delivery with the product owner. Scrum Masters don't deal with work products and deliveries; instead, Scrum Masters make sure that the development goes according to the agreed rules.
Unlike project management, development administration is often distributed between two organizations if two organizations are involved in one project.
The project customer identifies a business need, which is a problem to be solved, initiates a project to create a solution, and provides the budget for the project.
The project owner, consequently, hires someone who acts on behalf of the customer while approving solution requirements, project baselines, and/or assessing whether the work product meets acceptance criteria.
In Waterfall projects, this administrative role is called project sponsor. Baselines is not a feature of Agile projects, so the administration concentrates on product requirements only.
A product owner is the key administrative role in Agile projects. This person concentrates on envisioning of the right product, describing that product usually using user stories, and prioritizing the product backlog. Product owners do not deal with budgets, schedules, as well as other management functions such as hiring and procurement. The area of responsibility of product owner is making sure that the customer's money are spent on the product that the customer looks for.

Key terms

Project party, development administration, project management, project customer, project owner, project personnel, project management office (PMO), project manager, project baseline, business analyst, systems engineer, Scrum Master, business need, project sponsor, product owner

Closing

Write True or False:
Project owner refers to direct customer who owns and finances the project.


The successor learning activity is CNMCT Entrance Exam.

Presentations

Slideshow

Video

Retrieved from "https://pravka.bskol.com/w/index.php?title=Project_Parties_and_Roles&oldid=119314"