I have been confirmed as a speaker for the Business Rules Forum 2009 in Las Vegas, NV in November 2009 (http://www.businessrulesforum.com).
The title of the talk is: Business Rules Governance and Management: A Case Study in the Public Sector
If you read this blog and are coming to Business Rules Forum 2009, feel free to come talk to me!
Once again, my search for anything related to governance and management brought me to the bpmbasics.com website to watch the seminar Roles on BPM at http://www.bpmbasics.com/resources/academy/bpm104.jsp
My contention is that a lot of the concepts applicable to BPM are also applicable to business rules.
Here are some highlights of the webinar edited to apply to business rules:
It’s about the people. People are at the center of this, they make this possible.
The roles identified and their responsibilities:
- CIO / CTO, Executive Team
- If driving the initiative, account for metrics and high-level KPIs
- If not, push for executive buy-in and high-level organizational support
- Use high-level support as an opportunity for improvement across silos (COE, Governance)
- Center of Excellence (COE)
- Common location for skills, knowledge and an enterprise wide vision
- Technology Advisory Board (Technology Councils or Think Tanks)
- Facilitates standards and software adoptions across group
- Industry experts
- To help kick start the knowledge transfer within the organisation
- Vendor support
- To help make optimal use of the tools
- Business Analyst, Business Rule Analyst
- Gathering requirements, rules and performing analysis
- Rule developer
- Helps the Business Rule Analyst with implementation of the rules for execution
- IT Architect
- Responsible for the architecture and design of the enterprise system integration and configuration
- System Developer
- Responsible for low level development, integration with other system, etc.
Titles are less important than clear definitions of responsibilities.
Pay attention to the handoffs between roles.
Composing Project Teams
- Business goal driven, but technology powered
- Create mixed teams of technologists and business analysts
- Involve and be involved with outside groups
- Build teams for quick results but develop skills and roles for the long term
Creating your BPM team
- Adapt to the specific project size and complexity
- Leverage prior successes
This list of roles is a decent starting point. The information extrapolated from this webinar can also be cross referenced with the list of Roles from ABRD v1.2 (which seems a bit more complete) and other sources.
I guess I now have to take all that information and take it to the next level… You should expect more on this topic in the future.