Is each feature evaluated according to use cases ?
project methodology
B People
B Planet
B Prosperity
Difficulty
*
Priority
High
Récurrence
OnUpdate
Tests
Are the functions expected by the user and their scope of action defined in order to provide a framework for interactions and not go into the superfluous?
Precisions
User Stories / Use Cases must be specified in relation to uses so as not to lead to an inflation of functionalities that would be superfluous in relation to the users needs . Offering marginal functionalities will generate an unjustified environmental footprint, cost and misunderstanding of the additional service.
Use Case
Definition of Done
Additional elements
Operational issues related to the project
Rule for assessing the level of compliance of the criterion
0 / 0
Life cycle
Conception
8 other criteria related to the recommendation: Organize the project methodology to carry out a Sustainable IT approach
project methodology
What proportion of the functionalities (User Story) have a Sustainable IT component ?
project methodology
Are the Sustainable IT review steps included in the methodology ?
project methodology
Do any functionalities (User Story) only concern the Sustainable IT aspects ?
project methodology
What is the frequency of review / validation of Sustainable IT elements, in a similar manner to "Security" reviews and validation ?
Production
Is the use of continuous integration promoted ?
Production
Do the continuous integration processes not generate gaps in the consideration of Sustainable IT aspects ?
Production
Are non-functional requirements (User Story) dealt with in the same way for the ICT features Sustainable, security and accessibility ?
Production
Is the inventory of the input data made available to be remployed in other projects ?