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 Jonathan Allen on Nov 28, 2007
XNA Game studio is a game development toolkit that supports both Windows and the XBox 360. The initial edition was targeted directly at hobbyists and released as an extension to C# Express Edition.
The beta for XNA 2.0 brings the toolkit closer to the world of professional developers. The number one feature is that it now supports all versions of Visual Studio 2005. This unlocks tools such as integrated source control and testing frameworks. Multi-threaded debugging is enhanced and developers can use any VS Add-In they may have.
Another feature of XNA 2.0 is a tool for converting between Windows and XBox projects. While it may not eliminate the need to keep separate project files for the two platforms, it should at least make multi-targeting a bit less painful.
Speaking of projects, XNA 2.0 offers a new project type called "integrated content project". This allows developers and graphic artists to separate the game assets from the rest of the runtime and has support for the XNA Framework Content Pipeline.
Several APIs have been added or enhanced. For example, networking support has been added to allow for multiplayer games. This even supports games in which some players are on Windows while others are using an XBox.
Using Drools? See what you're missing! Get the Power of Drools with the Assurance of Red Hat
Agile Practices to Improve Project Management Organization (PMO) Effectiveness
Agility at scale, become as agile as you can be
Improve Java Garbage Collection, Runtime Execution, and JVM visibility with Zing
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