My Project for Collaborative Programming

Vision

  • Make programming as easy as writing a Wiki page
  • Allow every user to change the data and the program (restricted only by policy rules)
  • Make heavy use of reused code
  • Provide support for development processes
  • Pf0mp Vision

Example: Task List Example

Principles

  • Every change is automatically versioned and self documented
  • Code and data is interchangeable
  • Data is everything that’s available in memory, on file system or in a database
  • All code fragments are everywhere and every time available
  • Same code (semantics) should exist only once
  • Concurring codes is executed in a Fuzzy way
  • Open interfaces to other systems
  • Implementation is on a central server – no code required on clients
  • Collaborative Programming
  • WikiWords

read more: on MBWiki

My Project for Collaborative Programming

Communities of Practice in Scrum

If you have Scrum on a larger scale in place, you will end up with several cross functional (multi-skilled) teams:

Eg. you will have developers, business analysts, and QA resources in one Scrum team. After a while you’ll need to think about know-how sharing and skill enhancements. I propose to implement communities of practice (CoP, http://en.wikipedia.org/wiki/Community_of_practice) for each skill.

A representative for each skill (horizontal community) is sent to the Scrum of Scrum.

Mirko.

Communities of Practice in Scrum