Reputation
399
Top tag
Next privilege 500 Rep.
Access review queues
Badges
4 11
Impact
~26k people reached

  • 0 posts edited
  • 0 helpful flags
  • 81 votes cast
Nov
11
comment Maintain hundreds of customized branches over master branch
Also creating versioned packages to help the team track which client has which version of the code
Nov
11
comment Maintain hundreds of customized branches over master branch
Maybe they should use a static code analysis tool to narrow down what parts of the code are duplicated (after identifying all the files that are the same)
Oct
1
awarded  Popular Question
Jul
10
awarded  Popular Question
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.