Teams


Caution!

Just blurting out no, no, not on your life, or flying into a rant about the unfairness of a request is not generally a good strategic or safe approach to sorting whether you will do a specific piece of work. Gut feel or seat of the pants answers are rarely career-enhancing, rather answering any question requires preparation and a scalable process. (more…)

Saying no, at least where appropriate, is an important tool to ensure good morale, high productivity and delivering more value.  Just saying “no” is easy, having the statement be safe and make sense requires several prerequisite conditions.   (more…)

Collaboration is no soft toss!

Many people have the idea of the lone innovator or the lone programmer developing solutions based on the wits to the adulation of the business deeply embedded in their subconscious.  These lone wolves don’t collaborate. The picture is wrong. Today’s business environment is fundamentally different. Teams and teams of teams are the problem-solving technique de jour.  Collaboration is an important part of solving business problems in teams. Because collaboration is so important, it is important to consider whether planned meetings, events, and interactions are set up to be collaborative before they occur.  Jonas Bull suggested a modification to the collaboration filter we have been using to evaluate whether an event is collaborative posthumously. Jonas’s suggestions (melded with Stephen Adam’s suggestions) follow below: (more…)

Direct Playback

Subscribe: Apple Podcast
Check out the podcast on Google Play Music
Listen on Spotify!

SPaMCAST 554 features our essay on the misuse of the word ‘collaboration’. Collaboration is a hallmark of agile techniques, but people confuse collaboration with many other forms of interactions. When that happens everyone gets confused and disheartened. In order to stop the cycle, we identify four attributes to help recognize collaboration.

We’ll also hear from Gene Hughson who brings his Form Follows Function Column to the podcast.  In the second part of a three-part series on architects, Gene discusses the role of the solutions architect.  Part One can be found on SPaMCAST 543 – Value Chain, Solution Architects, Essays and Discussions Web Player and Show Notes: http://bit.ly/2L3tLku (more…)

A Panel Discussion - Collaboration?

We recently developed a structure for evaluating whether an activity was collaborative or not.  The four-step evaluation process is important because the same activity is collaborative in one context and overhead in another.  There are four areas of activities in all software development and maintenance organizations (and I do mean ALL) that are sometimes collaboration and sometimes not, but almost always sold as collaboration.  Today we tackle the first two areas. (more…)

A Framework For Collaboration

Collaboration is one of those words that is used way too often and is conflated to cover everything from transactional to shared relationships. In agile, the term collaboration is meant more specifically to mean the scenarios where teams create shared relationships so that they can achieve a common goal that individually would beyond their capabilities. In order not to dilute the power at the core of collaboration it is important to clearly understand behaviors that it are easy to conflate with collaboration.  A high-level filter to determine whether the behavior is collaborative includes the following criteria:   (more…)

Trust?

Trust is the third prerequisite for collaboration. Time and transparency help build a platform on which trust can be established. People do work together with only a modicum of trust.  Little to no trust leads to transactional and short-term interactions which are a pale version of collaboration. Developing trust past the basics of public decorum is essential to working in teams and teams interacting with other teams. There are six key attributes that are prerequisites to trust. At a team level, they are a reflection of how the individuals on the team act. At a team of team level, these attributes attach to teams. The six attributes are: (more…)

Next Page »