This article originally appeared in the March 2013 edition of Web and PHP magazine and is republished with permission.
Last month, I wrote about the need for development teams to develop increments of functionality that are “done” but what does that mean exactly? This article will explore the concepts of the definition of ready and the definition of done and will help you better understand how using them can help you successfully deliver increments of functionality in a sprint.
This article originally appeared in the February 2013 edition of Web and PHP magazine and is republished with permission.
On Scrum projects, teams talk about delivering a working increment of functionality every sprint but what does this mean exactly? Do teams need to deliver to a production environment every sprint? This may work for maintenance projects, but what does this mean for new projects starting from scratch? What kind of teams do you need to build increments of functionality every sprint? In this article, we will discuss cross functional teams, increments of functionality and minimum feature sets.
This article originally appeared in the December 2012 edition of Web and PHP magazine and is republished with permission.
Many web design firms work on too many projects simultaneously. When these firms start using agile software development practices, it forces them to look for different solutions to develop and meet the needs of their customers. This article presents ideas to consider if you want your web development teams to focus on one project at a time.
Photo by Financial Times / CC BY
What stage does your agile team gravitate around? Are you leading a Stage 2 team where the center of gravity is life sucks? Or are you in a tribe of high performing Stage 3 achievers that do not play well together? This week, as part of my continuing series of articles supporting my Tribal Agility talk, I will present some easy signs to help you identify the current stage of your Agile team. To learn more about these signs, you will have to read on.
In my last blog post, I wrote an introduction to triads. The popular question I got by e-mail from a few readers was: “Nice idea, but how do I apply this in real life?” As part of my continuing series of articles to support my Tribal Agility talk, I will write about building triads in agile teams this week. Are you working in an Agile environment with a stage two tribe? Would you like to use triads to break through collaboration barriers? To learn more, I invite you to read on.
Technology for distributed collaboration for application lifecycle management has come a long way in the last few years. Email and conference calls used to be the main ways to allow team members to work together across great distances, but that is no longer true. Here project managers will learn about some modern day uses of tools that will have your virtual team members communicating as effectively as if they were sitting face to face…
Read the full article at Search Software Quality at Techtarget.com by clicking here.
The biggest challenge many teams new to Scrum face is to understand when they are over-committing themselves during the sprint planning meeting. Before doing any sprint planning, the first thing teams should do is identify their sprint capacity, which is the number of hours they are available to work on backlog items during the sprint.
Read the full article at Search Software Quality at Techtarget.com by clicking here.
I spent the day at Agile Coach Camp in Montreal today. It was my first Open Space experience and I thought it was really amazing. At the end, they asked us to write a letter to ourselves, which we will receive as an e-mail in three or four weeks. They suggested writing about our experience, what we learned about ourselves and others and what we will be doing next. Sounded to me like they were asking me to write a blog post! To learn more about my Agile Coach Camp experience, please read on!