S¶
Schedule management¶
XXSchedule managementX
Documentation of the (technological) requirements for the project, definition of agreed dates and deadlines, including their optimisation and monitoring.
Scheduling¶
Scheduling
Documentation of the (technological) requirements for the project, definition of agreed dates and deadlines, including their optimisation. The monitoring of deadline adherence is also often defined as a function of time scheduling.
Scrum artifacts¶
Scrum artifacts
Represent activity(ies) or value(s) and are designed to ensure that key information is made transparent. Each artifact includes a Commitment that provides information in a clear and concise way to visualise progress.
This includes for the
- Product Backlog the Product Goal.
- Sprint Backlog the Sprint Goal.
- Increment the Definition of Done.
Scrum Master¶
Scrum Master
Creates an agile environment within the company and thereby enables Scrum. As a contact person for the Developers, his responsibilities include:
- Coaching team members to work in a self-managed and cross-functional way.
- Supporting the Scrum team in producing Increments that meet the Definition of Done and that add value to the final product.
- If the Scrum Team is hampered, removing the impediments.
- Responsible for ensuring Scrum events are held in a way that is positive, productive and within the time box.
Scrum roles¶
Scrum roles
- Product Owner
- Scrum Master
- Developers
Scrum Team¶
Scrum Team
Small team of people with no sub-teams or hierarchies.
Consisting of
- one Scrum Master,
- one Product Owner, and
- Developers, generally
- 10 or fewer people.
- cross-functional, and
- self-managing.
Scrum values¶
Scrum values
Five values in Scrum that the whole team shares.
- Commitment
to the rules of Scrum. - Focus
on the task(s) at hand. - Openness
to new things and to other team colleagues. - Respect
all project participants. - Courage
to stand by the values and to interact with each other in an open and honest way.
Scrum¶
Scrum
Scrum is a framework that originated in agile software development, but is now used to develop a wide variety of products. Specific for Scrum is the incremental approach to continuously generate added value by using recurring quality assurance measures as monitoring and control mechanisms during the whole project life-cycle.
Sender-receiver principle¶
Sender-receiver principle
Communications theory, stating that all communications comprise messages being sent and received. This model proposes that it is impossible not to communicate – breaking off communication or refusing to communicate also sends out a signal.
- Responsibility of the sender:
Ensures (by asking the recipient) that the message has been properly received (repeat if necessary).
- Responsibility of the recipient:
Ensures correct understanding of the message (either by repeating the message in own words or by asking the sender what is meant).
Slack time¶
Slack time
In a network diagram: the time differential between the specified completion date of a task and the date required to meet the critical path. Slack time can be needed for technological reasons or to provide reserve time.
Soft factors¶
Soft factors
Soft skills are personal attributes (e.g. human/ social/ communication skills, attitudes, mindsets) that enable people to navigate their environment or work well with others to achieve their goals.
Solution-neutral¶
1 2 |
|
Specification¶
Specification
Detailed (operational, technical) description of the product's characteristics. Ensures that project outcomes (goals) are determined before the project is carried out.
Specification of inputs¶
Specification of inputs
A list of the quantities of materials or standard components that are required for a project and can be quantified in terms of time or costs.
Sponsor¶
Sponsor
A person or entity which donates funds or payment in kind for advertising purposes (e.g. to a sports club). In the USA, it is also used to describe the person funding a project.
Sponsoring organisation¶
Sponsoring organisation
A generic term for the organisation, authority, association etc. that commissions, finances and defines a project's objectives. Synonym: project sponsor
Sprint¶
Sprint
A Sprint is a time-boxed iteration within which the Scrum events (Sprint Planning, Daily Scrums, Sprint Review and Sprint Retrospective) take place and the Product Owner's ideas are transformed into valuable results (= Increments). A Sprint lasts a month or less and a new Sprint starts directly after the previous Sprint has been completed.
Sprint Backlog¶
Sprint Backlog
The Sprint Backlog is a backlog of tasks or activities which are going to be carried out in the upcoming Sprint. The Commitment of the Sprint Backlog is the Sprint Goal.
Sprint burndown chart¶
Sprint burndown chart
Sprint tracking tool for graphical analysis of the sprint process.
Sprint Planning Meeting¶
Sprint Planning Meeting
The Sprint Planning Meeting is the initiation of the following Sprint. During this meeting, the work to be done during this Sprint is determined. At the end there will be a plan that has been created by the whole Scrum Team.
Topics covered:
- Why is this Sprint valuable?
- What can be achieved in this Sprint?
- How should the selected tasks be completed?
Sprint Retrospective¶
Sprint Retrospective
Opportunity for Developers to improve productivity and processes in a Sprint, usually held after the Sprint Review.
Sprint Review¶
Sprint Review
Collaborative meeting for inspecting the outcome of the Sprint and determining future adaptations. The Scrum Team presents the achieved work to key stakeholders and progress toward the Product Goal is discussed.
Stakeholder¶
Stakeholder
A legal or natural person with a vested interest in the project or its outcome. (See project team members)
Stakeholder analysis¶
Stakeholder analysis
Systematic documentation of the interests and intervention powers of all stakeholders, their classification in a stakeholder portfolio (e.g. according to influence or degree affected) and the definition of measures for interactions with stakeholders (e.g. communication, information, integration in the project team or the steering committee). Method for analysing and visualising the stakeholders' influence on the project. Stakeholders can classified in a matrix which measures the impact of the project on them and their influence on the project's success.
Stakeholder management¶
Stakeholder management
The application of management methods for a correct handling of stakeholders.
Stakeholder¶
Stakeholder
An individual or community of interest that has or could have an impact on the project as well as all people, organisations, etc. which are involved or affected by the project.
Standard network diagram¶
Standard network diagram
A network diagram which can be used for several (similar) projects.
Standard WBS¶
Standard WBS
A work breakdown structure which can be used for several (similar) projects.
Standards¶
Standards
A term describing two different, but related, terms:
- All standards, rules and guidelines (some external) valid for a specific field of activity.
- All work methods, document templates, values etc. that apply within a specific field of activity.
Steering committee¶
Steering committee
Committee with authorised members to which project representatives report. Its members can be the customer, investor(s), representatives of official bodies and public agencies. Some organisations differentiate between two kinds of steering committee: one as the project sponsor's internal committee and the other as a committee that also has external partners as members. The number of steering committee members should be kept to the minimum. It serves as a reporting, decision-making and escalation body for the project manager.
Stress management¶
Stress management
Stress Management is a collective term for the methods applied to manage stress.
Structuring¶
Structuring
The establishment of classification systems for products, processes, resources, costs etc. The majority of these are classified in the work breakdown structure, which also enables project definition.
Sub-project manager (= SPM)¶
Sub-project manager (= SPM)
Person responsible for a sub-project, he is part of the project management team.
Sub-task (= ST)¶
Sub-task (= ST)
A group of related work packages in the work breakdown structure. Sub-tasks can be defined at several levels, whereby each higher-level sub-task comprises a group of related sub-tasks at the next lower level. A task in the work breakdown structure that can be further sub-divided.
Supplier specification (= Performance specification)¶
Supplier specification (= Performance specification)
The supplier's strategy for implementing the customer specification. In most cases, the supplier specification is agreed between the customer and the project (manager), though it is often simply one of the contractor's internal documents.
Support processes¶
Support processes
All preparatory and support processes, particularly the supply of materials and equipment, that are necessary for project implementation.
System of objectives¶
System of objectives
Integral, systematic list of project objectives and their interrelationships.