|
CoMindWork is constantly growing feature-driven application. So, we want to share the current state and prospects of our work with the community.
To describe the functionality of CoMindWork we outline the vectors of development.
One view on the features is mapping onto enterprise ontology:
Activity and Resources (Process)
- 3 CMMI Layers: Process -> Project (customized processes set) -> Ad-Hoc (issue/case tracking for any ad-hoc process). The goal of the system is support for growing through maturity levels.
- Inter-project (enterprise-wide) management: workload balancing, workload conflict resolution. This is essential for running whole organisation, not only one project within company.
EO2: Organization (Internal Net)
- Organizational units and authority (levels of permissions)
- Company workers levels/competences map. Storing this information is essential for managing people more effectively.
EO3: Sales (External Net)
- CRM functionality: clients, billing, leads, prospects
- Supply Chain functionality: vendors, standard products order etc
- Community (eco-system): for open-source, social-commercial network, co-opetition, new biz models of collaboration
EO4: Goals (Conditionals)
- Collection - collect measures:
- Timeline - versioned history of all time-critical artifacts (plates!)
- Logging (of actions, access etc)
- Analysis - visualize results
- Reports and charts
- UI to review details, drill-down reports
- BSC - coming soon, auto-built "SilverBullet score" and similar
Info and Knowledge Sharing
- Wiki: pages, tagging, associations
- Blogging (personal, project and corporate)
- Files Storage (versioned): long-term library, in-progress project artifacts, source code, models
- Unified search (any content-based item: process-items, pages, storage, etc)
- Various helpers: tagging, wysiwyg.
Instant Collaboration
- 'Now online', status, chats, quick notifications
- Phones
- Video collaboration: window to another office
- Desktop sharing and related co-work tools
Integrations and Sub-Systems
- Notifications: emails, RSS, SMS, IMs: "total awareness enablers"
- Incoming email parsing (using email as additional UI)
- Famous or critical products integration: Microsoft Office, accounting software etc
Other Aspects
- Speed and responsiveness of UI (immediate!)
- Global versioning (any time-critical entity is versioned for "time-machine analysis")
- User interface, dashboards and helpfulness (proactive tips, level of user-maturity). Customizable UI.
- Internationalization - multi-language interfaces, time zones etc
- Authentication and authorization (based on org-permissions)
| |
| | | | | |
Another mapping is to common-sense functionality, and relation to other well-known products.
| Features | Famous systems
|
Knowledge Sharing and Collaboration
| | Wiki | Mediawiki (wikipedia), other enterprise Wikis
| | Blog | Wordpress, blogger.com, livejournal
| | Video Meetings, IM, desktop sharing | Webex, miranda
|
Business Processes Automation
| | Ticketing (aka "issue tracking) | Jira, ClearQuest, Kayako
| | Customizable workflows (visual editor) | ClearQuest, Jira. / Kayako has lightweight customization: fields only, no rules or constraints /
| | CRM, SCM, Contact Management | Salesforce, SugarCRM
| | Balanced Scorecards (BSC) - goals, strategy, measures, executive dashboards, customizable reports | QPR7, activestrategy
|
Aspect-like Sub Systems
| | Parser of emails with rules | Kayako
| | Email notifications and RSS | Any blogging software like blogger.com or livejournal.com. Specialized soft like feedburner.com
| | Permissions | Basecamp - easy config of permission for any element, fine-grained permissions.
|
Knowledge Work Helpers
| | Search (fast and handy), searches all types of content items | Ask.com, google-suggest
| | Tags | Any social network. Bookmarking: del.icio.us, digg.com; blogs; cms, wikipedia.org (bad UI); basecamphq
| | Rich Editor (WYSIWIG) | Any CMS - wordpress, famous WYSIWIGs, wikipedia.org - (ultra simple UI)
|
Integrating
| | SVN/CCNET integration | Collabnet
| | Microsoft tools integration (Exchange, Project, Office) | We already have connectors to Microsoft Office tools, and plan to integrate more.
|
Communities
| | Community features ("friend this company"), fast project-team building from legionery (like in football) | Various industry portals, which however work on 1-to-1 basis usually. Multi-player-games.
|
User Interface
| | UI: Widget-like dashboards, ability to customize (layout, size, dragging) | Google dashboard, netvibes
| | UI: Rich Visualization (Flash) - PivotTable, dragable Rich UI | yourminis
| | UI: Unified UI elements: lists (with standard but rich functionality), forms etc | MS Outlook
| | UI: Help, guiding, tips. "User maturity": (UI complexity and features based on selected "maturity level") | We want to create game-like UI to CoMindWork that guides user through learning curve
|
|