Category

Agile Project Management

Cutting-edge Agile methodologies, software development techniques and project management practices.

 
avatar

Agile practitioners talk a great deal about the importance of breaking bad old habits and replacing them with muscle memory. Since you’re breaking down programmed, reflexive responses, you need more than words. You don’t reason with a habit. That’s why I often inject serious games as training exercises when I’m working with someone in the midst of an Agile transformation project. For one client, specialization within teams was a serious stumbling block to Agility. As long as Bob (not his real name) was the only person who could build a particular kind of critical component, Bob would be a choke point in every sprint. Other team members had similar specializations in platform issues, data formats, …

Read more

 
avatar

Many organizations start their Agile journey by adopting Scrum because it describes a good strategy for leading Agile software teams. Scrum, however, is only part of what is required to deliver sophisticated solutions to your stakeholders. Invariably, teams need to look to other methods to fill in the process gaps that Scrum purposely ignores. When looking at other methods, there is considerable overlap and conflicting terminology that can be confusing to practitioners as well as outside stakeholders. Worse yet, people don’t always know where to look for advice or even what issues they need to consider. To address these challenges, the DAD process decision framework provides a more cohesive approach to Agile solution delivery (see …

Read more

 
Lean, Devops and the Resurgence of the Industrialization of Software

One the constant tensions in our industry is the business need to make software more like manufacturing — highly predictable and controllable — and the reality that much of the software development lifecycle is not amenable to the process control techniques that are so effective in manufacturing. Software development is different than manufacturing in that: There is a wide range of uncertainty. Software efforts span from green field projects with little initial understanding of the needed system to bug fixes and small changes with very detailed specifications. There is an indirect relationship between the effort expended and value created. Generally, if one spends 10 hours painting a wall, one can expect there will a lot …

Read more

 
2014: The Failure of Agile Software Development is Taken Seriously

What happened in the past: Agile is all the hype in Software Development and the talk at the golf courses across the country. Consultancy and certification are booming and rumor has it that all software development projects will now end as a success: faster, cheaper, better. What is really going on: More and more software developers are realizing that agile is being implemented as a hype. Processes become iterative. Documents are replaced by tools that maintain a backlog. Customers are still at a far distance from teams. People are still called resources. Cheap labor is still used to “reduce costs”. A few honest managers are aware that nothing is really changing. Quality is not improving, …

Read more

 
A Focus on Organizations and Value Chains

If there was one major development in the Agile field in the last year or two, it’s been a shift of focus from teams and methodologies to organizations and value chains. I expect this development to gain more speed and depth in the next three years — becoming the major issue of the debate. I see three main threads within the focus on organizations and value chains emerging. These seem to address different needs and markets. The first thread is a tendency to “blueprint” an organization in order to facilitate Agile’s introduction. The “Scaling Agile Framework” belongs, in my opinion, in this group, as do the initiatives of the PMI. Despite a heated debate about …

Read more

My List

 Gil Broza | Dec 4, 2013  No Responses
Dec 042013
 
My List

In 2014… People will still call other people “resources.” Even to their face. Nominally Agile organizations will continue to administer performance appraisal schemes that emphasize the individual and downplay the team. Companies will continue to not train their developers in Agile engineering, because technical execution skills will remain off the radar. Technology managers and stakeholders will still assume that their teams ought to develop quality products faster than is realistically possible. Project managers will still struggle to come up with a good measure of Agile team productivity for their executives, and consultants will continue telling those project managers that they shouldn’t be measuring productivity. Bad meetings — and complaining about the number of meetings in …

Read more

 
avatar

If you visit an Agile conference these days, it’s hard not to hear talks like “Scrum within a RUP project” or “Agile in a Traditional Organization.” From a dogmatic Agile point of view, this reminds me a little bit of a veggie-stuffed beef recipe promoted as vegetarian food. From a management perspective, it means that you are only exploiting about 10% or 20% of the potential of Agile . Many consultants would consider such an implementation as failed, and I’m sure you will find a lot of “Scrumbut” practices in these organizations. But does that necessarily mean such an approach is bad? I don’t think so. To the contrary, a fast judgment of these approaches often …

Read more

 
Defined vs Ready Technology Adoption — The Future is Now (and Forever)

In the 20th century, companies waited until their industries and competitors fully vetted technologies before investing in even the most tried and true ones.  Technophobes believed that investing too early was indulgent and reckless.  Executives wore their late technology adoption strategies as badges of corporate honor.  Today, emerging technologies are ready for immediate deployment:  iPads are ready; Dropbox is ready; Skype is ready; ListenLogic is ready; Foursquare is ready; YouTube is ready. I predict that these and many other hardware and software technologies will be adopted without clear (or “validated”) requirements models, without the venerable SDLC, and even without rapid prototyping. I predict that technology adoption will turbo-charge into instant deployments.  The figure below summarizes defined …

Read more

Nov 202013
 
Serious Games Need Agile

In my last post, I talked about the ways in which serious games can fill a significant hole in Agile practices. Let’s turn that around and see how Agile can help serious games. Before we can get into the meat of that topic, it’s important to be clear about which serious games we’re going to be discussing. There’s a wide variety of game-like activities used for reasons other than entertainment (education, ideation, market research, etc. etc.), and not all of them can benefit from serious games equally, or even in the same ways. For our purposes, we’ll be focusing on three types: Software-based serious games in general. This is a pretty broad category, encompassing everything …

Read more

 
avatar

Within the world of Agile, architecture often seems misaligned or is a forgotten value-add to a project, especially in enterprise and large scale programs. However, an agile architecture can enable a business to deliver features faster and give them a competitive advantage. Coupled with SaaS and/or Cloud, it seems obvious that agile architectures are required. So what is the problem? Sometimes organizations struggle to define what exactly an agile architecture is, the value it can add to product delivery, and what artifacts are most useful and relevant. Is an agile architecture about supporting rapid scale-out, continuous delivery and deployment? Or is it an exercise in futility? How much value should an organization attribute to having …

Read more