Archive for the ‘process’ Category
Thursday, April 22nd, 2010
Hard work does not pay off. At least not if your ultimate goal is to improve at what you do. And not if what you do is quality product development.
In that case you need to build in slack for learning into the system. You want everyone to have time for ...
Posted in Monday School, process, teamwork | No Comments »
Thursday, February 11th, 2010
After listening to Olve Maudal at the Lean Meetup in Oslo yesterday, and after reading some of his tweets today (@olvemaudal) I realized that we never informed our readers that we are not doing Scrum anymore. I don't think we have for 9 months or more. We ...
Posted in process, teamwork | 22 Comments »
Thursday, January 21st, 2010
Scenario: A customer has a problem with your software. His questions makes you think and you get an idea for a feature improvement. A good one! Act on it.
Plan it
Code it
Test it
Commit it
Deploy it
Nothing out of the ordinary, it seems. The seemingly new thing about continuous deployment is that we ...
Posted in process, teamwork | 2 Comments »
Saturday, January 16th, 2010
Defining what great software is, is not a complex endeavor. I prefer to boil it down into two distinct characteristics.
a) Ease of Use
The software solution walks you gently through the process of solving your problems as intended. No distractions, no unnecessary decisions to make, no confusions, always heading towards the ...
Posted in process, software | No Comments »
Wednesday, May 27th, 2009
I am a sucker for rationale. I've been struggling with rationale on the Extreme Programming (XP)-practice of pair programming for quite some time. What at first looks like one person writing code, and the other one watching, has admittedly been very counter intuitive to me. Let me share my current ...
Posted in coding, process | No Comments »
Wednesday, May 20th, 2009
The Software Management Manifesto *)
You have the right to an overall plan. The team should tell you what they could accomplish in the next year or two, and tell you how much that would cost.
You have the right to see progress. From the very beginning of the project, the team ...
Posted in process | No Comments »
Wednesday, May 13th, 2009
One of the more useful activities of Scrum involves a bit of self-reflection -- namely the retrospect. Admit that what you did yesterday could be done better today, and you are on the way to continuous improvement -- a goal in and of itself.
Scrum tells you to ask "What could ...
Posted in process | 2 Comments »
Tuesday, May 5th, 2009
If we are to do just-in-time user stories, we better know what is next, so we are not wasting any time on detailing stories way ahead. In this post we will look into how we will know what is next in line.
If you have only one, or just a few, ...
Posted in process | 3 Comments »
Wednesday, April 29th, 2009
The Agile movement *) has a lot of buzzwords. Keeping track of them, and knowing what is what is not always that simple.
Questions you might ponder may include
What is the difference between Scrum and XP?
Why are some using Scrum and some XP, and why are some using both?
What does XP ...
Posted in process | No Comments »
Thursday, April 23rd, 2009
In our summary post of Scrum, we refer to the Product Backlog as "a list of functional and non-functional requirements sorted by importance". This post aims to improve and add to this definition. We have decided to go with user stories in the Product Backlog.
A user story is a short ...
Posted in process | 6 Comments »
