Hey Folks -
Okay I have another totally real er I mean hypothetical case I'd like some input on, regarding a Project that a... circle member accepted.many moons ago. I think this... circle member ... accepted the Project in agreement that there was strong alignment with role purposes and accountabilities, and more so even a look at the team souls and thinking that there wasn't another individual on the team likely to understand the complexities and requirements.
BUT, this ... person ... has repeatedly bumped up against their own skill/experience limitations and the enormity of the Project in question and the ongoing under-resourcing of my er, the department at hand. This Project has high importance but a comparatively low urgency in relation to everyday and normal-for-department project work.
SO. When it comes to 4.1.2.b and related obligations and responsibilities of partners, how/when can a Project get re-assigned? Removed? Resources re-allocated? If a partner accepts a Project, but simply cannot complete it given lack of resource (skill, experience, funding, time) - does it just become an albatross wearing someone down to report no update at every tactical meeting until the end of time?
Does 'duty to process' and accept a project trump other action? I see 4.1.3.a giving some potential value in the last sentence - but don't think I've got a full picture.
"Processing does not mean executing upon captured Next-Actions and Projects, which is not covered by this prioritization rule."