Simplest way to provide clients with an idea of progress

[iteles]

This is a process issue and we'll need to have a process-specific repo asap ( #13 ). In the meantime:

Problem: Even with access to our repos and issues, clients still email half way through a 2 week sprint to enquire about progress. How can we improve the process so that they know without needing to ask?

Next steps

• [ ] Discuss best ways of keeping clients updated
• [ ] Define what clients actually want to know when they ask 'how are you getting on?' (i.e. which metrics are they interested in or do they want something more anecdotal).

Possible ways of keeping clients update [for discussion]:

• Milestone tracking: Adding issues to a milestone and letting clients track completion through that milestone. This was my fist thought as it's the simplest, but I think the problem here is that a) new issues are added throughout the sprint as bugs are encountered or tasks are split into details; b) a significant number of issues may not be closed until near the end of a project, making actual progress non-transparent to clients. We could however, have a milestone that includes only the high level tasks (set up environments, create minimum chrome extension for testing purposes, etc) laid out specifically to be more indicative to the client
• Readme updates: Split out key tasks and metrics into the readme file and track progress on them there
• Red/Amber/Green flags against key metrics: A sort of mini report on a weekly basis. This could be a little client-specific dashboard, with summaries of interesting metrics plus the weekly status - we'd have to manually enter the status data before we can build some interesting algorithms to churn it out.

[iteles]

Would love to hear more ideas on how this could be done more simply and intuitively