In Scaled Agile understanding the overall capacity of your Agile Release Train (ART) is extremely important to determine what is achievable and when by a collection of Agile teams. Scaled Agile Estimation Philosophy and Mindset In my articles, I typically write about my experiences of implementing SAFe in [...]
SAFe (Scaled Agile Framework) is one of a handful of Agile@Scale frameworks used to help multiple Agile teams organise and coordinate to deliver on a vision. No Scaling Framework should be used where it can be avoided, as scale almost inevitably results in a reduction in overall Agility. [...]
Three deadly traps to avoid when implementing the Scaled Agile Framework. You have a large vision for your organisation, the problem is how do you execute upon this vision when the implementation of that vision may span disparate teams, multiple systems, divisions and even political fiefdoms. SAFe is [...]
On traditional projects, requirements are often gathered without taking into consideration the different types of users that may interact with the system. This is problematic, as functionality which may be useful for a specific type of user may be left out, reducing value for that user with the potential [...]
Traditional requirements gathering techniques focus on obtaining the maximum amount of information from as wide a user base as possible early in the project lifecycle. The more effort we put into gathering requirements upfront, the more likely we are to build what the customer will want, right ? [...]
User Stories are the catalyst for the development process so it is essential to ensure that they are well formed. Bill Wake has suggested the famous INVEST acronym as a guideline for good stories. I for Independent A story should ideally be independent of other stories; there are three [...]
User Stories originated with Extreme Programming and represent a significant shift from the large documents that make up requirements in traditional projects.User Stories are small 'snippets' of business focused requirements. So why should we even bother with User Stories? How are they an improvement on traditional forms of gathering and [...]
Iteration is a unit of time during which user-valued functionality is created. It is the fundamental unit into which a project is divided. In other words, an Agile project is a series of iterations that continue, back to back, until the project concludes successfully. The exact length of [...]
An artefact is defined by the Oxford dictionary as 'An object made or modified by human workmanship, as opposed to one formed by natural processes'. The Scrum Methodology has three artefacts that are created by the team as a by-product of following the Scrum Process and performing its Ceremonies. [...]
Within Scrum one of the key artefacts that drives the delivery process is the Product Backlog. The Product Backlog contains a list of features or items that are ordered according to their business value. Items in the Product Backlog are frequently referred to as PBIs (Product Backlog Items). [...]
