Tuesday, August 31, 2004

![]() ![]() Jay Cross
New blog Links & more ![]() ![]() Subscribe to the BlogRecent Photos |
"Thomson NETg and KnowledgeNet are a perfect fit," said Thomas R. Graunke, chief executive officer and co-founder of KnowledgeNet. "Both companies have a long history of improving the effectiveness, accessibility and success of an array of training, development and learning programs. By merging our products, learning philosophies and industry expertise we are creating a compelling combination for all of our existing -- and new -- customers."
The transaction, expected to close later this year, is subject to customary regulatory and closing conditions, including the expiration of the waiting period under the Hart-Scott-Rodino Antitrust Improvements Act of 1976, as amended.
My congratulations to Tom Graunke and the folks in Phoenix. I remember when KnowledgeNet was a pup. When they gave the remote demo (Placeware, if I remember correctly) that landed the Cisco account, I was in the next room working on another project. As they walked out of the room, the Cisco folks appeared quite impressed. The "no travel costs" argument was important back then.
"The Thomson Corporation (Thomson) is a global provider integrated information solutions to business and professional customers. The Company generates revenues by supplying its customers with business-critical information from multiple Thomson and third-party databases, and further enhances the value of that information with analysis, insight and commentary. To enhance the speed and accessibility of information, Thomson increasingly delivers information and services electronically."
KnowledgeNet will be merged into NETg. Joe Dougherty, current president of Thomson NETg, will lead the combined business.
Objective | Subjective |
Content | Context |
Central | Distributed |
Description | Prescription |
Reaction | Proaction |
Predict | Self-fulfilling prophesy |
Static | Dynamic |
Solutions | Problems |
Value:
replicability | Value:
Appropriateness |
Efficiency | Efficacy |
Manifesto for Agile Software Development
We are uncovering better ways of developing
software by doing it and helping others do it.
Through this work we have come to value:
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
That is, while there is value in the items on
the right, we value the items on the left more.
"Software development is a series of resource-limited, goal-directed cooperative games of invention and communication. The primary goal of each game is the production and deployment of a software system; the residue of the game is a set of markers to assist the players of the next game. People use markers and props to remind, inspire and inform each other in getting to the next move in the game. The next game is an alteration of the system or the creation of a neighboring system. Each game therefore has as a secondary goal to create an advantageous position for the next game. Since each game is resource-limited, the primary and secondary goals compete for resources.A move isn't right or wrong; it's better or worse.
The software development game is played in a milieu of many other games, personal and organizational, simultaneous and criss-crossing in time and purpose. One of the other games being played is to be able to play the next round of this game, i.e. the next game. That is, having once deployed a software system, to set up for changing, replacing, augmenting or complementing it.
Therefore, there is a residue to the game: a set of markers that will inform and remind the players of the next game. The players of the next game will know a different amount from the players of this game, and so what counts as "sufficient" for the next team is different from what counted as "sufficient" for this team."
"The three outdated and inefficient process conventions I tend to watch and replace areCockburn has a lot more where these came from. Take a look in the Agile Toolbox.
- Get the requirements right before starting design and get the design right before starting coding.
- Writing things down in detail is better than sketching them and then talking about them.
- People work better in private offices.
Replace those with:
- Overlap activities in concurrent development. Get just enough requirements to get started on the design (where just enough varies from project to project), use early coding to get valuable feedback on the properties of the design.
- Capture documentation mostly in quick and rough form and support the documentation with good conversation.
- Get the people out of their offices into a shared work space."
About Us | Contact Us | Home | |