Project management, product development management or whatever you may choose to call it. It is all about creating the right sets of circumstances to reach your goals together with other people.
Why do, or don’t, organizations adopt agile practices? Vijayasarathy and Turk study this issue in a paper published less than a month ago. They found that perceived norms and training are significant factors in promoting adoption of agile methods. Perceived benefits – such as the fact that TDD really does…
In a recent, well written but smallish study, a team of researchers from Finland have tried to find where KanBan has benefits. In their setup, teams of master students were instructed to use KanBan in their software development projects and then interviewed about their subjective perception of the benefits of…
I spent last Friday in Linköping. It has been almost 12 years since I was there the last time. This time I came for two reasons: Continue reading
When people ask me to explain the difference between agile and waterfall methodology I usually give an analogy based on the construction industry: The Construction Industry as “Waterfall Heaven” Construction Site for The Oaks High School Retford © Copyright B Hilton and licensed for reuse under this Creative Commons…
In my inbox today I found a link to an article about what constitutes success and failure in software development projects from a supplier perspective. While the authors were able to find three project success criteria from their systematic literature review they were unable to find failure criteria… The three…
Here is yet another great installment of the Business 901 podcast. This time on being agile on the enterprise level part 1, part 2. I agree with most of what is said in the podcast, especially that there is no “one size fits all solution“. Different teams have different needs.…
According to this study you should because expert release planning is 40% less efficient than automated planning. However this is only for simulated projects. In their next work the researchers will try the approach on real project data…
In traditional non-agile project a lot of effort is spent in generating documents in order to achieve coordination, collaboration and communication. In agile software development the main artefacts beside the code are the storyboards. So what happens with all that other stuff? Open university research might have the answer in “
Three ‘c’s of agile practice: collaboration, coordination and communication“. I have requested a copy and will give more detail when and if I receive it.
There are three key, recurrent meetings in Agile practice:
Do these meetings contribute to team motivation or de-motivation? According to a recent study “Motivating Agile Teams: A Case Study of Teams in Ireland and Sweden” it depends.
Sorry, but I am not going to pay to read any further than the abstract but if someone will donate a copy to me I promise to write about any other sensational findings in the paper.
[bibtex file=http://www.citeulike.org/bibtex/user/greger/tag/20101119?fieldmap=posted-at:posted-date&clean_urls=0]
The Featured Image is taken from Klean Denmark on Flickr and is used under a CC BY SA 2.0 license. It has been slightly cropped.
