Jesper Boeg on Priming Kanban
In this interview, Jesper Boeg, author of the new InfoQ book – Priming Kanban, discusses the keys to using Kanban effectively, and how to get started if you are currently using other approaches.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Dilip Krishnan on Nov 05, 2008
According to a press release, Microsoft Corp. joined the Advanced Message Queuing Protocol (AMQP) Working Group, an organization focused on the development of the AMQP specification. AMQP is an open Internet Protocol for Business Messaging designed in collaboration by members of the AMQP Working Group.
It is interesting to note, as the press release seems to indicate, that this decision was a result of pressure from the industry and members of the group.
Microsoft is joining the AMQP Working Group at the request of its members, including several of Microsoft’s customers in the financial services industry, in order to support the development of an open industry standard for ubiquitous messaging.
Sam Ramji, senior director of platform strategy at Microsoft said
By joining the AMQP Working Group, Microsoft is aiming to contribute to the development of the specification in ways that will best promote interoperability for existing market implementations and provide customers with increased choice.
The release goes on to showcase positive reactions from members of the working group, such as Paul Fremantle, CTO of WSO2, Pranta Das, technical leader for Cisco Systems Inc., Adrian Kunzle, head of engineering and architecture at J.P. Morgan and Red Hat.
The expectation is that this move will strengthen the grass-roots AMQP standardization movement.
In this interview, Jesper Boeg, author of the new InfoQ book – Priming Kanban, discusses the keys to using Kanban effectively, and how to get started if you are currently using other approaches.
John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.
Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.
Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.
Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).
Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.
Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
1 comment
Watch Thread Reply