Test Retreat

Welcome to the homepage of Kris Corbus

Archive for the tag “agile”

Where Are We Going?

Some use Twitter to keep up with latest news, I like to read newsletters. Already long time ago I subscribed to several local testing & co newsletters. Here are two conference posts who made me think lately. Is this where we are heading?

The first conference is/was Swiss Requirements Day.

It was huge surprise to receive the last newsletter with subject “Rest in Peace Swiss Requirements Day” with the message:

“Dear Swiss Requirements Community
In acknowledgement of the changing environment, the Swiss Requirements Day lays itself to rest.
Digitalisation marches swiftly on; delivery times are getting shorter and shorter; agile is on everyone’s mind. There is no time for a thorough analysis and documentation of requirements. Or is there? What preparatory activities are needed before coding can begin?
Design Thinking, Human-Centered Design, UX, Business Analysis, Systems Engineering and yes, also Requirements Engineering, are central elements.
Against this changing backdrop, we say goodbye to Swiss Requirements Day and proudly welcome its successor, the Upfront Thinking conference.”

OK, they are kind of closing one and opening another conference… if it would be just a change of name, than why so alarming sentence: “There is no time for a thorough analysis and documentation of requirements.”? Is this agile? Do we really want to have software which is made without thorough analysis?

The second conference is Topconf Linz 2016, will be held on February 1-3, 2016.  If you wonder what is Topconf – here is what they say about themself:

“Topconf Software Conferences are premier international software conference designed for Developers, Product owners / managers, Architects, Project Managers, Methods- and Process-Experts.
Our speakers are authors, experts and practitioners across various areas of software development.”

I find it quite interesting – various areas of software development and all kind of job titles but nothing related to testing.

Any way – my attention got something else – Talk by Louise Elliott Punishment Driven Development. She got me! I really want to go to the conference and to see how she will put that all together – punishment, guilt and agile. Interesting that this talk is on New Ways To Manage track.

What About Agile

I am big fan of Dilbert.

I like how in few pictures he captures the essence of software development, but in the same time I am ashamed, because I am part of it.

My trouble lately (several years to be specific) is agile. I have no trouble with methodology itself, but the way it is used. I struggled around till I saw this:

I did small research – talked to people and by the way asked about their info source on the subject. Some of business people really said that they have no idea what it is, but they learned that that’s the thing what sells. Agile is new sexy!

I start to think, how could I explain in small talk, how I understand agile and why it is worth to get to know more about it. Trade magazines often points out the speed as a key value, but never tells you how to get the speed. By pushing just accelerator you will not make very far on bend and bumpy road.

So let’s go back to the basics. First value on agile manifesto says:

Individuals and interactions over processes and tools

Fifth principle of agile manifesto:

Build projects around motivated individuals.
Give them the environment and support they need,
and trust them to get the job done.

Individuals, motivated individuals… and trust them! How about that?! The trust. Whom do you trust?

I did small survey (that’s the thing I always do if I am on something) and got shocking answers. My responders do not trust their colleagues and will not address the issue, no matter that they agreed that trust among the colleagues is very important.

As more as I think about the trust as much, I think that may be it is the source of my struggle. Current society are so focused on career and success that we forget about individuals and trust at a workspace. This project is just a step to next big thing.

As a tester I wonder quite a lot about things, what I thought is common sense, but turned out that it is just my sense and I have to explain it to others or write a bug report :) . I think that trust among colleagues is nothing agile-unique. And also satisfied customers and working software should not be something extraordinary – isn’t it something “by default”? Why we need manifesto for that? And if someone wrote manifesto for all that, why do we grade it by doing not properly?

Post Navigation