Process is often viewed like a machine. We’d like to create a development process that works, then push a button and have everyone on the team conform to it. Wouldn’t it be great if next Monday everyone was doing Scrum perfectly?
It turns out that people aren’t machines. Who knew? People can’t change behaviors at the flip of a switch. New habits have to be developed, practiced, repeated, reinforced. Old habits need to be constantly transcended until the new ones have grown strong enough to be part of the quotidian.
Process enactment is about translating the vision of how our teams should operate – the practices those teams engage in that make the team successful – into actual behavior by individuals. At its simplest, we need to describe a task that should be performed, and then make sure it actually is performed by someone.
RMC is the tool for describing tasks (and guidelines, templates, examples, lifecycles, and all sorts of other things). RTC can import those tasks as work item templates. A project created using those templates automatically create work items that correspond to the tasks in our process. Those work items even contain links to the task descriptions in a published process, providing direction, guidance, and context to the assignee. RMC 188.8.131.52 can export tasks (and other elements) that can be imported into the current version of RTC as work item templates. The current version of RTC can import those templates.
I’ll get into the details in a future post. Until then, remember that RMC describes your process: the practices you want your team to execute that will make them successful. RTC enacts that process, enforcing tasks that must be performed and reflecting how well the team is performing those important practices.
– Jim Ruehlin