I am thinking I need a model to follow and adjust as I go along so this is a good topic for a blog series. I started reading a book on this subject and I'll try to document this process. The first meeting is tomorrow with a curriculum group about a project we call "Dashboard". Not sure why it ever got that name, probably due to our grandiose plans for all that it would accomplish someday, but it has never been more than a curriculum mapping tool. The purpose was to map the activities, resources, and assessments that we use to our curriculum (state content standards) in order to show that we cover all of the intended standards and to make sure there are not "gaps" in our coverage. So this seems like a good place to develop my planning model, test it out and modify it.
Here is the jumping off (or in) point. I am going to summarize the process from the above mentioned book and then break down the responsibility for each of these steps:
- Identify Stakeholders - Users and Roles
- Identify User Stories - Descriptions of what the site should be able to do
- Incremental and Iterative planning - Setting a timeline and expectations
- Determine what success will look like - User Defined Acceptance tests
- Determine best way to accomplish - Iterations carried out from the timeline
- Continuous Build - carry out iterations, run acceptance tests, review issues
- Who needs access to this system and what should each role be allowed to do?
- What constitutes a curriculum map?
- How will you use it?
- What should it look like?
- What links need to be a part of the map?
- What special features or characteristics does it need?
- What is most important?
- When do you need it?
- What will success look like?


