Archive

JUN

Book Review: Strategy and Business Process Management by Carl Lehmann

26 JUN 2012 | Posted in BPR, business process improvement, business process management, business strategy, CMMI | Author Alex McLachlan

Strategy and Business Process Management: Techniques for Improving Execution, Adaptability, and Consistency

by Carl F. Lehmann

This is a very useful resource if you are interested in continuous process improvement and ensuring that your processes support your business strategy. It is probably most applicable to medium and large organisations of a size and maturity to adopt approaches such as Six Sigma or CMMI (Capability Maturity Model Integration).

JUN

Enterprise Architecture for Business Agility

20 JUN 2012 | Posted in agility, CMS, CRM, enterprise architecture, IT | Author Alex McLachlan

Your enterprise architecture needs to support business agility to ensure your competitive position in today's market. Building on some of the themes from my last blog post on IT platforms and business agility, enterprise architecture is a cornerstone of your organisation's ability to run its business, react to market changes and implement change.

JUN

Collaboration tools and update from major change programme

06 JUN 2012 | Posted in Basecamp, collaboration, complexity, CRM, Microsoft Dynamics CRM, programme management, project management, Smartsheet | Author Anthony Flack

Back in February I posted that I was making use of Smartsheet to support a major change programme, in particular between suppliers, whilst at the same time the newly recruited IT Director was championing the internal use of Basecamp internally.

I promised to provide regular updates, so here is the first one all be it a little later than planned!

JUN

Database Reset Options for Test Automation

06 JUN 2012 | Posted in database test automation, testing | Author Brett Delle Grazie |

4 Comments

Some of our clients have legacy systems where the most effective test strategy is to use scenarios in the database. A key challenge when automating these tests is finding a mechanism to reset the database back to its pre-test state.

An additional consideration is the potential use of multiple reset points, for example:

JUN

Selling the Cost of Change

06 JUN 2012 | Posted in agile planning, change, contingency | Author Stan Wade

So we all agree that projects should expect a significant amount of change. Agile projects are geared to deal with change in an inexpensive way. That’s all great but there still needs to be a mechanism in play to pay for the change, inexpensive or not. That’s simple you say, that’s just contingency. Well it is, but if we use the word contingency then to some ears we are saying ‘just in case money’. But we have already agreed that change is inevitable, so it’s certainly not just in case, it’s going to be needed.

Archive - June 2012