I propose a paradigm shift in developing software to deliver business value.
For a team to satisfy a business need,
it is not the amount of work that defines the time needed,
it is the available time that defines the amount of work that can be done.
The deadline is part of the need, and not the result of estimation or planning techniques.
With the deadline being part of the need, the Team and the Product Owner have a shared budget ( = number of Sprints ) to realize the Vision.
Instead of using Poker to give insight in the estimated time of delivery, let’s create a Market Place where Product Owner and Team ‘negotiate’ on the complexity of each story.
Filed under Agile, Ideas, Project Management, Requirements Management, Uncategorized | 10 Comments »
What electronics tools exist to electronically master the agile process like Scrum, Kanban, and others?
Since this question surfaces every now and then, answers collect here (in alphabetical order).
Got more?
Contributors:
Filed under Agile, kanban, Project Management, Scrum, Scrum | 12 Comments »
Filed under Agile, Project Management | No Comments »
Sharing knowledge is one of our core values and as lot’s of research confirms knowledge transfer is best done between peers. We have a great knowledge sharing platform at Xebia through bi-weekly evening sessions, where we do some experimental coding and some presentations. Once in a while we take it to the max and organise a tech rally. One of those happened last Friday and it was a total blast. I’ll give you some of the highlights. More detailed posts on the technical details will follow and I’ll update the list below as they do:
Tags: hyperproductivity, jquery, knowlege-exchange, mongodb, posterous, Spring
Filed under Fun, General, NoSQL, Project Management | 3 Comments »
In this blog, I make a case for what I think is the next step in the evolution of Agile project management. The focus of project management used to be based on managing Tasks that people perform to deliver a piece of software. Agile project management shifted focus to managing the delivery of Features. I believe that the time is ripe for the Agile community to take the next step: move towards Value driven project management.
(more…)
Tags: Agile
Filed under Agile, Project Management | 18 Comments »
In this episode of the middleware pitfalls top-10 we want to discuss the merits of a clean and standardized set of (test) environments. Some refer to such a set as DTAP, an acronym for Development, Test, Acceptance-test (or pre-production) and Production. From here on the text contains capitals to indicate an environment. Basically the situation is like testing itself: you will never get it 100% right, but it will help you a lot if you invest in a sound, maintainable DTAP.
Tags: DTAP, omgevingsverschillen, OTAP
Filed under Middleware, Project Management, Testing | No Comments »
Development teams or even development organizations, are not always the well balanced, smooth operations we’d like them to be. In our software quality audit practice we have had the privilege to investigate many different types of organizations and found many different ways quality and productivity can suffer from a problem known as the Prima Donna Syndrome: a single individual exercises a disproportionate influence on the team causing problems like stagnation and unnecessary complexity.
(more…)
Filed under Agile, General, Project Management | 4 Comments »
My colleague Age pointed me at a blog post by Uncle Bob about a presentation where a Mr. Josuttis presented the inevitability of crappy code because “businesses will do whatever it takes to cut costs and increase revenue, and therefore businesses will drive software quality inexorably downward”. Uncle Bob proceeds to go against that argument, but I find it to be a technocratic (DSLs and produce better code) and ultimately unsatisfying answer. My answer to the problem?
Face reality, grow up.
Filed under Agile, General, Project Management, Scrum | 8 Comments »
This recipe describes the process of baking marvellous, slightly burned decisions. If you’re looking for the well-done version of decisions, I would suggest altering this recipe by adding things like “necessity”, “timing”, “context” and “feeling” or taking another recipe on the subject.
(more…)
Filed under General, Project Management | 2 Comments »
You may land up in situations when a project is almost stable. For developers handling issues and enhancements for the project, the work available is not sufficient. So, when team is comfortable with the project and it’s already stabilized, team can start handling another project at the same time. It’s good for the people working in these projects from learning perspective. They are exposed to multiple technology stacks, problems and functionality. At the same time, it works well for an organization in general.
(more…)
Filed under Agile, Project Management, Scrum | 4 Comments »