1,586 reputation
820
bio website neverletdown.net
location United States
age
visits member for 4 years, 2 months
seen Dec 2 at 3:35

Jun
13
comment Backend devs put down by user stories
@AlanShutko - exactly. "One person's front end is another person's back end" right? This is one of the reasons why I dislike slang like "back end" and "front end" especially when talking about multiple components in a system. Your point is extremely important! Even "full stack" is a relative term that can mean different things in different parts of a system!
May
22
comment how can we have a person to allot and track tasks in agile development
Ok... so what was the action item your team decided on to help resolve this problem? To me it sounds like you need to do some more digging. My point is, why are you asking strangers on Programmers.se when you should be asking your team? There is no single right answer to this question, though some ideas will work better or worse than others. But if the context isn't exactly the same then your results will vary. Agile is as much about the journey as it is about the destination.
May
21
comment how can we have a person to allot and track tasks in agile development
What came out during your retrospective? Did the team have any ideas for how to address these problems? It sounds like there are probably multiple root causes...
Apr
17
comment When does pair programming work for you? When should you avoid it?
Trying to understand the value and logic of closing this question three years after it was clearly answered objectively with references to empirical research. Of all practices common to Agile, this is one of the most researched and documented. Does the wording of the question need to be changed in some way? Have expectations/standards changed in the three years since it was published?
Apr
8
comment As an lone, Agile (PXP/PSP) developer what is the proper structure for a formal project post-mortem?
Isn't there a script in PSP for this? Perhaps an extension or modification of the PIP template?
Jul
9
comment How do I handle a user story that I complete, but with compromise and need to revisit?
@ProfK This is strategic technical debt. Remember that not all technical debt is negative or bad. In this case you changed the system so that you could ship today knowing that you would need to make a change later. This is an excellent example of taking on strategic technical debt -- in moderation a good thing.
Jul
9
comment Backend devs put down by user stories
Good advice. Keep in mind that there is nothing in the agile manifesto about "user stories" and they are just a popular practice that came about with specific processes. You can be just as agile with user stories as you can without..
May
29
comment Software Architecture Modelling
@AndreasHuppert, I didn't say impossible. But it can be difficult and depending on what views you plan to depict, unnatural. With so many diagrams to choose from using a slimmed down version as you mention is a very good idea. The second half of George Fairbanks' book "Just Enough Software Architecture" gives UML for software architecture a fair and thorough treatment.
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.
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
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
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
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?
May
21
comment How to specify a functional requirement?
The story wouldn't stop with just "manage the list of users" but would also include a bulleted list detailing what this means, as well as additional clarifying discussion (for example, on the back of the card) to help clarify the requirement as new information is uncovered, and maybe even some paper prototypes showing what the feature would look like.