Software Engineering, Project Management, and Effectiveness
I'm a fan of simple maps to help drill in. After all, it's hard to explore the concepts if you don’t know they exist, or you don’t know what they are called. Below is a work in progress. I’m making a quick, simple map of the key activities for a some software project-relevant processes.
I’m sure I’m missing key practices and some of the names have changed. So I’m sharing it, so that folks can help share what they know, to get to a map that includes the right top level names of key practices.
I respect your effort but I don't quite get the point of it. If someone is a pro in any of these processes, he knows the practices. So this list has not much value for him.
If someone is not a pro, those words have no meaning - which also makes this list useless.
I think this list would be of much more value if every word would have a link to an article whith further information.
The point is for the pros to see if I'm missing any practices or got the names of the practices wrong. For example, there are two flavors of the XP practices, I'm not sure if this is the right set of Scrum practices, and I couldn't confirm Kanban with an authority (and the RUP list is old, and I'm checking on MSF. So it's a strawman for crowd-sourced input.
Next step, from the topology map, is to find the best prescription for each practice.
Yes, the list would have more value if it was linked -- that would be a vNext.
Great, Thank you, Astonishing Big Picture of Methodologies
do u put this content to any collaborative space yet?
i saw u also have your own wiki
there'd easier for collaboration?
btw, ur blog is nice place to gain 1st sight.
so, can here show live snap from ur wiki ?
"Visualize the workflow" is often part of XP and Scrum
In Scrum, most Stories are small enough to be "finished" in a single sprint.
XP is often combined with Scrum but can also be combined with Kanban
As Ian's comment illustrates, most of these methodologies have common roots so use the same or similar practices and artifacts. The approach and management of the work is what differs between them - making sure the "bite of the elephant" is just right and matches the amount of risk, time or resources the sponsor is willing to provide for that set of deliverables.
Of course, you will watch out for the items that are labeled similarly but have different content and/or context.