Abstraction at this stage actually will prevent us from thinking about
(think of them as "duties" or "roles" within a specific team, for
Regardless of how we group them later, these are all essential functions.
Therefore we must think of each function separately:
* What are its "deliverables" (Success criteria)
* How it works (basic process)
* Which other stakeholder(s) are involved in the process (interdependency)
* What tools were used in the past (we have to offer the same/equivalent/better tools)
Later on we can assign them to any team.
This will allow us to create a workflow.
That workflow will decide how each module is to be designed.
When multiple functions are handled by the same team, we will have to integrate them in one place.
Imagine that each team has its own daily landing page.
All their functions are neatly summarized there (a dashboard, perhaps).
Each team can start any of their "duties" from here, and find all tools that satisfy their workflow.
For each team, all assigned workflows start from this landing page.
Note that we will also have to capture this "meta-model" and present it for all newcomers.
Something like- http://wiki.services.openoffice.org/wiki/Documentation/Building_Guide
Imagine a visitor who wants to know how we work before joining.
We can make a flowchart to explain the process and provide hotspots on it.
Clicking on any hotspot will take the visitor directly to the concerned team's welcome page.
From there, he can look around and get enrolled.
Once the visitor defines his profile (in terms of pre-defined roles), the website can present
04. Project managers
What kind of Project Managers do you have in mind?
Here is my idea of a PM in a collaborative social setup:
He takes care of specific modules and coordinate further amongst coders.
* Accept targets derived from the roadmap requirements
(Coming from the Release Management team)
* Planning to meet the target in coordination with other coders.
* Triage of features and bugs as applicable to the modules in his care
* Tracking the progress with an online Gantt chart system
(e.g. http://openproj.org/, http://www.project-open.com/)
These PMs will need support framework from the website:
* The website should provide a vacancy matrix where coders with specific skills are wanted for
* Coders in turn get credit points for doing work in any group (like "Karma" in Launchpad).
Unsubscribe instructions: E-mail to firstname.lastname@example.org
List archive: http://www.libreoffice.org/lists/website/
*** All posts to this list are publicly archived for eternity ***
Impressum (Legal Info)
: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (MPLv2
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our trademark policy