A group of people doing stuff
Activity Monitoring & Quick Access Panel
User can quickly see if others send him a message and directly reply to them.
User can see if “watches” are triggered.
User sees a list if clicking on one of the Activity Icons
User can filter activity's by project, group etc.
User can create Books and set corresponding preferences on sharing edit rights.
User can create groups and invite people to join
Social Networking
User can login using his Facebook Account. If user doesn't exist in tiki user will be created.
User can manage which Social networks will be connected with his account.
Once Social Networks are connected user can “push” content towards his Social Networks Channels based on Rules and promote pages post etc. with one-click.
Geo Data
User can identify his current location.
User can identify distances to other geo information based information (wehre to buy, which is the closest co-worker)
Trusted Network Builder
Manages Core groups of Judges and Monitors their reliability for the Trusted Network.
Only members are allowed to register known by an existing Member.
Members will have a Weighted Rating relation.
Existing user can define the level of relation on invitation of new user (tight, loose, related)
Teambuilding
Teams alias Channels alias Worlds alias Projects
1 Team = 1 Group of People = 1 Project = 1 set of objects/pages that is controlled by the team
From the project perspective it might be easier to have a 1:1 relation, 1 team can only have 1 project. From the data perspecctive this would be just one table to handle it.
The social aspect might favour a permanent team ("friends, collegues") but having differnt projects together.
Creating Team
User can create a team
User can join a team
User can associate Members with the team
User can associate individuals, teams or Virtual Companies/Projects with a task
Roles
A role could be: functional or social
A worker can switch easily between set of Roles by switching his Avatar
"in the role of the other person" function using Avatar feature
Some possible roles:
Technical sales contact
Dedicated project manager if job is accepted (requires upfront payment)
Coder
Developer
Visionary technical scout
Designer
GUI designer
Usability tester
QS
Consultant off site / on site
Doc
Task manager
Spokesman
Integrator
Reseller
Distributor
Trainee
Noob
Knowledge Worker
Manager
Stakeholder
Evangelist
Early Adaptor
Assistant
Project Sponsor
Director of Security
Project Director
Assistant Director of Identity Management
Project Manager
Project Coordinator Identity Management
Team Members
Engineers
Training
Customer Support
Marketing
Customers
Customer Representatives
Security Advisor
IT Policy Director,
Consultant Advisor
Workspace
Have Workspaces connected to Avatar and Roles
Avatar (functionality can maybe also achieved through workspaces)
A standard Avatar is created alongside with the User Registration.
A Avatar could serve as container for a set of Roles
If "Multiple Avatar" feature is deactivated "User equals Avatar"
A person can have unlimited count of Avatars (if perm)
An Avatar contains an optional "skill profile" which will help to aid ((Weighted Rating))
If no Profile is supplied ((Weighted Rating)) automatically will continuously sharpen the Avatars Profile.
a worker could have an Avatar for each of his jobs, occupations or interests.
Each Avatar can have its own TimeCard
Avatar name can be changed
User Example:
Avatar 1 -> Project Manager @ Company A
Avatar 2 -> Project Manager @ Company B
Avatar 3 -> Private Shopping
Avatar 4 -> Research Regarding Project Management (effecting Company A&B)
An Avatar can have an associated workspace which (optionally) automatically triggers when active.
User can activate several avatars from same IP/Computer but in different Tabs/Windows
User can Monitor multiple avatar activities through same “Activity Monitor”
Task List
User can create Task Lists (Timeline display optional) from Tasks.
User can create Tasks directly at the List.
User remove tasks from the Task List.
User can Edit existing tasks.
User enter % of completion on tasks.
Task Ownership
User can specify the owner of a task. By default creator is the owner.
User can take ownership of tasks or delegate (permission)
User can Monitor Tasks and receive notifications (eg. Email, status.net) when ownership or status changes.
Splitting of Tasks
User can split a single Task into several subtasks or independent (parallel) Tasks
Reunion of Tasks
User can merge Tasks. If Tasks are at different levels (Parent Child) the resulting task reside at the higher level.
Project Management
see: http://dev.tiki.org/Project+Management
User can evolve a note to a task, splitt a task into several tasks group those to a project and build a Virtual Compnay form a project. Change State Wiki by switching page types and setting up conditions via connection editor.
Resource market
User can place bids or ask for biddings on tasks/projects. User can define minimum/maximum amount, due date, min./max. average rating and can ”push” bid-request through this .
User can pipe a sales channel to the market
User can post ideas, job offers, projects etc at the job-drop-box
User can define a finders fee or commission as minimum share on those jobs
User can identify which open projects are closest to his position.
User can identify on submission of an idea a Direct or Dedicated contact (person/platform).
User can identify the status on denial/acceptance of a job or idea
User can define requirements such as:
features
deadline, type of support (eg. long term, none)
budget
User can define contractual level of cooperations and can easily access clear definitions of obligations for both
User will receive a bid within a defined timeframeclear foreseeable/fixed pricing
User receives clearly defined technical requirements
User can easy pick up smaller portions a larger project
User can submit or update his work capabilities within a single input form (when registered).
User can connect his social network accounts for communication purposes.
User can monitor job inquires and bookings
User can meet and track the other "team members" via status.net, facebook and internal services (IM)
User can access support and has a easy way to call for (sales orientated) support on submitting or booking jobs
User can bid/submit before being actually registered. (similar to writing)
User can building a team fulfilling fast moving requirements ad hoc.
User can manage multiple projects for several customers (Avatar)
User can submit multiple skill profiles and offer those at different rates
User don't have to bother with billing and insurance (outsourced)
Tasks
tasks have single owners.
User receive/submit a definition of rewquired results.
User has to submit/receive clear deadlines.
User will receive a "payment" guarantee for his commitment on work.
User will benefit from an "insurance" or “product delivery guarantee” if workers fail to finish on time.
Group of users will earn (90*)% of bids ((10*)% for poiesis as handling fee) when no guarantees made
Group of users will earn (65*)% of bids ((35*)% for poiesis as fee) when guarantees made (Vworker.com)
User can participate on code submission race. Best implementation will earn the most.
User has a limited number of votes. Count based on commitment, number of user seats, billing volume, rating
User can use his (earned & limited) votes for voting on “features” and prioritize his feature request
User can access an “acceptance progress bar” representing the “acceptance workflow” for his submissions.
- Numbers are examples
Scenario:
Group of Content developers, Software Developers Graphic Designers setting up a project, maybe for a real customer or to build a product which might be of commercial interest in any means. Customer delivers Pflichten Heft and through auctioning a agreed pricing will be determined. Depending on collaborative work amount the participants will receive their payment. A customer could be also a “non existing virtual” entity and payment could be a share of whatever future revenue might be (not necessarily money).
Task Splitter & Delegator
User can commit to a specific task completion to generate trust
User has the ability to break tasks down into smaller tasks and delegate further
User can delegate tasks (effectively) to the ‘right’ person
User has focus on important tasks through the activity monitor
User can prioritize tasks
User can build task oriented meeting agenda and review tasks during meeting
User can create easily tasks from notes or other page types
The creating User of a task is the owner unless he delegates to other user.
User can use critical path calculation & assignment
User can switch between graphical reports eg. By switching from GANTto Swim-Lane
User can build work breakdown structure
User can add tasks to a callendar by drag&drop
User can use auto prioritize and dependency builder to “sort” his ToDo/Task lists
User can use auto rescheduling if resources are unavailable or a time shift is required
Some Ideas related to Project Management:
1. Introduce "Page Type Selector": Start as Note -> if required switch to -> Task -> on completion switch to -> wiki (for documentation.
2. Merge "All" Editable Content Containers to a single Base Class. For Articles only derive/add functionaliti from eg. Wiki. (larger Project).
3. Status Bar: Shows Project Mates Online Status if logged into Project Site only if they working on related content Avatar
4. When "hovering" a tasks representation in a eg. SwimLane Graph a pop up shows some options such as modify start-end, when double click the related objects opens up for editing.
5. Dependency Check and Automatic Reordering of Tasks
Input From A Project Manager
Please do not try to repeat any existing project management tool. - Recording/capturing of ToDo's * Who (1 responsible person/owner) * based on talking with /required initiated by * What, a description of the todo * Duration * start * end * Due date / deadline * status (like pending open closed) * time left for completion No cost calculation - no duration of work ??? (carsten I do not understand this -> "No duration" but "time left..." - Linking of ToDo's * prerequests /preconditions * have to be worked on parallel to other to do - Visualization * Gantt * Swim Lane * To Do List * Netzplan -> carsten translates this to: Precedence Diagram Method - Needs * Simple User Interface (apple like) * automatic linking of team members via iPhone, Blackberry, Laptop * daily pop-up of todo's incl. the remaining work-time, status, parent subject (standard order criteria), Warnings based on project owners preferences * direct access of project plan regardless of place via www to enable team members to update todo's or add things to the plan (device independent!) * Message for Project Plan Owner on any change/update/addition in case of dependencies also sending messages to child activities. * dedicated sending of ToDo's or parts of those from "office" to the devices of the projectmember * via mail, sms, mms, etc. * sync of devices such as wepad, ipad, laptop * conversion of ToDo's to excel
Job publisher & promoter
User can choose to post jobs when connected to a facebook group or other networks like eg. vworker.com
TimeCard: User can have a logging of time spend on a project. TimeCards are bound to Avartars
Weighted Rating: beside readily defined attributes it incorporates
TimeCard based Score tuning (less time higher value closer to estimation better value if not slower then others estimations)
;){kind=link}
;){kind=link}
;){kind=link}
;){kind=link}