Closed hannahkane closed 8 years ago
cc @ldecoursy @chrislarry33 @davidascher
Meeting scheduled for Wednesday with @cassiemc @simonwex and @davidascher - hoping to do some high level estimating (read: S, M, L) there.
Got about halfway through with @cassiemc and @simonwex. Follow-up meeting scheduled for Friday.
The need represented by this ticket is evolving. I'm going to close this and file new tickets that better reflect recent conversations.
As part of our H1 planning process, we have isolated the production work (read: work that requires design and development resources) implied by our strategic plan.
One of the next steps is to have designers and engineers become familiar with the work and provide effort estimates. Note: we are not asking for time estimates, which are notoriously inaccurate and which many people would be (rightly) resistant to giving. Instead, we are asking for relative estimates of effort (e.g. "Task A is twice as much effort as Task B"). This information, when combined with some assessment of value, will inform prioritization decisions.
Seems like something @simonwex and @cassiemc should help implement. I'd like to help, too.
Also note: we will only estimate the work we have a decent understanding of. Projects that don't yet have a clear vision or requirements won't get estimates.