February 2012
M T W T F S S
« Jan    
 12345
6789101112
13141516171819
20212223242526
272829  

Not pushing the team too hard – a fine balance that can be easy to miss – Part 2 ..




The previous post (Pushing the team, maybe too hard) detailed some of the problems that a team that was under-performing started experiencing when it decided that it would not longer under-perform and started to move up the performance chain, but in the end, the focus on productivity started taking a toll on the team members. [...]



How to define tasks for a User Story without spending a fair amount of time on these ?




We seem to find ourselves running into a fundamental problem during out Sprint planning meetings. Some of it is from our older methods, but partially it also seems to be a problem with the way we are using our Scrum processes. Consider the process before getting into Scrum. We would have a list of features [...]



When executive apply pressure on the Scrum team to get a required number of features in




When a team is following Scrum, it means that the team decides the estimates, the number of features that are to be done per cycle (Sprint). The priority of features is as per the Product Owner, and it is the responsibility of the Product Owner to ensure that all the stakeholders are kept in the [...]



Scrum Product Owner – Clear vision vs. evolving thought and adaptability




Scrum has been setup based on some principles that seek to map how modern software projects actually are, with the biggest basic principle being the fact that business requirements keep on changing. Hence, if there is a methodology that requires you to lock all your business requirements at the beginning of the cycle, and makes [...]