Harrington Web

I-Team vs We-Team

Wednesday, May 11, 2016
Agile Agile Agile....  The loudest buzzword of many I get to hear lately.  Even though we hear it does it actually sink in to our everyday practices.  So many seem to know the Agile Manifesto to heart, and also the 12 principles.  What is interesting to me in working in some of the teams is that even though we call our team an agile team, it still acts like the old waterfall project work.

I could spell out many reasons why I see conflicts that inject a lot of churn within the team.  However the biggest and I believe root cause is the word TEAM itself.   For instance within your own group have you ever said or heard something like, "we all should be responsible for the outcome"?  Then when someone is asked to do something a little outside their comfort zone they get mad or offensive and say "That is not my job", or "I do not feel qualified to do that."

This is what I like to call the I-Team.  Or Individual Team.  In General these people can come from an array of places, but their primary focus is on either their specialized role, or they just do not want to expand their horizon of knowledge any.

The opposite of this would be what I call the We-Team.  This is the complete reversal in which a person can still be specialized in a particular area, like developer or qa, yet if the need arises they could without asking jump in a fill the role.  They may also not be fully trained at the role, but they would know how and where to get the necessary information to help complete the needs of the team.

Where do you sit within your team, and how does that coincide with agility. Back to Agile big 4.
  1. Individuals and interactions over processes and tools
  2. Working software over comprehensive documentation
  3. Customer collaboration over contract negotiation
  4. Responding to change over following a plan

Individuals and interactions over processes and tools.  Imagine you are part of a team that has many members in the I-Team environment.  You may have certain timelines and processes so that each role can work on a particular assignment.  For example.  Developer may need 2 days to work on a story, but then because you are an I-Team QA will also need a day to do their work.  Sounds great right?  As it states individuals.  But what we are missing is the interactions.  That same model but it is a We-Team.  Developer and QA can pick up a card together and work through it.  Though it still might be the same amount of time to work on the card, they can do so in parallel, and also have a quicker feedback loop.  You may be asking what do you mean about feedback loop.

In the first example of I-Team this was really a happy path.  Meaning the developer is super awesome and can code every time without creating bugs.  I really want to work here by the way....  But that is not the case we live in the real world.  So lets say qa finds a bug.  Well now it has to go back to the Developer and within the sprint dev and qa will keep passing the buck back and forth until it is satisfactory.

Now you may be thinking whooopppeeee.  You would still have to pass it back and forth working on the card at the same time.  Guess what you are right.  But here is one of the benefits of the We-Team.  Both individuals are focused on the same thing.  If you are working on a story synchronously then you can reduce the feedback time, and also keep you mind on the goal.  When you are the I-Team once you pass the buck you are now moving on to the next thing in your queue.  This can lead to a very distracted validation of your new development.

Working software over comprehensive documentation.  Come on man there is no mention of people here.  Well... Your right about no mention however remember the first principle.  Process and tools.  Having the I-Team in place means you will need more rules, process and documentation of contracts so that everyone has a level playing field and expectations drawn out so everyone has nice neat lines.  To be honest the more documentation I have to keep up with the more I get annoyed.  Even more so than that how many people want to take the time to remember 500 rules of how to get something done.  Many people have trouble remembering these 4 main principles of Agile.

Customer collaboration over contract negotiation.  To me a customer is whomever you will be delivering something too.  It can be an employee or someone who is actually paying for the item.  In a team though a customer is also your other teammates. Remember from the manifesto that we value the things on the left over those on the right.  In the I-Team mentality we now have to keep up with this large set of rules and responsibilities that each role will complete.  The more rules and contracts you have the more you have to spend time maintaining those rules versus working on actual value add.  On the We-Team, we know that our responsibilities are working together and collaborating not only among out trade but with actual paying consumers as well.

Responding to change over following a plan.  The last and final section of my rant.   Responding to change.  This is such a big topic that even a small paragraph doesn't do justice.   There are long books and tons of topics on change alone.  If you work in a project with lots of different types of customers, you will see lots of change.  Change can be very good, and one of the benefits to making an agile team is allowing the team to morph and re-mold to a new shape if needed to complete the goal.  Think again about someone on the I-Team.  On an I-Team certain members may get the communication and do their part.  Awesome job done.  However just because 1 part of the team is complete doesn't mean that everything needed for the story is done.  Maybe there is some integration or testing dependencies?  Its really hard to tell when it is on the I-Team because you can never really be sure who is in the loop of what is going on.  We-Team imagine that idea of people working together and maybe even pairing on developing a story.  It would be much easier to keep everyone in the loop.  Now it also says over following a plan.  Some people and especially those who like the I-Team really love completely worked out plans.  However when then they go bad or need to be completely changed, they get offensive.  When they become offensive all of a sudden there are meetings.  Then more meetings to talk about meetings and trying to cool everyone down.  Have you been there done that?  What just happened?  Oh we got off topic and talked about how everyone feels and not about solving the issue on the change that is happening and keeping our customer happy.

