In his recent blog posting “Theory of Constraints and Software Engineering” Steve Tendon addresses why throughput accounting should be preferred over cost accounting in software development organizations. He also provides a simple model for throughput accounting that is applicable to software engineering.
Distributing the right applications and links to a user’s computer has always been a challenge. Login scripts tend to be fragile and tools that automatically install applications are often difficult to use. The increased use of personally owned computers and devices further complicates the story. Microsoft is attempting to fix both issues with Windows 8 and the Self-Service Portal.
A recent Forrester report gives evidence to the advance of agility into the business world. This article reviews this trend and some of its potential implications.
Is the Lean Startup movement another fad or a real source of value creation? The implications of the latter are extreme. If Lean Startup is a real way to achieve consistent success in new ventures then Eric Ries may have cracked the code toward persistent venture success and ultimately: wealth creation.
Historically, some product owners have prioritized backlogs by making pairwise comparison of projected economic return between two items in isolation. Successful Agile teams often take a holistic approach, accounting for risk, dependencies, and the complex interplay among and across backlog items.
Tony Wong, a project management blackbelt, enumerates some practical points on individual procutivity. This article wonders how well these apply to software development and contrasts his list with that of other lists.
Business-IT alignment, now part of mainstream EA, is increasingly viewed as an unnecessary overhead in a world where IT is a core business entity in the enterprise. Anirban Ray proposes a model driven approach to creating a SOE which makes a core assumption that IT is an integral part of the business which leads to business focused service offerings.
Patents are quite often in the news these days, most notably the ones related to smart phone vendors like HTC, Samsung, Google and Apple. This also holds for the rather emotional and controversial discussion about software patents which some consider as a means to ensure innovation and others as a kind of weapon. Do software patents cause more harm than good, or vice versa?
IBM's IMPACT 11 conference is underway this week hosting more than 8,000 business and IT leaders representing 60 countries, gathered to learn discuss how to "work smarter for better business outcomes". During the 4 day event, IBM revolves their unveiling of many new tools, products, solutions, and ideas around the one key message of enabling "Business Agility".
Using business architecture to improve project life cycles and applying a standard Enterprise Architecture methodology can be the drivers to add business value in organizations. Richard Reese, VP of Enterprise Architecture at Discover Financial Services, recently spoke at Troux Worldwide Conference about driving business value through EA initiatives.
The Chief Financial Officer is responsible for financial planning, financial reporting, financial analysis and managing financial risks. What would be a better language than finance to explain the benefits of Agile to a CFO?
The International Institute of Business Analysis announced the release of a first draft of the Introduction for the Agile Extension to the Business Analysis Body of Knowledge at Agile 2010 today. They are looking for participation and feedback from Agile practitioners and business analysis professionals.
Much of the generally accepted agile literature will advise you that the best way to capture your user's needs is through examples encoded into automated tests - "automated acceptance tests". Thought-leader Jim Shore says maybe not, while others still challenge him.
UX specialist Anthony Colfelt presents a case for how agile, alone, might not be sufficient and a thorough and engaging look into how User-Centered Design can, and should, be merged with it.
The traditional agile approach to prioritization is that user stories of higher business value should be implemented before ones of lower business value. The concept is simple, but implementing it well relies on having a mechanism to assess business value. Pascal Van Cauwenberghe has recently described an approach to defining business value, called "Business Value Modeling", which may help.