Originally posted by Darya Akbari:
So what's the Software Development method you use? You say that any sort of iterative/incremental lifecycle will work. But which one do you present in your book? Does it has a name?
I think you're asking two questions here .
For software development methodology (not project management), I lean towards the XP practices. They're low ritual and high return for the time.
For project management, I lean towards Scrum. I didn't name the generic i/i lifecycle in the book. I did picture something more like Scrum than anything else.
In the book, I discriminate between the management practices a PM can use and technical practices a team can use. Maybe I'm just too literal , but I really believe the PM has different work, so I don't believe that the PM approach is the software development methodology. To me, they are two different things.
Originally posted by Johanna Rothman:
I don't believe that the PM approach is the software development methodology. To me, they are two different things.
Same to me .
Let me just summarize:
Obviously you see above combination as today's best practice .