darkmatter
53
edits
WikiCED manual: Difference between revisions
Jump to navigation
Jump to search
→Explaining and developing the project
Oskenontona (talk | contribs) (→TODO) |
Oskenontona (talk | contribs) |
||
| Line 137: | Line 137: | ||
Except in the simplest cases, one of the most difficult parts of developing a project is explaining it so everyone understands it. Many people (often most) will either assume someone else is taking care of details, or will imagine what the system will be like rather than trying to follow along. Confusion and disappointment inevitably follow. | Except in the simplest cases, one of the most difficult parts of developing a project is explaining it so everyone understands it. Many people (often most) will either assume someone else is taking care of details, or will imagine what the system will be like rather than trying to follow along. Confusion and disappointment inevitably follow. | ||
It's difficult to tune the | It's difficult to tune the balance between too much documentation and too little for each individual. The best approach is to use examples and capture key expectations of all stakeholders, and make sure everyone involved has a chance to participate. | ||
Processes can start open ended, for example using [[wp:appreciative inquiry]] or [[wp:open spaces]] to discover what stakeholders consider the most valuable features, and should become more specific but still inclusive, using techniques such as [[wp:participatory design]]. | Processes can start open ended, for example using [[wp:appreciative inquiry]] or [[wp:open spaces]] to discover what stakeholders consider the most valuable features, and should become more specific but still inclusive, using techniques such as [[wp:participatory design]]. | ||