1,576 reputation
820
bio website neverletdown.net
location United States
age
visits member for 4 years
seen Jun 24 at 13:19

May
24
answered Software Architecture Modelling
May
24
answered Agile MVP (Most Valuable Player/Programmer)
Feb
22
awarded  Caucus
Jan
23
comment Has research been done on the effectiveness of Planning Poker as an estimation technique?
Planning poker is an example of a delphi estimation technique, and is a variant of wide-band delphi. There is much research on wide-band delphi that applies to planning poker.
Jan
2
comment IEEE SRS documents: lightweight version when working with outside contractors?
"...I realize that with outsourced development that it is a good idea to be as firm and specific as possible..." interesting that you seem to hold a double standard to the way your team works vs. an external company. In this scenario, wouldn't your team fill the "customer" role?
Jan
2
comment IEEE SRS documents: lightweight version when working with outside contractors?
we're in total agreement on that point. No process is... no process no matter what label you put on it. The main problem I have with your answer is in the idea that "SRS is a no-go in Agile" and "in agile, requirements are specified as User Stories." You can still be perfectly Agile and not use user stories. This is wrong and distracting an otherwise good answer.
Jan
2
comment IEEE SRS documents: lightweight version when working with outside contractors?
I don't recall reading anything about user stories in the Agile Manifesto... be careful not to confuse common agile practices with what you must do to "do agile." Being agile is about promoting practices that allow change and maximizing value. In an outsourcing scenario such as this, sometimes extra structure can create greater opportunities for agility.
Jan
2
revised Hardware requirements
updating to include a new section of information
Jan
2
answered Hardware requirements
Dec
7
comment How do bug reports factor in to a sprint?
One way I've handled Option 1 is to set aside a block of points, in the backlog for bug fixing. It makes planning a little easier and gives visibility to priority etc. along with other work items. Of course you wouldn't include these "bug fixing points" in with your velocity since you're not adding any value...
Sep
29
awarded  Yearling
Sep
15
comment Are costs part of the requirements?
Cost is very much an architectural driver and should be considered side-by-side with functional requirements, technical constraints, quality attributes, etc.
Aug
27
answered Story points for bug fixing tasks: Is it suitable for Scrum?
Aug
27
comment Story points for bug fixing tasks: Is it suitable for Scrum?
@maple_shaft "bugs found in a feature after the sprint has been accepted means testers made a mistake in not catching these bugs before acceptance" -- or developers made a mistake injecting the bug in the first place, or the product owner made a mistake not understanding customer's actual needs when articulating the story, or .... A defect can be injected in lots of different places by lots of different people. You can't test in quality.
Jul
25
comment Documentation degrading - how to deal with it?
The underlying point here is important -- you need a documentation champion who is going to hold the team to some kind of standard.
Jun
27
comment Who should be the architect in an agile project?
Don't forget about the "5th value" of the Agile Manifesto: "Craftsmanship over crap." It sounds like your team is favoring the item on the right a little too much. infoq.com/news/2008/08/manifesto-fifth-craftsmanship
Jun
8
awarded  Constituent
Jun
8
awarded  Caucus
May
25
comment How to create the architecture/design of an application in Agile?
@SamehSerag, "The core grows automagically as you [re]factor..." implies that the architecture is not being actively chosen but rather allowed to "automagically" emerge by coincidental choices about lower-level (not systemic-level) decisions. That is the problem with trying to organically "grow" the architecture through refactoring.
May
25
comment Ways to version user generated documents
What is the security model -- I assume each users' documents are private?