Project Management Quarter

From CNM Wiki
Revision as of 12:51, 30 March 2018 by Test.user (talk | contribs) (Concepts)
Jump to: navigation, search

Project Management Quarter (hereinafter, the Quarter) is the last of four lectures of Project Quadrivium (hereinafter, the Quadrivium):

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 Product Design Quarter.

Concepts

  • Beta launch. The limited launch of a software product with the goal of finding bugs before final launch.
  • Deliverable. Any unique and verifiable work product or service that a party has agreed to deliver.
  • Incremental delivery. Creating working software in multiple releases so the entire product is delivered in portions over time.
  • Impediment backlog. A visible or nonvisible list of impediments in a priority order according to how seriously they are blocking the team from productivity.
  • Impediment. Any obstacle that prevents an individual or team from completing a task or project. Unscheduled meetings, technical issues, lack of knowledge or expertise, a distracting workplace, and office conflict are all examples of impediments.
  • Project management. The task of getting a project's activities done on time, within budget, and according to specifications.
  • 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.
  1. 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.
    • 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.
  2. Task.
    • Task force (ad hoc committee). A temporary committee or team formed to tackle a specific short-term problem affecting several departments.
    • Task identity. The degree to which a job requires completion of a whole and identifiable piece of work.
    • Task identity. The degree to which a job requires completion of a whole and identifiable piece of work.
    • Task significance. The degree to which a job has a substantial impact on the lives or work of other people.
    • Task significance. The degree to which a job has a substantial impact on the lives or work of other people.
    • Task structure. One of Fiedler's situational contingencies that describes the degree to which job assignments are formalized and structured.
    • Task structure. The degree to which job assignments are procedurized.

Roles

  1. Project manager. The stakeholder assigned by the performing organization to manage the work required to achieve the project objectives.
  2. Developer. Developers are responsible for the construction of software applications. Areas of expertise include development languages, development practices and application components.

Methods

Instruments

Practices

This lecture concludes the Quadrivium. Since the next, third module of the Course is Operations Quadrivium; thus, the successor lecture is Business Inquiry Quarter.