Skip to content
This repository has been archived by the owner on Nov 10, 2020. It is now read-only.

As a project stakeholder, I want to know about project progress at a high level #470

Closed
meiqimichelle opened this issue Mar 2, 2015 · 7 comments
Assignees

Comments

@meiqimichelle
Copy link
Contributor

Stakeholders are interested in project progress. We should provide tangible, high-level info for people who aren't in our project day-to-day, but still need to know that we're moving forward in the right way. Will be provided on a monthly basis.

@meiqimichelle meiqimichelle added this to the Sprint 14 milestone Mar 2, 2015
@meiqimichelle
Copy link
Contributor Author

Done for February. Provided update document to share.

@meiqimichelle meiqimichelle changed the title Better track project progress at a high level Maintain project progress tracking at a high level Mar 13, 2015
@meiqimichelle meiqimichelle modified the milestones: Sprint 15, Sprint 14 Mar 13, 2015
@meiqimichelle
Copy link
Contributor Author

Contextual narrative working group will give update to implementation subcommittee on March 25. Judy will provide this as an update to Paul.

@meiqimichelle
Copy link
Contributor Author

Brainstormed 'another way' with @ultrasaurus. Resulted in @meiqimichelle testing a repo-wiki-based roadmap that tracks project hypotheses and is constantly updated with learnings and progress — see USEITI wiki.

We will know we are right when:

  • we hear feedback from stakeholders (in particular ones that don't follow our progress day-to-day) that they're better able to track what's going on with our project
  • we get fewer 'surprised onlookers' about the direction of site development
  • when we get questions about a site development roadmap or quarterly plan, directing them to the wiki provides the answers people are looking for

@meiqimichelle meiqimichelle changed the title Maintain project progress tracking at a high level As a project stakeholder, I want to know about project progress at a high level Mar 24, 2015
@meiqimichelle meiqimichelle modified the milestones: Sprint 16, Sprint 15 Mar 27, 2015
@meiqimichelle meiqimichelle modified the milestones: Sprint 17, Sprint 16 Apr 10, 2015
@meiqimichelle
Copy link
Contributor Author

Address roadmap concerns.

@meiqimichelle meiqimichelle modified the milestones: Sprint 18, Sprint 17 May 8, 2015
@meiqimichelle meiqimichelle removed this from the Sprint 18 milestone Jan 5, 2016
@meiqimichelle
Copy link
Contributor Author

@coreycaitlin updated the way our wiki is organized and cleaned it up quite a bit. 🎉 We're also going to be using the hypotheses/research branch more extensively over the coming months. We will check back in on this issue and its "we know we are right when"s again soon.

I think we're already hitting the last metric: when we get questions about a site development roadmap or quarterly plan, directing them to the wiki provides the answers people are looking for

...but before the reorg we still weren't quite hitting metrics one and two. It may be that the repo wiki is not the right solution for 'concerned onlookers', or that our content should still be kept there, but it needs to be delivered differently (actively emailed out, perhaps).

@coreycaitlin
Copy link
Contributor

This also seems like something the "what's new" page can help with, to show recent progress and provide evidence of continued activity. Even if it doesn't show where we're going, at least it'll show that we're moving.

Have we had any "surprised onlookers" recently? With this kind of metric, sometimes silence is a good sign...

@meiqimichelle
Copy link
Contributor Author

For right now, we'll take silence is a good sign. If this becomes an active issue again, we will revisit.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants