611 reputation
25
bio website theagilecoder.wordpress.com
location
age
visits member for 2 years
seen Dec 18 at 13:44

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


Dec
14
awarded  Yearling
Dec
4
comment Scrum: Capacity vs Velocity when planning a sprint
You can use a rough 'hours per day' historical average and then plug in the days off and you should get a good guess at your total hours capacity. Visual Studio Online/TFS have this type of planning capabilities in it and it can be helpful. However, people tend to get caught in the accuracy (or lack thereof) in the task hours estimates.
Dec
3
answered Scrum: Capacity vs Velocity when planning a sprint
Nov
13
revised How can I specify user stories for processes with third-party involvement?
Finishing incomplete sentence.
Nov
13
answered How can I specify user stories for processes with third-party involvement?
Nov
5
answered Scrum: Is it okay for the development manager to be the Product Owner
Oct
21
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 :)
Oct
21
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