The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.
Difference between revisions of "DCH-RP:Documentation guidelines"
(Created page with "{{DCH-RP:PoC_main_menu}} {{DCH-RP:PoC_main_submenu}}{{TOC_right}} WP5 is using a number of tools to conduct its work. Many of the activities in Work Package 5 require documentin...") |
|||
| Line 5: | Line 5: | ||
This page will summarise how and where to document what. | This page will summarise how and where to document what. | ||
== DCH-RP backlog | == DCH-RP backlog == | ||
[[Category:Proofs Of Concept]] | [[Category:Proofs Of Concept]] | ||
Revision as of 19:14, 18 March 2013
| WP5: Proofs of Concept | Scenarios | PoC Phase 1 | PoC Phase 2 | DCH Glossary |
| WP5: Proofs of Concept | | Documentation guidelines | | DCH Glossary |
WP5 is using a number of tools to conduct its work. Many of the activities in Work Package 5 require documenting outcomes of some sort, and we need to find a way to document progress, outcomes and problems as a way of communication with other project and work package members. Usually, in a Scrum-managed project, team members are physically co-located to facilitate communication and mind-sharing. However, in projects such as DCH-RP this is impossible. Electronic documentation becomes paramount to communicate to team members efficiently and extensively.
This page will summarise how and where to document what.