Software Archictecture, Development, Agile Methods and the Intersection of People Process and Technology
Icons – The Standard Way There are so many little details that a software developer must take care of before publishing an application. One of the most time-consuming is the… Continue Reading
The solution to the lack of a round button in Xamarin is a pretty simple one.
Occam’s Razor is a principle of simplicity that eliminates assumptions in support of a conclusion. The principle is valuable in virtually every aspect of life, but it essential to the success of software projects – in particular large complex ones. One of the guiding principles of Agile Methods it that we focus most on the things that provided the greatest value and Occam’s Razor is a valuable tool that helps maintain that focus.
Are We There Yet? Are we there yet? – Donkey from Shrek 2 If you are a parent with kids any older than three or four years of age you’ve… Continue Reading
A Simple Way to Calculate the Velocity of Your Agile Teams and Projects Whenever the work is itself light, it becomes necessary, in order to economize time, to increase the… Continue Reading
Over the years that I’ve been leading software development projects, I’ve used a number of methods including comparison of projects of similar size and complexity, Microsoft Project, Function Point Analysis or even simply guessing. There have been a few other trendy and perhaps oddball approaches thrown in for good measure. Curiously, regardless of method, the results have tended to be pretty much the same. There has, however, been one exception. I’ve gotten noticeably better results with Agile methods using Agile Planning Poker.
Wrong Way – Go Back (flickr – naz’s stuff) The best we can do is size up the chances, calculate the risks involved, estimate our ability to deal with them,… Continue Reading
In many organizations, there are monthly or quarterly reviews of a portfolio or program by senior management to ascertain the progress. Risk assessment is an important facet of project management, and assessing and reporting on the Risks of projects is thus an essential part of this regular review.
(flickr: Sven Hein) This report, by its very length, defends itself against the risk of being read. (Winston Churchill) Background In my post on Agile Project Charters I outlined the… Continue Reading
All software has defects of some sort – we know that. If left unresolved, some defects can have cataclysmic consequences while others are so minor that they go unnoticed by… Continue Reading