Veel IT organisaties zijn in verandering. Daarbij verandert vaak de manier waarop de werkzaamheden ingericht zijn, en de aansturing en rapportage. Voorbeelden daarvan zijn "Het Nieuwe Werken", Scrum en Agile werkwijzen, tijdelijke samenwerkingsvormen zoals teams en steeds korter durende projecten. In hoeverre zijn de "traditionele" kwaliteitsmethodieken, gebaseerd op ISO, INK, TQM en CMMI nog steeds bruikbaar?
Some companies say that “people are our most important resource”. I’d rather use the term “professionals”, since they are trained, have build up experience and are continuously developing themselves to deliver value for your customers. Question is: Are they empowered to do this in a efficient and effective way? The People-CMM can be used to develop a powerful professional workforce, supporting self-organizing agile teams.
Business needs for process improvement projects are changing. Organizations expect faster results from their process improvement investments; they want their improvement to follow changing business needs and be more engrained in the organization.
Delivering product with the right quality, on time, can be difficult. Testing decisions are crucial to reach this. Are there ways to improve your testing decision capabilities? Yes there are, and they have been used and have shown to be valuable.
Software development teams use the word “customer” a lot. But there are different kinds of customers. Being aware which kind of customer you are talking about can help you to deliver better results to your customers.
One major change in CMMI V1.3 is the addition of agile. Let’s take a look at this, to see how the deploying the CMMI version 1.3 delivers value for Agile organizations and how we can combine agile and CMMI in process improvement.
When I started this website back in july, I mentioned that my main reason to start blogging was to share my experiences.
SPIder, the Dutch Software Process Improvement Network organises a session about software reliability on november 2. Three speakers will give their views on reliability, and discuss with the attendees what can be done to develop reliable software.
A topic that has been fascinating me for a long time is how people take decisions? I have seen many problems with decisions, but there are ways to improve decisions.
Root Cause Analysis (RCA) has been used by many to determine a fault’s first or “root” causes to improve processes. Given the current economic climate, the business case for RCA has become more more explicit then ever!
The customer is considered more and important for software development. Software teams have to delivers products and services that solve the needs of their customers. But understanding what a customer wants isn’t always that easy.
Many people think Quality Assurance (QA) is only testing. This surprises me, after working many years as Quality Manager to prevent defects and improve products.