This Is A Custom Widget

This Sliding Bar can be switched on or off in theme options, and can take any widget you throw at it or even fill it with your custom HTML Code. Its perfect for grabbing the attention of your viewers. Choose between 1, 2, 3 or 4 columns, set the background color, widget divider color, activate transparency, a top border or fully disable it on desktop and mobile.

This Is A Custom Widget

This Sliding Bar can be switched on or off in theme options, and can take any widget you throw at it or even fill it with your custom HTML Code. Its perfect for grabbing the attention of your viewers. Choose between 1, 2, 3 or 4 columns, set the background color, widget divider color, activate transparency, a top border or fully disable it on desktop and mobile.
­

User Roles, Personas and why they are needed

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 to impact revenues. Agile projects focus on the importance […]

By |June 5th, 2016|Agile, Scrum|0 Comments

Creating the Product Backlog

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 ? Well, this approach makes a number of […]

By |June 5th, 2016|Agile, Scrum|0 Comments

What does a good User Story look like?

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 main types of dependency:

Order Independence
Ideally stories should be […]

By |June 5th, 2016|Agile, Scrum|0 Comments

Top 5 reasons to use Agile User Stories

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 documenting requirements? Below we discuss some of […]

By |June 5th, 2016|Agile, Scrum|0 Comments

What is an Iteration?

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 iteration varies from one project to another […]

By |June 5th, 2016|Agile, Scrum|0 Comments

What are Scrum Artefacts?

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.

The Scrum Artefacts form a group of written records […]

By |June 5th, 2016|Agile|0 Comments

What is the Product Backlog?

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). Usually in Scrum PBIs are formulated as User […]

By |June 5th, 2016|Agile|0 Comments

Introduction to User Stories

A User Story is a requirement formulated as a brief statement that describes the required system behaviour from a specific users perspective as well as the benefit obtained from its implementation. Importantly, each User Story provides some functionality that is of value to the end-user or purchaser of the system.  Below is an example of what a User […]

By |June 5th, 2016|Agile|0 Comments