Wednesday, July 1, 2009

Team 2.0

My quest for knowledge has pushed me to the extent that I started feeling insecure for any activity happening without getting updates. This is even more if it is my area of interest Business and Technology.

Example: Powerbuilder migration proposal needs some data. Legacy modernization group would like to know the research done by B&A team for them to leverage the efforts. Tools group would also be interested for any tools that would help migration. Similarly Pain points group would like to the business case build by team to showcase pain points of any Powerbuilder application.

Same tasks numerous groups interests involved. Think of the collaboration needs for this activity. Should only one or few core team member need to know all these activities to direct teams for co-ordination?

Listed are the high level actors

  • HIPOS groups are formed each targeted to address different areas. (9+)
  • Leads trying to get some info. (No of Projects)
  • Managers for data for various reasons (10+)
  • Team wish know recent happening and probably the work done by HIPOS would help them reduce rework in learning from scratch.

It was suggested that for any problem put forth you, we need to start with “If I had unlimited time and resources, and knew I could not fail, what would I choose to do?”.

Write Blogs: Every one part of HIPOS group would blog at regular intervals on their activities around these groups.

TAG Blogs: Each blog would have base category (tag?) mapped to their group. Author could also tag their content optionally; others could also tag the content (Folksonomy).

Even use for auto tag generation (say tags created by users are scanned through blog’s content to generate tags , even when not specified)

TAG CLOUD: Generate Tag cloud and help the users trying to find specific content easily. Provide search facility as well, as Tag cloud could hold limited tags.

Advantages

  • Every one is trained to articulate their learning
  • Hold sense of contribution and accountability by each
  • Track the performance (transparency)
  • Access to all interested
  • Leverage WEB 2.0 features yet to be realized.


Till this could be implemented could we have this implemented in available Sharepoint as communities ?


1 comment:

  1. What happened to the HIPOS ? Though there are many ideas in the minds of us, nothing is getting shaped.

    ReplyDelete