Software Archictecture, Development, Agile Methods and the Intersection of People Process and Technology
Icons – The Standard Way https://material.io/resources/icons/ 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… Continue Reading
Does anyone actually think that a Burn Down Chart contributes one iota to creating Better Software Sooner? In my view, it is one of the most anti-agile things that we can do and it provides absolutely no value to anyone other than perhaps the executive suite so that they can have a nice, warm fuzzy feeling that we have a pretty chart that has a nice slope to it and it looks like the one from last sprint.
The solution to the lack of a round button in Xamarin is a pretty simple one.
What is creativity and why is it important in software development? Here is how to find the creative people you need and help them to be successful in your company
Agile software development places more responsibility on individual programmers to make key decisions. How to recognize, hire and keep the top performers who improve your chances of success.
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