Hi, Am I correct in thinking that in the exploration phase of iteration planning, not only does the team write task cards for stories, but it also writes tasks...
... I believe he was alluding to the notion that for whatever reason, a project may need a framework, but he couldnt see how that would be estimated into story...
... and it is in this same meeting ... to give estimates? This was ... stories and needed some estimates. ... a project that has none and ... I know this is...
Thats what I thought. So if no framework exists yet the team need a
consistent mechanism for the data access layer, how would this be factored
in? Not sure...
Kiel, thats very useful. I am sure when we discussed this, we kinda thought
that that is how it must happen in XP, given all the principles.
Now, when i think...
Not to speak for Ron, but... ... Fix the problems in the code and make another build of v1? ... Why? I guess you could end up with multiple levels of...
... It seems like this is the sort of thing that would come up in iteration planning, or worst case in a daily standup meeting. You: I'm going to implement...
... time. ... The data access layer wouldn't be factored in, it would be refactored out. You could start by not having a data access layer. When it comes time...
... You don't have a domain model already? From some of the conversation I had assumed you were working in a corporate environment, where most of the turf is...
... Separate build procedures. Stuff common to v1 and other versions + stuff unique to v1. ... I would suggest that (a) it requires exactly as much foresight...
... Well, if you create task cards, yes. I don't usually recommend them any more: I recommend that the team brainstorm tasks onto the whiteboard during ...
Hi Alex, that definitely makes some sense. I am begining to see that the
fundamental principle here is that one doesnt worry too much during
planning? Maybe...
Hi Erik,
Doesnt the factored out depend on how you are going to implement it. If I
was building a domain model, I personally would add persistence when...
... How might pair programming, team code ownership, and refactoring address the same problem? ... Observe during planning, where we brainstorm the tasks:...
... Just so. The same problem occurs in the branched format. Think Venn Diagram. Ron Jeffries www.XProgramming.com It's easy to have a complicated idea. It's...
... kinda thought ... dig deep for ... there are ... wish to have ... if there are ... then its ... different ideas for ... pure domain ... creating a ... ...
... producing a ... concepts in ... Why would you create a class graph? Is the class graph just a representation of the customer's experience and knowledge in...
... needed. ... but ... I'm not saying that I agree with the proposed design, but perhaps you could do it this way: You have class Foo. If it needs to persist,...
... His point is an excellent one, and his behavior is great in a non-XP context. It is a dangerous behavior in XP. My tips for dealing with this urge: Explain...
... Regarding 1 and 2, if they need 'em to estimate, then let them produce them on the whiteboard, right then. Forbid them to copy them down. If they need to...
... Your first iteration is kind of special. You're going to be shaking down the development environment. Besides this, you need to put out something that goes...
... I'm wondering if the above doesn't assume there is only one project whose needs must be considered. Mike Beedle has done some XBreed stuff using a combo of...
... John, I've heard this before, but I've never been comfortable with it. It seems to me that an iteration that doesn't implement any /User/ Stories should be...
... What caused you to do this? I would think that if I were going to experiment with the planning game, I'd start with a situation that matches the entry...
I'm contemplating writing a story on XP that would follow the experience of an actual team on an actual project. The methodology has been written about a lot...
