Maybe i'm not using the right word (procedural), anyway here are my thoughts on why XP is procedural ... I see XP as a specific agile methodology. It requires...
I've been reading "Project Retrospectives - A handbook for team reviews" by Norman Kerth, in preparation for doing one. Mr. Kerth recommends a couple of things...
When I was running weekly retrospectives at Torus we held them in the boardroom. We got the whole team together and went around asking everyone what they felt...
... It does help. Sounds like it did result in useful changes. Doing a little each week seems to me like something that can be in or out without a cost hurdle...
The advantage of weekly retrospectives is the speed of feedback. A reoccurring theme in XP is "if something is good do it more often". Post-mortems are good,...
Hi Thanks to all who repsonded to my original thread of "Anyone successfully used SCRUM?" Good food for thought in those posts for me personally. This leads me...
... Yes. ... Yes. ... Yes. That makes sense. And if we have a project where we haven't been doing weekly retrospectives, or anything like that, I think that we...
... Probably very true. Just saying that is the easy bit however. The hard things is exactly how to do this. XP provides some guidance but it's such ...
Without having read the book, a couple of simple techniques I've used in the past quite successfully include: 1. Continuing on the theme of keeping positive,...
We are busy reviewing how we are going to buid the teams for our sprints, and we decided to create the teams after the Sprint Backlog (SB) has been identified,...
... Thank you very much for sharing your experience with me. This all sounds to me like something likely to work well and worth trying. I'll have a talk with...
This would seem to relate more to the practices you are using inside your Sprint, so is outside the scope of Scrum. Frequent customer interaction is essential...
What we are trying to figure out is, would you add the activity "Gather and document requirements for End of Year business function" to the Product Backlog,...
I like to draw the "team" boundary as broadly as possible. You can ask similar questions about DBAs, HCI specialists etc. I find that I need to draw...
Yes, I'd agree with Steve. I use a broad definition and include non-programming tasks such as design and database specific tasks. However, I usually keep it to...
Good advice. That is the empirical process after all..inspect and adapt. Thanks Kurt ... programming tasks such as design and database specific tasks. However,...
So, on the Product Backlog, would you include ALL activities required to produce the Product, e.g. "Procure hardware", "Developer training in .NET", "Gather...
Just my opinion here... I would include: "Developer training in .NET" "Gather requirements re: XYZ" ... since they affect the amount of time the team has in...
Sorry, late getting back to these things... Yes, I would. If you don't do that, then you're creating a group of teams, each with their own backlog. If you...
Chris, I bet you'd still include "Check that hardware was procured" in the backlog though. Just because something is a responsibility allocated to someone in...
Robert, I think that you mean "prescriptive", rather than procedural, but I understand what you mean. There is *NO* list of practices that must be followed for...
... Ah yes ... your right "prescriptive" is what i was looking for. ... Gosh, here we have very different views. Unfortunaley my XP books are at work, but my...
... XP is a list of practices that Kent and others have found to be synergistic. It's a great starting point (although Kent also talks about adopting XP one...
Hi The system we are working on is currently developed using Visual Basic 6 COM components and ASP pages. New development will take place using .NET. Can...
What you say makes sense to me. I'm going to have to think more about this "prescriptive" bit though ... you have me thinking. Food for thought, thank you. ...
