understand architecture (see - http://improving-bpm-systems.blogspot.ch/2013/06/entarch-basics-in-for-dummies-style.html)
understand #bizarch (see - http://improving-bpm-systems.blogspot.ch/2011/02/explaining-ea-business-architecture.html)
know #bizarch artefacts
- mission, vision, strategy (see - http://improving-bpm-systems.blogspot.ch/2013/04/enterprise-patterns-strategy-to.html ),
- goals, objectives, (see - http://improving-bpm-systems.blogspot.ch/2013/03/result-based-logical-framework.html ),
- organisation design (see - http://improving-bpm-systems.blogspot.ch/2011/10/enterprise-pattern-structuring-it.html and http://improving-bpm-systems.blogspot.ch/2012/01/enterprise-pattern-sito-extended.html )
- portfolio/projects (see - http://improving-bpm-systems.blogspot.ch/search/label/PMO )
- capabilities (see - http://improving-bpm-systems.blogspot.ch/2013/03/bizarch-artefacts-definition-again.html )
understand processes as the most popular #bizarch artefacts
know process patterns (see http://improving-bpm-systems.blogspot.ch/search/label/practical%20process%20patterns)
know how culture may effect organisation
know "business analysis" from http://www.iiba.com and get ceritication
know "business architecture" from http://www.businessarchitectureguild.org/ and get certification
know the relationships between all #bizarch artefacts (very important)
know enterprise patterns
be able to design processes (as a path to business process architect)
understand basics of application architecture
specialize in e-gov or healthcare or other domains
AS
No comments:
Post a Comment