Developer

Balancing front-end and back-end work

Submitted by Barnaby Golden on Mon, 27/05/2019 - 12:07

Developer

Sometimes a team finds themselves with requirements that require a lot of back-end development and a small amount of front-end work. If the team has specialist front-end and back-end developers then it may be tricky to balance the workload.

One approach I have seen work is to initially stub the back-end functionality before doing the detailed development work.

These are the steps the team takes:

User stories are more important than epics and themes

Submitted by Barnaby Golden on Wed, 30/01/2019 - 17:18

Waterfall

Scrum teams take user stories into sprints.

For many teams that is the end of the conversation. They do not need anything else to describe the work they are doing and the requirements they plan to do in the future.

For other teams, particularly those with a long product backlog, it may be beneficial to use other terms for requirements. Terms like 'epic' and 'theme'.

Products versus Projects

Submitted by Barnaby Golden on Mon, 18/04/2016 - 15:58

 

Favour a product approach over a project approach

Software development has traditionally been done in projects.

Wikipedia describes a project as:

In contemporary business and science, a project is an individual or collaborative enterprise, possibly involving research or design, that is carefully planned, usually by a project team, to achieve a particular aim.

Scrum myths

Submitted by Barnaby Golden on Fri, 27/02/2015 - 11:33

 

The following are some common Scrum myths.

 

Velocity is a measure of performance

Isn't a higher velocity a sign of a more productive team?

The Scrum guide is very clear that velocity is purely about establishing the likely capacity of a team for future sprints. The actual value is irrelevant, it is the predictability that is important.

 

© Copyright 2018 bhgagile Limited

Paperblog

Software Development Blogs - BlogCatalog Blog Directory