Process Styles

I have been reading about REST a lot recently, and hence about architectural styles. Perhaps I have found them in the opposite order. Nevertheless, it has been extremely refreshing and educative. So much so that I saw even SOA in the new light.

An architectural style is a coordinated set of architectural constraints that restricts the roles/features of architectural elements and the allowed relationships among those elements within any architecture that conforms to that style.

The most important keyword there for me is constraints. If identified properly they help, not hamper, productivity. And I think most of the faults in software development boil down to the assumption of wrong set of constraints.

This led me to wonder if we could have process styles. Like the architectural styles, the process styles provide a coordinated set of constraints. Software development process depends on various aspects, and might need to change depending on various scenarios. Nature of the work, skill-set of the team, timelines, client’s knowledge, and many more things can affect which software process to use for a project. In such cases, process styles can help us identify and get a coordinated set of constraints in an easier way.

Another important aspect of styles is that they do not design or implement things. This gives a lot of freedom to the team to implement in different ways depending on the scenario.

Do we have process styles? RUP is more of an all-inclusive meta process. XP seems to talk about some things in more detail than some would like. The closest we have today for a process style today, is their abstraction, agile development.

But I think we do some more work here, especially by focusing more on constraints. Maybe this thinking will bump into other styles as well. This can help us in choosing the right process or customizing a process to the right level for our work. I am sure you see that I am not very clear in my thoughts yet, it is quite foggy. Hopefully writing here and discussing more will help me think through it.

Discussion [Participate or Link]

  1. Mike said:

    You’ve definitely hit upon the bane of Project Managers’ existence. If you are able to flesh out these ideas and create the framework for your constraint-based “process framework”, you could find yourself a wealthy person! I look forward to reading your developments

  2. Agile Development A Culture, If You Believe | iface thoughts said:

    […] to follow a set of principles without being restrictive about how we do that. I like to call it a process style, which lets you implement your own process to be […]

Say your thought!

If you want to use HTML you can use these tags: <a>, <em>, <strong>, <abbr>, <code>, <blockquote>. Closing the tags will be appreciated as this site uses valid XHTML.



Abhijit Nadgouda
iface Consulting
+91 9819820312
My bookmarks


This is the weblog of Abhijit Nadgouda where he writes down his thoughts on software development and related topics. You are invited to subscribe to the feed to stay updated or check out more subscription options. Or you can choose to browse by one of the topics.