Bindings, Platforms, and Innovation
This presentation focuses on the Internet and separating myth from fact, history from the future, and the mundane from the imaginative. Bob Frankston presents a vision of what could and should be.
Tracking change and innovation in the enterprise software development community
Posted by Mark Levison on Mar 25, 2008 12:10 AM
In a recent AgileJournal article, Doug Shimp, Managing Partner with 3Back and Samall Hazziez, Senior Managing Partner for the Preferred Professionals Business Group, have written about what it takes to enable high-performing "Well Formed Teams" to thrive.
The authors have observed a number of characteristics that enable Well Formed Teams:
However on their own, the principles and practices may burden a team with too much process and information. Instead the authors recommend we focus on what makes teams thrive. In their experience these can be broken down into "3+2".
Let the product lead - always pay attention to the needs of the product. Any time the team considers adopting a new practice or idea ask the question how does this serve the needs of the product.
One bite at a time - Each item of work should be broken up into small enough pieces to eat. Most of us bite of larger chunks than we can chew. Breaking tasks down into smaller parts means that we can get them done in smaller timeboxed cycles.
Keep it visible - one of the most obvious principles it is rarely done well. When we cannot see what our team mates are working on, we cannot see where to apply our own efforts. The result we struggle. With increased visibility we increase the chances that other team members will step in with useful ideas that help solve our problems.
Conversation and Structure - these are used to balance the three principles above. "The conversation requires enough structure from an established protocol so that we can communicate effectively. … The conversation is necessary for humans to establish rapport so that we can create, contribute and share deep meaningful understanding."
How can you tell if you have a well formed team? In the opinion of the authors they exhibit some of these characteristics:
Well Formed Teams are valuable to the business because they're nimble and able to adapt to the constantly changing business landscape.
Give-away eBook – Confessions of an IT Manager
Ebook: Scaling Agile with C/ALM
Ensuring Code Quality in Multi-threaded Applications
This presentation focuses on the Internet and separating myth from fact, history from the future, and the mundane from the imaginative. Bob Frankston presents a vision of what could and should be.
This article explores the use of JBoss and jBPM to implement design solutions that effectively address the issue of orchestrating long running activities.
This presentation covers the use of graph databases as an optimal solution for data that is difficult to fit in static tables, rapidly evolving data or data that has a lot of optional attributes.
This session introduces Real Options and shows how it can help in running your project. Real Options is a decision-making process that can be used to manage risk.
This article discusses the use of bindings on services and references (including the instance of non-configured bindings) as the means to implement SCA communications in a Web and SOA environment.
After a short introduction to DSLs, Scott Davis plays with the keyboard showing how to approach the creation of a DSL by typing working snippets of Groovy code that get executed.
IBM Rational and InfoQ present, Scaling Agile with C/ALM, an eBook showing organizations how to become “finely tuned software delivery machines” by enabling team integration and scaling.
Amanda Laucher presents a real life enterprise application written in F#. She shows actual code snippets, explaining design decisions and suggesting how to use some of the F# constructs.
No comments
Watch Thread Reply