Differenze tra le versioni di "Project configuration steps - Products"
Da itm wiki.
(→Information of a delivery) (Etichetta: visualeditor) |
|||
| Riga 9: | Riga 9: | ||
|- | |- | ||
| − | |<u>Name</u> || The name of the ''[[glossary|delivery]]''. | + | |<u>Name</u> || The name of the ''[[glossary|delivery]]''. This is a mandatory field. |
| − | This is a mandatory field. | ||
|- | |- | ||
| − | |<u>Output Description</u> || The description of the ''[[glossary|delivery]]''. | + | |<u>Output Description</u> || The textual description of the ''[[glossary|delivery]]''. |
|- | |- | ||
| − | |<u>PBS Type</u> || The type of the ''[[glossary|delivery]]'', which can be one of the following: "Simple Product" (a delivery which is not ), "Collective Grouping" and "External Product". This is a mandatory field. | + | |<u>PBS Type</u> || The type of the ''[[glossary|delivery]]'', which can be one of the following: "Simple Product" (a ''[[glossary|delivery]]'' which is not made of other components), "Collective Grouping" (a ''[[glossary|delivery]]'' which contains other components) and "External Product" (a ''[[glossary|delivery]]'' which is produced outside of the scope of the ''[[glossary|project]]''). This is a descriptive but mandatory field. |
|- | |- | ||
| − | |<u>Impact</u> || | + | |<u>Impact</u> ||The impact of the ''[[glossary|delivery]]'' on the ''[[glossary|project]]''. This is a descriptive field and its value can be blank or "Low", "Medium", "High". |
|- | |- | ||
| − | |<u>PBS Delivery Father</u> || | + | |<u>PBS Delivery Father</u> || This is an alternative way to build the ''[[glossary|product breakdown structure]]'' which allows to choose (and view) the father ''[[glossary|delivery]]''. The most common approach is to manage deliveries in ''[[glossary|grid mode]]''. |
|- | |- | ||
| − | |<u>Expected Delivery</u> || | + | |<u>Expected Delivery</u> ||The expected delivery date of the ''[[glossary|delivery]]''. |
|- | |- | ||
| − | |<u>Actual Delivery</u> || | + | |<u>Actual Delivery</u> || The actual delivery date of the ''[[glossary|delivery]]''. A ''[[glossary|delivery]]'' can be related as an input for a ''[[glossary|sales contract]]'' ''[[glossary|billing schedule]]'' (the relationship can be established only starting from the ''[[glossary|sales contract]]''). In such a case, it will be possible to invoice the ''[[glossary|sales contract]]'' ''[[glossary|billing schedule]]'' only if the <u>Actual Delivery</u> of the related ''[[glossary|delivery]]'' is filled (which means the ''[[glossary|delivery]]'' is done). |
|- | |- | ||
| − | |<u>Milestone</u> || | + | |<u>Milestone</u> || The ''[[glossary|milestone]]'' (one only) to which the ''[[glossary|delivery]]'' is related. When this relationship is established it means the ''[[glossary|delivery]]'' should be done by the time the ''[[glossary|milestone]]'' is scheduled. |
|- | |- | ||
| − | |<u>Milestone Description</u> || | + | |<u>Milestone Description</u> || The description of the ''[[glossary|milestone]]'' (see <u>Milestone</u>) related to the ''[[glossary|delivery]]''. |
|- | |- | ||
| − | |<u>Delivery Predecessors</u> || | + | |<u>Delivery Predecessors</u> || One or more ''[[glossary|deliveries]]'' which are needed in input in order to complete the current one. The relationship contributes to the definition of the ''[[glossary|product flow diagram]]''. |
|- | |- | ||
| Riga 46: | Riga 45: | ||
|- | |- | ||
| − | |<u>Documents</u> || | + | |<u>''Documents''</u> || |
|- | |- | ||
| − | |<u>Tickets</u> || | + | |<u>''Tickets''</u> || |
|- | |- | ||
| − | |<u>Messages</u> || | + | |<u>''Messages''</u> || |
|} | |} | ||
Versione delle 22:17, 7 feb 2016
Some project management methodologies recommend to clearly define the products or output of a project as one of the initial steps. In itmSUITE®, products or project output are called deliveries and are managed mainly through the Deliveries tab of a project. Here, it is possible to define the product breakdown structure which is the tree structure of the deliveries.
Deliveries and their associated product breakdown structure are managed in grid mode (see grid mode for additional information).
Information of a delivery
| Field | Description |
|---|---|
| Name | The name of the delivery. This is a mandatory field. |
| Output Description | The textual description of the delivery. |
| PBS Type | The type of the delivery, which can be one of the following: "Simple Product" (a delivery which is not made of other components), "Collective Grouping" (a delivery which contains other components) and "External Product" (a delivery which is produced outside of the scope of the project). This is a descriptive but mandatory field. |
| Impact | The impact of the delivery on the project. This is a descriptive field and its value can be blank or "Low", "Medium", "High". |
| PBS Delivery Father | This is an alternative way to build the product breakdown structure which allows to choose (and view) the father delivery. The most common approach is to manage deliveries in grid mode. |
| Expected Delivery | The expected delivery date of the delivery. |
| Actual Delivery | The actual delivery date of the delivery. A delivery can be related as an input for a sales contract billing schedule (the relationship can be established only starting from the sales contract). In such a case, it will be possible to invoice the sales contract billing schedule only if the Actual Delivery of the related delivery is filled (which means the delivery is done). |
| Milestone | The milestone (one only) to which the delivery is related. When this relationship is established it means the delivery should be done by the time the milestone is scheduled. |
| Milestone Description | The description of the milestone (see Milestone) related to the delivery. |
| Delivery Predecessors | One or more deliveries which are needed in input in order to complete the current one. The relationship contributes to the definition of the product flow diagram. |
| Delivery Successors | |
| Activities | |
| Documents | |
| Tickets | |
| Messages |
