10 Ways to Screw Up with Scrum and XP
Henrik Kniberg talks about 10 possible reasons to fail while doing Scrum and XP. Maybe the team does not have a definition of what Done means to them, or they don't know what their velocity is.
Tracking change and innovation in the enterprise software development community
Posted by Rob Thornton on Nov 09, 2006 11:26 AM
Two new articles are out bolstering the documentation on using JSR-170, the Java Content Repository API. The first on TheServerSide is a practitioner's perspective which has an informative FAQ and the second on onjava.com is an in-depth look at versioning and observation using JackRabbit.
TheServerSide's article, co-written by InfoQ's Chief Architect Alexandru Popescu, gives a good introduction to the JCR and how to get up and running with JackRabbit, the reference implementation available from Jakarta. While there are other tutorials available on getting started, the value in this one is the frequently asked questions section which answers common questions that arise where most tutorials end. The questions range from when to use the JCR as opposed to a filesystem or database, to a discussion of the pros and cons of using a single workspace or multiple ones.
OnJava has a new article that goes into depth on how to use two of the optional features defined in the JSR, versioning and observation. Versioning, in the context of JCR, is the ability to save the state of a node so that you can recall earlier states. Observation allows you to monitor the repository and take action when changes are made. This article describes how both are used, and is a follow-up to one mentioned in an earlier InfoQ post.
WebSphere Virtual Enterprise 3 minute demo
Spring App Platform, Java Concurrency/Multicore, Eclipse Mylyn and more @ QCon SF Nov 19-21
The Agile Business Analyst: Skills and Techniques needed for Agile
IBM software architect eKit: Grady Booch podcast, whitepapers, articles
Henrik Kniberg talks about 10 possible reasons to fail while doing Scrum and XP. Maybe the team does not have a definition of what Done means to them, or they don't know what their velocity is.
This article outlines 9 principles Marc Lammers discovered while building the world’s best field hockey team, mapping them to software development practices.
Michael Poulin explains the necessity for SOA governance to ensure an Enterprise SOA's success, relying on concepts from the OASIS SOA Reference Model and Reference Architecture.
This article covers setting up a RichFaces portlet using JBoss Portlet Container and JBoss Portlet Bridge, deploying a RichFaces portlet, and RichFaces capabilities.
This article discusses scalability worst pratices including The Golden Hammer, Resource Abuse, Big Ball of Mud, Dependency Management, Timeouts, Hero Pattern, Not Automating, and Monitoring.
Obie Fernandez shares his experience selling consulting services for both Thoughtworks and Hashrocket and give tips how Ruby developers can work with clients.
Jeffries and Hendrickson derive Agile practices from the natural laws of software development. They don't just say "Be Agile!", but they explain why Agile practices make perfect sense.
Jinesh Varia talks about the architecture of one of Amazon's web services called Alexa. Jinesh explains how Amazon has reached scalability, performance and reduced costs for the Alexa service.
No comments
Reply