The Latest
How Scrum Increases Productivity: The Product Owner[article] In Scrum, the Product Owner role is the one person responsible for the project's vision and direction. He or she leads by communicating with the team, outlining chunks of work through the composition of product backlog items and then prioritizing those items. |
||
Scrum and SVO-p[article] Scrum is unique in that the management method is consistently direct. All communication in authentic Scrum is concise, direct and clear. Scrum encourages responsibility. The daily stand-up meeting actively encourages personal responsibility to execute on specific work, and to be accountable to the Team. The three questions of Scrum are questions related to accountability for specific commitments. |
||
A Second Look at "Requirements Come Second"[article] My article, "Requirements Come Second," in a recent issue of Agile Journal caused something of a fuss. The piece was picked up by several more sites and was widely commented on - both on websites and in my inbox. I'm not entirely surprised by this reaction, I've been discussing this research for a year or so now and often find it surprises people. Given this level of interest it is worth looking at how people responded. It is also worth restating the key message: Requirements are an essential part of maximizing business value, but when an organization is struggling with effectiveness it is best to start change by improving delivery. |
||
Executive Strategies for Agile Transition - Charlie Kennedy and Tom Paider[article]
Podcast
Bob interviews Charlie Kennedy and Tom Paider about Executive Strategies for Agile Transition. |
||
Continuous Integration and Testing[article] Lisa Crispin explains in this article how CI has become an absolute necessity for any software development team in this day and age. For those who have yet to fully embrace CI, this article gives you some great reasons you should, along with some helpful resources to get you started. |
||
What's So Special About Specialists?[article] If two projects in your organization require specific expertise that only one employee has, what do you do? Projects need to stay on track, but one person certainly can't be everywhere—or even two places—at once. In this column, Johanna Rothman shares a story of an organization stuck in the specialist mindset and offers some tips on how to escape if you're stuck there, too. |
||
Do You Know Why You Are Doing That?[magazine] It's easy to get caught up in the inertia of a project and forget to ask exactly what we are developing, who our customers are, and what their goals with our software might be. Few software projects have the time and budget to figure out what their project is through trial and error. Getting clarity on project focus not only helps productivity, working to create software that people actually need increases our chances for success. |
||
Tips and Advice - Beyond The Team - Sanjiv Augustine[article]
Podcast
Bob interviews Sanjiv Augustine about agile transitions. |
||
Deep Agile Conference 2009 - Nancy Van Schooenderwoert, Jack Ganssle[article]
Podcast
A podcast about the Deep Agile 2009 conference. |
||
Tips and Advice - Team Rooms[article]
Podcast
Many organizations know the importance of nurturing culture in order to create happy and productive teams, but how many have set aside team rooms for these groups to accomplish their builds? In this podcast, Bob Payne get the opinion of someone who agrees with this added bonus for teams. |
||
Feature Injection: Part One[article] We are leaving the "last responsible moment" for a while. This month we start a discussion of Feature Injection, an analysis process based on real options and Kolb's circle of learning. The first episode ( of five ) introduces the "Information Arrival Processes. |
||
Tips and Advice - Listener Email - Self Organizing Teams[article] In this podcast, Bob and George respond to a listener-submitted email by providing a better understanding of what truly makes self-organizing teams. We encourage you to listen to this informative discussion to make sure everyone is on the same page with what these teams are truly made of. |
||
How Scrum Increases Productivity[article] Scrum has become the most popular exponent of agile software development frameworks. Organizations-and those developing software, in particular-are drawn to Scrum for many reasons. They include its capacity to mitigate risk, facilitate frequent communication, reduce cycle time and cost, and deliver the right products to customers. From a managerial standpoint, Scrum's most appealing attribute is its ability to boost productivity through autonomous, hyper-performing teams. |
||
Agile Development Infrastructure—on Premises or in the Cloud?[article] How do companies face the challenge of setting up their infrastructure when they've just started agile development? One option is to move your infrastructure to the cloud. In this article, we help you decide what's the best fit for your team and project by addressing this issue head on. |
||
The GDM-Agile Paradox: Tips to Tap into the Capabilities of Agile in the Global Delivery Model[article] Agile is a development strategy that we have worked with for a number of years now. Lately, we've been getting a lot of questions from clients along the lines of: "I've got a project, I want to globally source it, can I use Agile Development?" Well, that depends. |