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 Abel Avram on Jan 31, 2009
In this interview made by InfoQ’s Rob Bazinet during RubyFringe 2008, Dan Grigsby talks about programming and entrepreneurship, how a programmer can take his idea and transform it into a successful product.
Watch: Dan Grigsby Shares Secrets of Successful Entrepreneurship (20 min.)
A successful entrepreneur himself, Dan has a pool of ideas to choose from all the time, and he starts by partially implementing some of them, then he tests how they are received. If the idea is well received, then he invest more time and money in it or it sells it to someone else.
When starting to work on a new idea, Dan suggests not to go alone. He personally needs someone to share his thoughts with, to rely on, and to work with. Going alone takes way too much determination.
Also, it is important to know when to quit a failing idea. If one quits too soon, he might miss a big opportunity that was just not developed enough. If one quits too late, he will waste too much time and resources. Having someone else to partner with also helps to choose the right moment to quit, he says.
Dan also talks about getting new ideas. He does not get them from technical sources but rather from the surrounding society and culture. He notices a need, reflects a long time upon it, then acts.
Free Gartner Cloud Service Brokerage Report
Mobile and the New Two-Tiered Web Architecture
Agile Practices to Improve Project Management Organization (PMO) Effectiveness
Fair Trade Software Licensing - A Guide to Neo4j Licensing Options
Agile Maturity Model Applied to Building and Releasing Software
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.
No comments
Watch Thread Reply