Thanks for taking the time to read my rant.  But I encourage you to think about it are you on the We-Team or I-Team.  Are you willing to step outside your little cube and see what other team members are doing and how you can help?  My boss has a great phrase of "What can you do to move the needle?"  So engage with your team and see what you can do to move the needle.

Juniper VPN using OpenConnect

Wednesday, April 20, 2016

Finally there is a tool worth using for vpn besides the default from Juniper that works on Linux. Its rather quick to get started.

Install Arch

$ pacman -S openconnect

Install Ubuntu

$ apt-get install openconnect

Install Fedora/RedHat

$ dnf install openconnect

or this if you have older Fedora/RedHat

$ yum install openconnect

Once you have it installed you may need to reboot. This will allow proper access to /dev/net/tun

Run it

$ openconnect --juniper vpn.domain.com

I'll Fly Away - Lyrics and Chords

Wednesday, March 30, 2016


G Some glad morning when this life is o'er, C I'll fly away

GTo a home on God's celestial shore, C I'll fly away


G I'll fly away, O glory, C I'll fly away G In the morning.

G When I die, E hallelujah, by and by G I'll D I'll fly away


G When the shadows of this life have grown, C I'll fly away

G Like a bird from prison bars has flown, C I'll fly away


G Just a few more weary days, and then, C I'll fly away

GTo a land where joys shall never end, C I'll fly away

Calculate your Macronutrients

Tuesday, March 29, 2016

Macronutrient Calculator

All Weights are in grams.
Protein Carb Fat

Waiting for asynchronous calls in Protractor

Tuesday, March 22, 2016

Sometimes when dealing with tests the asynchronous objects are just a little ugly and hard to read. For instance if you have 3 buttons on a page and you wanted to make sure that all 3 were the same size. You would have to wrap all 3 elements together with a promise all. I am sure you can imagine the fun. With ES6 there is as new option to await asynchronous calls.

First you will need to add some libraries to your project

$ npm install babel-core babel-plugin-transform-async-to-generator

Then you will need to add some information to the protractor-conf.js

//You can add this either at the top of the file or you can put it within your onPrepare section.

Now create a .bashrc file

  "plugins": ["transform-async-to-generator"]

Now the fun part accessing the power of async and await. On you it statement we need to add an async.

it('should give us text', async function() {...

or like this if your are more current in syntax

it('should give us text', async() => {...

Now lets say you want to write the text to the console within your test.

it('should give us text', async() => {
  let someTxt = await $('.someElement').getText();
It is that simple. To compare the same using a then.
it('should give us text', () => {
    .then((val) => { console.log(val) });
If you wanna see more Protractor help ideas you can checkout the book I am working on. Protractor: Learn Testing Angular

Query Selector: How to Or Selection

Thursday, March 17, 2016

This is probably an odd topic, however I was recently asked how could one select between 2 possible elements on a browser using Protractor. If you are unfamiliar with Protractor it is a testing tool for AngularJS applications. To start lets show a code example of what we are looking at.

    <div id='ex1'>
      <!-- some code here -->
    <div id='ex2'>
      <!-- some code here -->

Notice from the code that we have 2 divs with id's ex1 and ex2. Now depending on the code you ex1 or ex2 can be hidden. Lets say hypothetically they both do the exact same thing and you just want to click which ever one happens to be available. At the same time you also don't want to add expensive checks for isPresent or waits. To get around this you can do the following with the by.css query selector.

$('[id="ex1"], [id="ex2"]')

Did you know that this same query selector will also work within JQuery, and the DevTools Console on your browser? Give it a try on this page.

  1. Goto your DevTools Console in Browser
  2. Type: $('[id="ex1"], [id="ex2"]')
  3. Hit Enter

Add Search to Blogger

Wednesday, March 16, 2016

Simple way to add a search to your blog on Blogger.

  • Click -> Layout
  • Click -> Add a Gadget
  • Click -> HTML/Javascript
  • Paste -> Code below
<form action="/search" id="searchthis" method="get" style="display: inline;">
  <input id="search-box" name="q" size="30" style="height: 30px;" type="text" />
  <input id="search-btn" type="submit" value="Search" />