The types of Project Issues (PI) listed below are rather common for ICT systems, and substantial literature and examples exist for each of them.

These are some recommendations for handling project issues during requirements gathering:

  1. A mature ICT department may have a standard project life cycle and interface with user departments in which a number of project issues are addressed. If this is the case, a reference to those arrangements can suffice prior to the elaboration of issues and aspects that are specific to the project.
  2. For project issues that emerge for specific requirements, it is an option to list the project issue in the suitable slot as part of the Stakeholder template, Business use case (BUC) template, Business object template, or another template. On the other hand, when the PI matters for several functions or a domain, then it may be better to list it in a separate chapter "Project Issues", as illustrated by #lib12 - Project Issues of #2030library.

Some of the project issues are illustrated in the e-parliament tagger example.


PI type Name Definition Examples
18 Open Issues See Volère #lib18 - Open Issues
19 Off-the-Shelf Solutions
In a Collaborative Planning Methodology after having Identified and validated what needs to be achieved, there is a Research & Leverage phase to identify external organizations and service providers that may have already met, or are currently facing needs similar to the ones identified in the current project. #lib19 - Off-the-Shelf Solutions
19a Ready-Made Products See Volère
19b Reusable Components See Volère
19c Products that can be copied See Volère
20 New Problems
During the Research & Leverage the analyst is likely to get a clearer pîcture about new problems that come with implementing (Phase Invest & Execute) the envisaged services in the stakeholder constellation. It is important for the planning of the change to document the new problems so that they can be taken into consideration when organizing and planning for the change. #lib20 - New Problems
20a Effects on the Current Environment See Volère
20b Effects on the Installed Systems See Volère
20c Potential User Problems See Volère
20d Limitations in the Anticipated Implementation Environment That May Inhibit the New Product See Volère
20e Follow-Up Problems See Volère
21 Tasks See Volère #lib21 - Tasks
21a Project Planning See Volère
21b Planning of the Development Phases See Volère
22 Migration to the New Product See Volère #lib22 - Migration to the new product
22a Requirements for Migration to the New Product See Volère
22b Data That Has to Be Modified or Translated for the New System See Volère
23 Risks See Volère #lib23 - Risks
24 Costs See Volère #lib24 - Costs
25 User Documentation and Training See Volère #lib25 - User documentation and training
25a User Documentation Requirements See Volère
25b Training Requirements See Volère
26 Waiting Room See Volère #lib26 - Waiting Room
27 Ideas for Solutions See Volère #lib27 - Ideas for Solutions

Acknowledgement: Volère Template chapter numbers and names used to tag the types of project issues.



Other sub-sections under Requirements templates and patterns


Questions, answers and comments

Add a New Comment

FAQ