The first week was discussing architecture, but it went pretty quickly. No UML, no TDD, just git-r-done. If I were to change things in the future, I’d attempt to do some TDD from the get-go since the lack of architecture hasn’t been a problem, but lack of regression testing has since we’re iterating so quickly.

I’ve never used/read up on the pragmatic approach so don’t know how it compares to the iterative one I’m attempting to do.

Sounds like development then switches almost to creating a prototype, and then using this as the foundation of future development. Might well be a lot more instinctive for coders to work this way, certainly seems much more old school software development than starting with wireframes and architecture.

I’m left wondering through if there could be ways of using agile alongside the more pragmatic approach? Or are these far to radically different to each other?

1. Does Scrum or the project manager makes detailed effort estimations (besides the pointing system), Gantt charts, etc. And what’s your opinion or your project manager opinion on having this type of effort estimations?

2. Are there any differences between a story and a use case?

3. When does Scrum starts – are there any prerequisites before the actual Scrum begins, e.g. already completed communication and planning activities – or these two activities are somewhat incorporated in the Scrum itself?

I’m not looking for recipes and I do realize that the process is usually tailored for the particular circumstances, but I’m really interested in your point of view.

BTW, thanks for posting your business talk online, http://jessewarden.com/archives/blingflex/ . It really brought focus to what I need to do next.