The Latest

For development, a production application should be fully baked and not in what would be considered a “development” state. Tracy Ragan explains that frequent releases are a basic requirement of rapid development methodologies like agile and this impacts the way in which development teams and production control teams must interact.

In classic Scrum textbooks, the Product Owner (PO) permanently hangs out in the agile team room, churning out a stream of user stories, regularly prioritizing the backlog, deciding color schemes for screen design-all while keeping the team

We've all been there. You work incredibly hard to develop a feature and design tests based on written requirements. You build a detailed test plan that aligns the tests with the software and the documented business needs.

Even though team collocation is strongly recommended in agile methodologies, a distributed team is often required in the real world today. What is so important about collocating anyway?

If you are managing your portfolio using projects, and not products, you may be missing opportunities to deliver more business value to your organization.

You're familiar with agile and, perhaps, practicing Scrum. Now you're curious about Kanban. Is it right for your project? How does Kanban differ from Scrum and other agile methodologies?

Although many of us want to use only agile practices, we often work alongside teams with strong waterfall traditions.