View and vote on the article here: The Proposed Projects System
The Proposed Projects System| Category | | | Summary | | Those of you who are members of CA-SAS or have worked with the brigade are probably aware of the "projects system" they use. It was originally designed by Gen Sieco and is used to solve several issues within the current brigade system, including |
| | Body | The system basically removes the lowest level of subgroups from the brigade tree and instead moves them into "projects", each with its own project leader. The advantages of this are that the brigade structure is flattened, and therefore easier to understand and administrate. Individual projects, on the other hand, are no longer limited only to their subgroups' members, but can now take on any individual willing to help.
This has been proven to not only raise productivity, but also member motivation, as members are able to get involved with as many interesting projects as they wish to take on. A direct result of this is that creating new projects has become easier and quicker reaction to new demands are now possible.
Whereas C/O's were formerly required to recruit new members for a new subgroup before starting to become productive, they can now mainly rely on the additional spare time of already active brigade members. This means that new projects are not only formed more easily, but also that they will get results much faster.
The projects system was presented to Staff recently. The consensus is, given the very positive experience with the system in CA-SAS, it will be implemented CA-wide in the future. The result will be two sections, the already existing /brigades for administrative purposes, i.e. the Chain of Command, and /projects as a listing of all existing CyberArmy projects to give a better approach to the individual brigades' activities.
/brigades/ remains essentially the same. C/Os can create subgroups in order to better organize their members, and they can set these subgroups to accept anyone, or have them invite-only, or require a special application, etc. The brigade tree will continue to retain the 1:1 restriction (one member can only be in one brigade at any given time), and the member primarily will belong to that one brigade. The only real change here is that the C/Os can create projects, meaning that the brigade trees are flattened as described previously.
/projects/ will be more of a true picture of a brigade's activities; it will show all the projects a brigade has (both ongoing and those with some sort of a deadline), along with who the project leader is and who the various project members are (there will be no more "associates"; you are either a leader, or a member). Each project will belong to *only* one brigade, which will be primarily in charge of its completion (which is not to discourage cross-brigade projects; just that it is much easier when there's only one "boss" compared to two or three). Participation in projects is *not* limited to only those from a particular brigade, but potentially from any brigade, and one person can potentially be involved with more than one project.
Projects can be set up as either public or private. The specific details of projects marked as private will not be shown in each brigade's /project panel, but only include the title so that there isn't an assumption by people that a certain brigade isn't doing *anything*. They can be set up as either "open for joining" or "restricted joins", in which case the project leader will appoint specific people to project positions. There will be a way to mark a project's overall "status", such as "Not started", "Planning phase", "In Progress", "On hold", "Completed", etc. Some sort of project planning code (things like a "to-do" list which leaders can use to give out assignments, a calendar/schedule for tracking meetings/deadlines, "notes" field for updating on major milestones, etc.) will be implemented as well.
This article is only a rough idea of where we are heading with the brigades system. The implementation requires lots of code changes and additions, as well as a more detailed introduction to the C/Os of the various brigades. The current focus is on the release of the CyberArmy source code and a few other projects, but we are hoping to get started with the projects system once more CyberArmy members are able to contribute to the site's source code.
If there are any questions about this outlook, you are more than welcome to direct them to your Brigade C/O or to myself. |
|
This article was imported from zZine. (original author: hisim)
There are no replies to this post yet.
|