"I've heard of people doing that on the release burn down when new work gets added by the PO. Not convinced that it's such a great idea for a sprint burn chart. But then, I'm not a big fan of sprint burn charts or tracking stories,…"
All About Agile | Agile Development Made Easy!
Dominic Hurst's Discussions
How to Handle Bugs
1 Reply
Hello all Agile masters, masters of agility.We are about to embark on our first journey of a release into the QA environment for integration testing. Our main objective from this excercise is to…Continue
Started this discussion. Last reply by Duncan Campbell Apr 26, 2010.
Velocity Points
11 Replies
Hi all agile mastersQuick question; what is the approach recommended when you realise during a sprint that the original estimation for a user story is too low, its now more complex than what was…Continue
Started this discussion. Last reply by Phlip Jun 7, 2010.
How to keep all Team members busy
8 Replies
We are an organisation that has adopted SCRUM about 4 months ago and to be honest things are not maturing as fast as theory says it should. One of the questions that was asked during a sprint…Continue
Started this discussion. Last reply by Ilja Preuß Jan 21, 2010.
Dominic Hurst's Page
Latest Activity
"Hi, thanks for the reply. I deal with this situation in a similar way to what you described above, thanks again"
"thanks for the reply. I generally add a negative burndown underneath the original to track the points added during the sprint and then redraw the sprint burn line, hope you get what I mean. Similar to your chart going upwards but it keeps going…"
Radha Israni replied to Dominic Hurst's discussion Velocity Points"1) For the remaining tasks within the current Sprint - have a mid sprint meeting and re-assign story points to the remaining tasks- this will likely cause you to miss out on certain tasks but at least you will have better and more accurate reporting…"
Ilja Preuß replied to Dominic Hurst's discussion Velocity Points"First and foremost, if you don't know the answer, be a rolemodel and admit it. Being able to admit when you don't know something is a strength and necessary behavior for a team, that as a leader you probably want to model for…"
Duncan Campbell replied to Dominic Hurst's discussion How to Handle Bugs"Is this a bug-fixing sprint, or a sprint where you expect to also have to fix bugs?
Bugs are just like features: they are the absence of the required functionality.
Therefore, bugs should be treated like features, and prioritised accordingly.
You…"
How to Handle Bugs
Hello all Agile masters, masters of agility.We are about to embark on our first journey of a release into the QA environment for integration testing. Our main objective from this excercise is to align just how far off the mark we are. We will be planning our next sprints in the same way we always have but I have suggested we keep it light in order to deal with bugs coming from integration testing. The idea that I have in my head to deal with bugs is that we create a user story on the sprint…See More
"come on you are living in Utopia, we still need to make decisions while we learn and then does the learning ever end? Yes in theory there is a clever answer for everything but in reality someone needs to put their signature to paper or code."
"for making the decisions? People are happy to discuss all hours in a day but when you want to hold someone accountable for the decisions they tend to back away. I am not saying a design cannot be achieved by a grp but at the end of the day there…"
Manish Manekar replied to Dominic Hurst's discussion Velocity Points"Dominic,
I happenes with most, if not all! There are many ways teams handle it and here is my take on such a situation:
1. Every task - planned or not, this way or other - should be accounted for.
2. It obviously adds up to the sprint backlog and…"
Velocity Points
Hi all agile mastersQuick question; what is the approach recommended when you realise during a sprint that the original estimation for a user story is too low, its now more complex than what was originally thought, lots of purple stickies start appearing (unplanned tasks). I ask the question to the team " how many points did we burn yesterday" and the developers thinking cause they killed a few unplanned tasks ask back " what happens to the velocity if its now more complex than what it was and…See More
"Hi
Where I am now we are still maturing our SCRUM process and Architecture is one of my(scrum master) biggest headaches. My opinion; You can have all the agility in the world but you still need a single point of responsibility for architecture you…"
"Hi
Are you refering to me when you mention about benefiting from a coach on site? If so we happen to have one coming on Monday : ). Interesting that you strongly disagree with having tech stories on a product backlog, I would like to know more…"
Ilja Preuß replied to Dominic Hurst's discussion How to keep all Team members busy"One pattern that has worked well for us: let the junior pair with the senior for the morning. After lunch, split: the senior continuous working on the stories, the junior reviews what he has learned - takes another look at the code, takes/reviews…"
"You are right on both. I was coming from having to plan sprints in accordance with priority, what if you never got decent work for the jnr guys or there was never enough to keep them busy/happy. My statement of it being silly is aa bit…"
Comment Wall
- No comments yet!
© 2012 Created by Kelly Waters.
