[Ux] *PMT/PCP Planning and coordination meeting*
kasper at markus.dk
Thu Mar 27 12:24:20 EDT 2014
Thanks for the quick replies!
There was no date where everyone was able to join. Since the first step
is to gather all the remaining work/features/requirements to the
PCP/PMT, the prioritization for finding a date has been a mix of getting
the most people present and ensuring that the key people for defining
these requirements are present.
*The meeting will be held on: Wednesday, April 9, at 14:00 CEST
*We will have the meeting in the second gotomeeting room:
If you have items for the agenda, please send them as a reply to this mail!
Thanks and see you all then,
On 3/26/14 12:48 PM, Kasper Markus wrote:
> Hi PCP/PMT teams + friends (In particular: *Jan-Paul, Chris, Alex,
> Dana, Jess, Justin, Colin, Andres, Michelle, Ignacio, Claudia,
> Andreas, Christophe, Steve Githens*, and whoever I forgot)
> Seeing how were half way through the project, are wrapping up the
> pilots work and have to start worrying about the next review, I'd like
> to call for a *PMT (and PCP) planning meeting* with the goals (more
> goals are welcome):
> * Get an overview of *all the remaining work/features* for the PMT/PCP
> * Get an overview of the remaining resources
> * What are the requirements on the PMT from other activities in the
> * What is the targeted fidelity of each feature (ie. paper
> prototype, prototype implementation, production state, etc)?
> * Make a roadmap with dates, priorities, assignees, etc.
> In other words, the goal is to make a plan for ALL the remaining work
> - ensuring that it's possible (and reacting on it, if it's not, etc).
> I've created a doodle poll for finding a suitable date. As the PMT/PCP
> affect quite a few areas of C4A, the list of people that would be
> useful to have present is also quite long (PMT leads, PCP/PMT
> implementers, designers, MM teams for feedback mechanisms,
> representatives for the common terms work, architecture team reps,
> etc).. So when filling out the doodle poll, please try to be as
> flexible as possible.
> Kasper Galschiot Markus
> Lead Research Engineer,
> Raising the Floor - International,
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Ux