Dirk Krafzig presents general aspects of implementing SOA security using a token and role-based approach rather than session and application-based access to resources, including organizational issues, such as the need for an enterprise security architect.
The Product Owner role is regularly debated and discussed. The challenges of the role and the responsabilities encompased by it are a frequent source of discussion and advice. Recently there has been discussion about common aspects of the role and the important activities a product owner needs to ensure happen on an agile project, and the difference between the product owner and product manager
Tom Hollander, a Solutions Architect at Microsoft Australia, held a presentation entitled The Role of an Architect in an Agile Team at TechEd Australia where he discussed what he does as an architect leading an agile team.
Patrick Wilson-Welsh, Chris Beale, Gary Baker, John Huston, Daryl Kulak, and others are attempting to popularize the idea of a new role, the "Agile Team Lead", to supplant many of the existing leadership roles found in and around agile teams.
Mapping traditional software development roles to just the three roles in Scrum can be challenging. Mike Cottmeyer attempts to provide an effective mapping which would help the teams.
This article surveys the expected variation of different roles in the Agile organization and proposes techniques with which to better handle the transition to Agile methodologies from traditional Waterfall. The following roles are discussed in this article: Customers/Stakeholders, Product Management, General Management, Project Management, Developers and Quality Assurance.
Service Governance is an essential aspect of a successful Service Oriented Architecture. Its establishment has to be planned and tested out early in the initial phases of a SOA initiative. In this article, Jean-Jacques Dubray shows what it takes to create such a structure efficiently.
In this presentation recorded during QCon London 2008, Udi Dahan, The Software Simplist as he calls himself, explains why sometimes it is not enough to apply good OOP and patterns lessons. He introduces a new principle: make roles explicit.
In this presentation, which was recorded at JAOO, Software AG's Ivo Totev introduces his views on SOA and SOA Governance. Topics covered include how SOA governance can be defined, why governance is needed, and what areas it can be decomposed into. Totev also describes a SOA registry/repository solution, which in Totev's opinion is something that should be introduced in the earliest stages.
