Comments, Code and Qt. Some words about the wonderful world of software engineering


Non-sterile Agile: Comments on “Handling Bugs in an Agile Context”

Posted by kypeli

In my earlier post I already wrote about experiences with agile development. I call these posts "non-sterile agile" because I feel that once agile principles are let loose into the corporate world, agile development changes its nature. I stumbled upon an interesting article by Elisabeth Hendrickson about bugs in agile development. In her article, Hendrickson talks about bug triaging in agile context. It's an interesting read and I agree with her - but only from an agile theoretical point of view. In agile context, it all makes sense that we don't have bugs (or we don't call the issues we observe as bugs at least). Normally we call software defects bugs, but in agile development we don't have bugs because we only create done backlog items. If an item has a bug in it, it will not be called done. Simple - in theory.

Technorati Tags: , , , , ,


Non-sterile Agile: Distributed teams

Posted by kypeli

I call this post non-sterile agile because I feel that once agile principles are let loose into the corporate world agile development changes its nature and face. In this (and hopefully upcoming posts) I will try to go through some of the ideas and experiences I have about agile development in the corporate world. Agile development embraces communication over written documents. This we learn already from the agile manifest. Good communication is best achieved by talking to each other. Then you can really describe the problem. You can ask direct questions or even draw something on a whiteboard to make things really clear. If all relevant people sit next to each other working on the same project, there is no need for design documents, architecture descriptions, UML diagrams and such when you can go and ask the person next to your seat if something is unclear. Likewise you wouldn't not need send emails and wait for replies which will only hold you back while you wait for the answer.

Technorati Tags: , , , ,


My Master’s Thesis

Posted by kypeli

Master's Thesis Originally uploaded by Kypeli
One final time. This time with covers and all 🙂 P.S. get it here:

Technorati Tags: ,


Thesis: Quantitative Approach for Lightweight Agile Process Assessment

Posted by kypeli

Yes, I have finally finished my Master's Thesis. And I must stress, finally. Some spell checking might still occur and I will print it next week. But I am quite pleased with what I current have. I am more than happy to receive any feedback and comments on my theses! My thesis is about about our experiences at Plenware Oy on how to assess the agility of a process in a lightweight fashion, but still to be accurate and to support the Software Process Improvement (SPI) initiative. We came up with the idea that the assessment could be a set of predefined questions that could be easily answered by taking process metrics from a project management tool. The answers would be compared against reference answers and points would be given based on the assessment. Finally, a weighted sum gives the agility of the process. The same approach could be implemented for other assessments, but our goal was to assess the agility of the process. The processes were in a transition phase to go towards agility and it was important to be able to measure the agility in a lightweight fashion. I express my deepest sense of gratitude to my supervisor PhD Luka Milovanov at Plenware Oy for assisting in writing of this thesis. Here's the abstract:
One focus in software development is to achieve high quality without loss of agility in the development process. In software engineering an agile development process is able to react to frequently changing customer requirements and also able to develop the software in small well tested increments. This is not an easy thing to do and will not emerge on its own, but requires well optimized and continuously improved software development processes. The quality of a process can be assessed by some external audits but they usually are heavyweight and costly processes. To measure the quality and follow the improvements in a process a lightweight assessment method is desired. In this thesis I will look at Software Process Improvement (SPI) paradigm from the perspective of both Reference Process Models and the Experience Factory (EF) infrastructure. Then, I will present a quantitative lightweight process assessment method for agile projects. This method allows the assessment of a process in less than two hours. The method yields numeric results of the agility of a process in a lightweight fashion. I will conclude by stating that the work done in this thesis is only indicative of this kind of assessment for agile processes there is a need for further research. The results presented here result from the current need in Plenware Oy related to SPI evolvement.
Here's the PDF: Quantitative Approach for Lightweight Agile Process Assessment

Technorati Tags: ,