The greatest strategy for project retrospectives

Software delivery teams often struggle to implement all outputs from a retrospective. Once a team is into their next sprint, the new backlog takes priority and what may have been agreed in the retrospective can be put onto the back burner. Starfish, a technique for retrospectives, helps the team to take accountability for retrospective outcomes to ensure they are achieved...

How to improve Agile software delivery with story maps

As part of an Agile delivery team, you may be familiar with the usual project constraints of budget, time and scope. All too often, one or more of these elements needs to be reduced to allow for project delivery. But how can you quickly find out how close you are to delivery? How can you decide at what point your product becomes a releasable MVP?

An introduction to testing and quality assurance

It’s human nature to make errors and therefore any developer working on a large piece of work will make errors along the way. Since the inception of high-level computer programming back in the 1950s, developers have been writing massive amounts of code to deliver a very specific function. Ultimately errors will occur, bugs can and will slip into the code, and as a result defects may appear in the software delivered to the end user.

5 simple tips on starting a new scrum team

As many companies within the IT industry move away from Waterfall/PRINCE 2 and more towards Agile/Scrum, it can be hard for project managers and Scrum teams to know what the best approaches are for a new Scrum team. There is a lot of information online that provides information about what Scrum is, what tools are available, and what the Scrum process is. I have worked in the digital/ IT industry as project manager/ business analyst since 2005 and have worked with Scrum since joining Inviqa at the start of February 2014. The transition has been a steep learning curve and in this article I will share some of the practices I have learnt to improve Scrum team efficiency.

Bugs and defects: why you should treat them differently

How many of you have wondered about the difference in bugs and defects? How many would argue they both are the same? And how do you define if an issue is within or out of the scope of a sprint? In this blog, I’d like to look at what defines a bug and a defect, why I think they are different, and the benefits for keeping them separate. While differentiating bugs and defects won’t address every issue within a sprint, having clear distinction for these terms definitely helps to keep your team focused on what you have agreed to deliver.

8 tips for avoiding vendor lock in

Vendor lock-in makes a customer dependent on a supplier for a product or service, and unable to use another vendor without substantial switching costs or inconvenience. While standards, bodies and an increased focus on interoperability have helped reduce the threat of application lock-in, web site and web application development can still be a minefield. In this article, we will look at eight ideas that can help companies avoid vendor lock-in, intentional or otherwise, when setting up new sites or systems.

Pages