In the second of two articles Claudio Kerber talks about his experiences in team formation and collaboration and explains the process whereby he "became unnecessary" as the team he was working with built trust and cohesion through trust, shared knowledge and shared experiences. He examines the theoretical underpinnings and discusses ways in which servant leadership emerges.
Nick Malik, an Enterprise Architect at Microsoft, wrote a blog post differentiating business analysts from business architects and he received a swift rebuke of his stance. Malik contended that business analysts do fundamentally different work than business architects but Kevin Brennen of the IIBA strongly disagreed and pointed out the resemblances between the roles.
Historically, some product owners have prioritized backlogs by making pairwise comparison of projected economic return between two items in isolation. Successful Agile teams often take a holistic approach, accounting for risk, dependencies, and the complex interplay among and across backlog items.
The International Institute for Business Analysis and the Agile Alliance have collaborated on a volunteer program to produce the Agile Extension to the Business Analysis Body of Knowledge. The Extension has now been released for public comment and feedback.
The International Institute of Business Analysis announced the release of a first draft of the Introduction for the Agile Extension to the Business Analysis Body of Knowledge at Agile 2010 today. They are looking for participation and feedback from Agile practitioners and business analysis professionals.
In this presentation from SOA Symposium 2010, Manas Deb and Clemens Utschig-Utschig discuss how to derive business agility from SOA and BPM, motivations for agility, developing and nurturing agility, influencers and dependencies, how SOA and BPM enable agility, pitfalls and recommendations for organizational culture, and pitfalls and recommendations for business and technical architectures.
At a recent IIBA New Zealand members event Shane and Pete debated the role of the business analyst on Agile projects. Shane presented on why analysis is so important on Agile projects, and why the role of the analyst remains crucial to project success. Pete said that the traditional role of the Business Analyst is under threat and will need to evolve in order to be valued on an Agile project
Dennis Stevens discusses ways to identify and focus on business value and risk mitigation in Agile projects. As a contributor to the Agile Extension to the BABOK, and in his work on the ICAgile Business Analysis & Value Management area, and how to identify, prioritize and mitigate risk in software development projects.
