Atlassian spent almost a year on improving JIRA project management tool. What has been done and what was expected for 6.0 version?

When last we spoke, I discussed some of the pleasant discoveries that I had in my initial pair programming outings.  In this post, I'd like to share some of the pain points I experienced, my thoughts on mitigating them, and some additional thoughts on when pair programming might be more or less appropriate.

A fair question to ask is why should your organization consider adopting the Disciplined Agile Delivery (DAD) process framework.  I believe that there are several clear benefits to doing so:

Some commonly accepted ideas and best practices aren’t important: if you don’t follow them, nothing bad will happen to you and your project will still succeed, but there are a couple that you are better off not following at all.

Waterfall model follows application development in phases with checkpoint and deliverable documents in each checkpoint. It advocates rigours project management, strategy and processes to track the status. The main drawback is that it require more than 80% project understanding before kick off the project which is impossible in major cases. Cause of volatile requirements and understanding business feels, 80% of software projects using this methodology fail to meet their objectives.

Testing has a body of theory that helps its manageability and scalability. Many of the principles deserve to be borrowed into DevOps

The Economics of Software Quality, a book by Capers Jones and Olivier Bonsignour, provides solutions to quantify Software Quality which can help you to manage software development and maintenance. It contains software quality data that you can use to build a business case to improve the quality of your software and technical debt, understand what drives quality, and decide upon processes and techniques that can help to improve the quality performance of your organization.

Our behavior is always a reaction to the system around us. Let us take an example of an Agile team working on a project, and as we know its behavior would be determined by the stakeholders, leaders, enterprise culture around them.

When creating something of value, the first people we care about are those who will get value from the product we create. I call these Consumers. These are the users and those who are affected by the work of the users.

Do you know what a Sprint Review is for, and how it differs from a Retrospective? In this article we look at what a Sprint Review is meant to be, why it is important, how it differs from a Retrospective, and what you can do to make sure one actually happens.

Employing a collaborative workshop, and following the process described in this article creates an initial Product Canvas that allows you to focus on solution validation – building the product with the right user experience and features.

I gave a talk at Devs in the ‘Ditch last week when I was in London. I posted the slides on slideshare: Overcoming Three Pitfalls of Transitioning to Agile.