Learn more about how we develop IBM Integration Bus. And the channels to influence it!
James Naish 110000A4PK Visits (1963)
Over the years, Agile methodologies and practices have become increasingly popular. In IBM, we were early adopters of this approach and develop IBM Integration Bus in an Agile style - so we can adapt to change quickly and deliver new functionality as the market changes.
As part of our development process, we engage stakeholders, both inside and outside IBM, with two distinct purposes: receive direct feedback on the capabilities that they would like to see in IBM Integration Bus, and receive feedback on how features under development are meeting their expectations. We work with a variety of stakeholders through a mixture of routes - managed beta workshops, open betas, request for enhancements (RFE), customer visits and customer events.
Our development team is organised into multiple scrums (for historic reasons we call them LIDs – Line Item Delivery teams) that cover all the development disciplines – design, architecture, coding, testing and technical writing. Each LID focuses on delivering stakeholder value around a particular theme, feature or capability. The teams have a single purpose and work collaboratively to meet that goal. We are a global team, spread across multiple development labs - regular communication is facilitated through daily scrum calls.
Work is broken into Epics, User Stories and Tasks. The Stories are story-pointed to help the teams better understand what is required and the relative complexity of the work. The points also help with Iteration planning. We use a clear ‘Definition of Done’ to ensure all the work we deliver is complete and high quality. Regular internal and external demos are encouraged to ensure the capability meets the needs of the stakeholders.
We currently work in 4 week iterations, though some teams break this into 2 x 2 week iterations. Any discussion on changing iteration length is always lively!
That's the high level view of how we operate. If you would like to learn more, add a comment to this post, or email me at email@example.com