InfoQ Homepage Culture & Methods Content on InfoQ
-
Catching up with Nuxeo: Switching from Python to Java
Back in 2006 InfoQ covered a story about Nuxeo, an open source Enterprise Content Management (ECM) specialist company, who had announced that it was changing its core technology platform from Python to Java. Four years on we caught up with Eric Barroca, CEO at Nuxeo, to find out how that conversion went, and to explore their new technology stack and position in the ECM industry.
-
Working with the Product Backlog
Roman Pichler discusses the product backlog along with techniques for effectively grooming it. Complicated applications of the product backlog are covered as well as how to handle nonfunctional requirements and how to scale a product backlog for large projects. This is a chapter excerpt from Roman's book: Agile Product Management with Scrum.
-
Ars Magna: the revolution is overdue
This essay is an intentionally provocative and controversial call for a real revolution in how we conceive of and practice software development. The intent is to stimulate discussion.
-
Skills for Scrum Agile Teams
The skills required to be hyper-productive in agile projects are different from those required by a traditional one. This article identifies behavioral and technical skills required for a team to have that edge. Anyone who acquires these "delta" traits should be equipped with the right set of behavioral and technical skills, which enable them to work effectively in an agile project.
-
Manager 2.0: The Role of the Manager in Scrum
Scrum defines just three roles, Product Owner, Scrum Master, and Team - not Manager. Pete Deemer explores the consequences for Managers, how the managerial role might be redefined (including a sample job description), and appointing the manager as Scrum Master.
-
A collaborative approach for real-world BPM
Bernd Ruecker explores how to achieve a better Business-IT alignment when developing BPM solutions. He describes a methodology which uses BPMN-based process model as center for collaboration where users can discuss and link requirements, business rules or other artifacts, visualize development status, specify business driven test scenarios and much more.
-
The Limits of Agile
The problems faced by teams that are attempting Agile in non-traditional settings aren't that Agile principles are inapplicable, nor that the feedback cycle is doomed to failure; but rather, outside of a certain Agile sweet-spot there are additional barriers and costs to applying Agile techniques. None of these obstacles prevents Agile in itself but each increases the cost of getting to Agile.
-
The Science of Learning: Best Approaches for Your Brain
Why don't people understand your idea in a meeting? Why does the developer you're mentoring still not get it? Why do attendees in your course only learn 10% of the material? We are all teachers in some way, yet only professional educators receive training in this area. This article discusses lessons from neuroscience and how they can be applied to Agile Software Development and beyond.
-
Success Factors for Systematic Reuse
Systematic reuse requires the interplay of people, process, and technology decisions executed within the context of real world constraints. Are there success factors that will make a difference to reuse? This article offers five success factors that will help capture domain variations, ease integration, delve deeper into design context, work effectively as a team, and manage domain complexity.
-
Who Moved my Product Value?
At the outset, it seems like agile is all about short-term focus and a product life cycle is typically the polar opposite – it runs the total gamut in the spectrum that is the life of the product, starting from incubation to end-of-life. So, how does one attribute the relationship between the two? This is where product value comes in.
-
Agile Team Meets a Fixed Price Contract
Fixed price contracts are evil - this is what can often be heard from agilists. On the other hand those contracts are reality which many agile teams have to face. But what if we try to tame it instead of fighting against it? How can a company execute this kind of contract using agile practices to achieve better results with lower risk? This article will try to answer those questions.
-
Fred Brooks on The Design of Design: Interview and Excerpt
A review of Frederick P. Brooks' latest book, The Design of Design. Few individuals have had as much influence on the 'practice' of software development and this book of loosely coupled essays on the essence of design, design process, and the development and nurturing of great designers extends and enhances previous contributions to the field. The review is enhanced with an interview and excerpt.