It’s been a while since we wrote about the issue of processes and projects. These often get muddled up, mainly because we tend to look at the disciplines as being very different. For example would a business analyst call themselves a project manager, or vice versa?
The answer of course depends on the person. Vendors, HR, products all contribute to the confusion making you think that one technology can’t be applied to a different problem. Here are some points to determine where you stand on this issue, and my personal answers:
- A project is just a series of processes connected together. True or False?
- True. Every project can be broken down into processes. Usually we add milestones and deadlines to the project, but the basis is still the same.
- Most project management software is not very good at creating multiple outcomes from tasks, and the interdependencies are hard to represent in the linear input format of most systems.
- TaskMap 4 Professional has the ability to create Work Breakdown structures, and any expert who knows the requirement for the WBS could use it regardless of application.
- An interesting question that needs to be considered by all project managers and process groups.
Have some fun answering this questions, and I will follow up with my own answers tomorrow.