When all the tasks are completed, the MP moves to COMPLETED stage. They may add additional tasks in this phase. In this process they try to give an estimate on the time they spent on the task in order to help quantifying work put into it. The participants run through their tasks and mark them as completed when they are. When planning is completed, the participants move the project to IMPLEMENTATION status. If another role is needed, one is added and the project reverts to BOARDING status. The participants create tasks (this may be other MP's) amongst themselves, decide dependancies of eachother's tasks and decide how to do the project. When the team is full, the project moves to PLANNING status. The project is ready to accept participants and will accept anyone joining into the project as filling a role. When they are complete, the project changes to BOARDING status. The project is currently waiting for the MP's it is depending on to complete. Initially the MP is in either WAITING or BOARDING status. A community member can choose to be one of these roles and will work towards the goal of this role.įinally, a MP has a status. It has a list of other miniprojects that it depends on to be completed before the project can be started.Īlong with those, a MP lists a series of roles along the goal of this role in the miniproject. A miniproject may be given priority by either votes and/or council decision - this means it will be marked as a priority miniproject in listings in order to give the community work direction.Ī MP (Miniproject) has two descriptions, one short, one long. This post is about a hypothetical web system that might do the trick.įirst off, I'd like to describe a miniproject formally. ![]() So how can we deal with this? We are many talents in this community and we could easily do very complex and big activities -but- we aren't that well organised and we might need tools to help us become so. We also have problems quantifying the amount of work people put into the community into karma. ![]() ![]() The other problem is that newcomers into the community rarely know where they could contribute or fit in. Along with that, we have the problem that there's no 'staff' as such (excepting paid staff which is a scare resource) to allocate onto projects. The principle is that in a community we have a lot of interwoven mini projects that often depend on the completion of others. Initially it started out as an idea for Mer, but I think it might scale to the requirements of the community. Due to the scale of the community and the less-than-optimal sprint system for the activities in the community I have lately pondered if there was a way to try and handle the many activities this community could be doing.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |