Difference between revisions of "Project Management Quarter"
(→Concepts) |
(→Concepts) |
||
| Line 10: | Line 10: | ||
===Concepts=== | ===Concepts=== | ||
| − | |||
| − | |||
*[[Task performance]]. The combination of [[effectiveness]] and [[efficiency]] at doing core job tasks. | *[[Task performance]]. The combination of [[effectiveness]] and [[efficiency]] at doing core job tasks. | ||
*[[Task performance]]. The combination of effectiveness and efficiency at doing your core job tasks. | *[[Task performance]]. The combination of effectiveness and efficiency at doing your core job tasks. | ||
| Line 17: | Line 15: | ||
#*[[Project management]]. Practice and a set of concepts, based on that practice, that define culture of managing of [[project]]s from the moment when the [[project manager]] is identified to the project closing. | #*[[Project management]]. Practice and a set of concepts, based on that practice, that define culture of managing of [[project]]s from the moment when the [[project manager]] is identified to the project closing. | ||
*[[Scheduling]]. Detailing what activities have to be done, the order in which they are to be completed, who is to do each, and when they are to be completed. | *[[Scheduling]]. Detailing what activities have to be done, the order in which they are to be completed, who is to do each, and when they are to be completed. | ||
| + | #'''[[Enterprise effort]]'''. A determined attempt or a set of attempts undertaken in order to create outcomes of a [[work package]], [[task]], [[activity]], [[project]], [[operations]], and/or [[enterprise]]. | ||
| + | #*[[Work package]]. | ||
| + | #*[[Task]]. | ||
| + | #*[[Activity]]. | ||
| + | #*[[Project]]. One or more [[enterprise effort]]s undertaken in order to create a unique [[deliverable]], most features of which can be identified before the development starts. | ||
| + | #*[[Operations]] (or [[Operations|Ongoing operations]]). Repetitive [[enterprise effort]]s undertaken in order to create a specified [[deliverable]] or a batch of specified [[deliverable]]s using already designed process. | ||
| + | #*[[DevOps]]. Practice and a set of concepts, based on that practice, that define culture of unifying software development (Dev) and software operations (Ops). Its signature toolchain represents a chain of tools that fit one of the following categories: (a) Code, (b) Build, (c) Test, (d) Package, (e) Release, (f) Configure, and (e) Monitor. | ||
===Methods=== | ===Methods=== | ||
Revision as of 12:11, 25 March 2018
Project Implementation Quarter (hereinafter, the Quarter) is the last of four lectures of Project Quadrivium (hereinafter, the Quadrivium):
- The Quarter is designed to introduce its learners to enterprise implementation, or, in other words, to concepts related to implementing enterprise design; and
- The Quadrivium examines concepts of administering various types of enterprises known as enterprise administration as a whole.
The Quadrivium is the first of seven modules of Septem Artes Administrativi, which is a course designed to introduce its learners to general concepts in business administration, management, and organizational behavior.
Lecture outline
The predecessor lecture is Solution Design Quarter.
Concepts
- Task performance. The combination of effectiveness and efficiency at doing core job tasks.
- Task performance. The combination of effectiveness and efficiency at doing your core job tasks.
- Project management. The task of getting a project's activities done on time, within budget, and according to specifications.
- Project management. Practice and a set of concepts, based on that practice, that define culture of managing of projects from the moment when the project manager is identified to the project closing.
- Scheduling. Detailing what activities have to be done, the order in which they are to be completed, who is to do each, and when they are to be completed.
- Enterprise effort. A determined attempt or a set of attempts undertaken in order to create outcomes of a work package, task, activity, project, operations, and/or enterprise.
- Work package.
- Task.
- Activity.
- Project. One or more enterprise efforts undertaken in order to create a unique deliverable, most features of which can be identified before the development starts.
- Operations (or Ongoing operations). Repetitive enterprise efforts undertaken in order to create a specified deliverable or a batch of specified deliverables using already designed process.
- DevOps. Practice and a set of concepts, based on that practice, that define culture of unifying software development (Dev) and software operations (Ops). Its signature toolchain represents a chain of tools that fit one of the following categories: (a) Code, (b) Build, (c) Test, (d) Package, (e) Release, (f) Configure, and (e) Monitor.
Methods
Instruments
Practices
This lecture concludes the Quadrivium. Since the next, third module of the Course is Operations Quadrivium; thus, the successor lecture is Compliance Research Quarter.
