389 reputation
49
bio website
location London, UK
age
visits member for 2 years, 9 months
seen Apr 20 at 21:21

Mar
20
awarded  Curious
Mar
15
comment How to monitor code review efficiently?
great, i look forward to hearing how it goes
Mar
13
awarded  Yearling
Mar
11
revised How to monitor code review efficiently?
added 7 characters in body
Mar
11
revised Are deadlines Agile?
added 11 characters in body
Mar
11
revised How to monitor code review efficiently?
added 108 characters in body
Mar
11
revised How to monitor code review efficiently?
Less emphasis on process and include code meeting the requirements
Mar
11
comment How to monitor code review efficiently?
@Mawg yes you are right the review should also include checking the code does what it is supposed to do
Mar
10
comment How to monitor code review efficiently?
It's running fine in my current team and wasn't too difficult to setup and it's helping - it's not an advert but it's the only tool of this kind i've got experience of. Would you say the same for Redmine codereview and ReviewBoard?
Mar
10
answered Project structure for overlapping product generations?
Mar
10
answered How to monitor code review efficiently?
Feb
23
answered Are deadlines Agile?
Feb
19
revised What is the purpose of planning poker in a sprint?
added 624 characters in body
Feb
18
comment What is the purpose of planning poker in a sprint?
It does tell you that once you've figured out how much complexity you can fit into 2 weeks - which can definitely change but if you need an indicator and i think it is more accurate than time estimates
Feb
18
comment What is the purpose of planning poker in a sprint?
I disagree - in Agile you're flexible with the scope. So if someone wants to fix the deadline and/or the budget you adjust the scope accordingly so you don't sacrifice quality, that's why the product owners should be prioritising the backlog.
Feb
18
comment What is the purpose of planning poker in a sprint?
I agree it would be great to just prioritise the backlog, forget estimation and just work through it. But this only works in certain organisations. Once you start introducing customers (meaning end users, clients or other teams/departments, budget holders, the Board, etc) they all want to know when will something get done and how difficult is it, so you need some way of estimating the work. Most people won't accept "it'll be done when it's done" that's just a reality we have to work in.
Feb
18
comment What is the purpose of planning poker in a sprint?
Don't worry about it too much just give the estimate you think fits best. You'll need to explain your thinking but once you've done it a few times with the team you'll get the hang of it. No estimation technique is perfect but I do think story point estimates are better than time estimates.
Feb
18
comment What is the purpose of planning poker in a sprint?
It is a relative measure, and yes it just gives a rough idea or indication. Complexity isn't exactly the same as effort but they can be equated. Something can be very complex or very simple. Which might mean it is a lot of effort or very little. The two concepts can definitely be equated but they are slightly different.
Feb
18
comment What is the purpose of planning poker in a sprint?
And you estimation itself barely takes up any time at all. Most of the time in planning meetings should be discussion of the features as a team
Feb
18
comment What is the purpose of planning poker in a sprint?
True but customers and users do care when something will be done. You might have a deadline imposed where e.g. the budget runs out so your product owners need to decide what gets delivered first. The complexity of something is part of deciding the order that features are delivered in.