, , , , , , , , ,

Hi all,

Time for part 2 of this short series about Graphic and Design work within Software development.

This post revolves around the little progress we’ve made to reach any kind of headway into getting teams to work to produce functional pieces of work. It certainly would seem that way at first glance, but like so many adoption processes we have made leaps in terms of understanding and reflexion on what it is they do to get results. This brings to mind a great story, “The little engine that could”. The general feeling is one of Reluctance. The immediate stare that you get and question that forms behind it is : “What am I going to do if I don’t work on the whole picture?” The prerogative was to work on everything before anyone could get a sense for what was actually needed. i-knew-couldThe UX people would simply hand down the work to the little people (warning* dramatization) and would simply wait in the wings to either argue the points brought forward by developers or have the sudden urge to rework everything having an impact which could be felt all the way to the Product Owner. As you know, talking about this subject in Part 1 we wish to create a Team who can deliver complete (according to Definition of Done established by that very Team) functional pieces of software. As of now, the reluctance is such that all we hear is “No way I can”. In certain members, which is why I said that we have made great progress, we can hear “I think I can”. For you guys out there having achieved a fair level of success, I work towards “I knew you could” :). Obviously, we want them to gain a sense of greater purpose and work with all the diverse fields of competences to achieve great results. What we have seen rise out of certain teams, especially the ones that can’t navigate the remaining work within their plan, is that it realizes that these members with such a narrow field of competence isn’t helpful. They quickly realize that together as a group, have the ability to come up with great ideas and answer the functional needs of the business. This brings us to the last great improvement that I saw rise from these newly formed Teams and this is the ability for them to be critical with themselves about the work they do. Did seems quite ridiculous at first, though I have to remind everyone that before this time Teams were given work and this work was handed out to individuals which would work in their own little bubble. The behaviour comes from the now newly formed identity which is reinforced at every opportunity that they have to work together. They now see fit to be more critical and not simply take things lightly when the work someone around them does impacts the results.

There is alot of work still to be done and I have no doubt they will achieve greats software together like they imagine they could. We are all capable of change, though not everyone is willing to make the effort. At times it is very conflictual, not only with people around us but rather within us.

Thank you and Scrum on! PS