Softwaredevelopmenttoday.blogspot.com Website Review

just a quick note today to let you know that the call for sessions for scanagile, the agile finland annual conference is open for will also be tracks for those starting up or that have already started but are in the early phases of their agile transformation journey.  the agile finland community is very active and has a long history of agile adoption and promotion. they have some of the most advanced practitioners in the world, so i am really looking forward to see who the scan agile team chooses for the 2015 lineup of the conference!  subscribe and get special features not available on the blog. 340 people follow this blog already!. quite often is: how can we make decisions on what projects we should do next, without considering the estimated time it takes to deliver a. although this is a valid question, i know there are many alternatives to the as*umptions implicit in this question. these alternatives - which i cover in this post - have the side benefit of helping us focus on the most important work to achieve our business goals.. below i list 5 different decision-making strategies (aka decision making models) that can be applied to our software projects without. requiring a long winded, and error prone, estimation process up front. a decision-making strategy is a model, or an approach that helps you make allocation decisions (where to put more effort, or spend more to start must help you achieve business goals that you define for your business. more specifically, a decision-making strategy is an approach to making decisions that follows your existing business strategy. other types of business goals are possible, and it is also possible to mix several goals in one business strategy. different decision-making strategies should be considered for different business goals. the 5 different decision-making strategies listed below include examples of business goals they could help you achieve. but before going further, we must consider one key aspect of