Reputation
21,082
Next tag badge:
161/100 score
15/20 answers
Badges
6 41 113
Impact
~790k people reached

Feb
25
comment Integrating QA within agile sprints
I think on top of that if they still have nothing to do there is probably always some "sprint zero" tasks or research that can be done. Maybe you had to spike in the next sprint to find out more about a tool that the team has little collective experience in? Maybe you want to expand the capabilities of your CI environment?
Feb
24
answered Multithreading message broker in a transactional system - Best Practice
Feb
12
answered Sharing dependency configuration over multiple projects (Maven)
Feb
12
comment Sharing dependency configuration over multiple projects (Maven)
In the future if you feel you posted a question to the wrong place, then flag a moderator and request migration. Thank you.
Feb
12
comment Boss is ordering me to send spam. How to I deal with this issue/what is my options?
Make your boss read this. stackoverflow.com/questions/3905734/…
Feb
12
answered What to do with user stories that depend on horizontal integrations?
Feb
12
comment What to do with user stories that depend on horizontal integrations?
+1 for a good answer, however I would like to note that the OP never actually mentioned he was using Scrum.
Feb
11
comment How can I ask my boss (in a polite way) to comment his code?
Comments are not for extended discussion; this conversation has been moved to chat.
Feb
10
comment Trying to process partial POST of data in REST when some data is successful?
@CormacMulhall This really should be an answer. It is much better than the currently accepted answer as that one condones breaking principles of REST
Feb
10
revised Trying to process partial POST of data in REST when some data is successful?
edited title
Feb
9
comment How can user stories not contain requirements (when written on a card) and still be implementable
The problem with this line of thinking is that it works well in a creative project where the user needs are clear but the hard specifications are limited. When we start talking about complex system interactions and especially regulatory constraints and business need for hard defined system parameters then user stories alone often fall short of capturing the important details. So they strike up the conversation but when I have 20 pages of hard unbending specifications and rules then that is too much to absorb in a "conversation". Functional requirements are necessary here as well.
Feb
9
comment How can user stories not contain requirements (when written on a card) and still be implementable
@Alex See my comment above. I think you are both confused as to what a functional requirement is.
Feb
9
comment How can user stories not contain requirements (when written on a card) and still be implementable
@jmoreno Actually a performance metric like that is considered a Non-Functional Requirement a non-functional requirement is a requirement that specifies criteria that can be used to judge the operation of a system, rather than specific behaviors. The behaviors themselves are functions of a system. The user story contrasts both of these by defining the need of a user. The function of a user is instead what we know as a Use Case and not a functional requirement.
Feb
9
comment How can user stories not contain requirements (when written on a card) and still be implementable
@AK_ I don't think he is stating that all of this needs to be done upfront, but certainly enough has to be done upfront prior to sprinting where a sizable backlog exists.
Feb
9
comment How can user stories not contain requirements (when written on a card) and still be implementable
@gnat I think while there are "rantish" elements to the question, the underlying question at hand is good and answerable.
Feb
9
answered How can user stories not contain requirements (when written on a card) and still be implementable
Feb
9
awarded  Good Question
Feb
6
comment Is prototypal inheritance inherently slower?
Comments are not for extended discussion; this conversation has been moved to chat.
Feb
5
comment Functional Requirements, Non-behavioral specifications, Acceptance Criteria and the gap
@DocBrown You are right about too many levels of requirement analysis but believe me when I say this is borne of necessity. Being polite as possible, I can only say that the Non-Technical BA's are quite poor at actually writing good requirements and often need a lot of hand holding. The abstraction comes from trying to fill in the gaps that they leave behind.
Feb
5
comment Functional Requirements, Non-behavioral specifications, Acceptance Criteria and the gap
We have been espoused by Scrum zealots that have a holy crusade against a formal SDS document. Also an interesting caveat is that the business stakeholders wish to see and personally approve each user story and functional story. To give them a clear picture we must define all aspects of a complete testable functional requirement in user story form on the backlog. I suppose our problems is that the business demands the aspects of scrums while not abdicating the need to personally approve functional details.