546 reputation
15
bio website theagilecoder.wordpress.com
location
age
visits member for 1 year, 10 months
seen 11 hours ago

Solution Architect with nearly 15 years of experience in the software development field. Into ALM, integrations, software architecture, and stopping slapshots.


16h
comment In an Agile Environment, who is responsible for software architecture
Thank you gnat, I have tried to edit it to make it more clear as to what my intention had been for responding to the question. I made a few leaps in my head, but forgot to write them down :)
16h
revised In an Agile Environment, who is responsible for software architecture
added 896 characters in body
Oct
17
answered In an Agile Environment, who is responsible for software architecture
Sep
24
awarded  Autobiographer
Aug
5
answered How does requirements management work in the long term with Agile projects?
May
20
answered Should a user story be shared between developers?
May
7
answered Agile retesting
May
5
answered Planning troubleshooting in a sprint
Feb
4
comment Criteria for prioritizing product backlog
It only goes against the paradigm if the system is unusable with the code in place. If you are making changes that can't be stabilized within your sprint or hidden so as not to impact your users, the story is probably too big and needs to be broken into smaller pieces.
Feb
4
awarded  Commentator
Feb
4
comment Criteria for prioritizing product backlog
For risky items we attempt to chunk into more palatable pieces that can be delivered iteratively, and then resolve 'showstopper' bugs that would prevent delivery. Essentially, the story isn't "Done". Other bugs that are lower priority go to the backlog to be prioritized alongside other work.
Feb
4
comment Criteria for prioritizing product backlog
That's why value is also part of the equation. You don't want low-value high-risk items first. If you have high-value or mid-value items with risk, you should do those before high-value low-risk, because you don't have risk in doing those later. Ask your devs: if you have 2 days left in your timeline, do you want to start on some easy stuff, or the riskiest stuff in the project? That's why you raise priority on riskier items: project risk mitigation. With that said, if you can deliver minimum shippable without a risky item, that probably indicates a low business value anyways.
Feb
4
awarded  Editor
Feb
4
revised Criteria for prioritizing product backlog
spelling typo
Feb
4
answered Criteria for prioritizing product backlog
Jan
21
comment How to introduce Scrum in a company accustomed to Scrumbutt or Scrumfall?
Well worded PDR, this is exactly what I've had to do in similar situations. Actually, if the managements is already open to 'agile', that makes fixing the problems a little easier because you don't have to sell them on what they've already bought.
Jan
17
answered How to organise the different bits and pieces in an agile environment?
Dec
14
awarded  Yearling
Nov
13
answered How to estimate tasks in scrum?
Oct
31
comment What happens with project backlog if sprint due date is missed?
I think I'm just confused in your use of the term 'velocity report', as it is different than how I use my velocity report. I use the velocity report to track business value delivered, not effort spent, but I can see what you mean. I can definitely see the benefit of you also tracking the effort your team spent in R&D versus maintenance. In my opinion, you still should only recognize the'estimates' that were successfully delivered, but you may want to make your velocity report have multiple bars (hours delivered, hours spent, hours on maintenance).