I’m now in my second role in which I’ve had the chance to introduce agile working practices to the team. In both roles, the projects and applications developed under scrum have been successfully shipped and accepted by the business. The success of the deliveries has been measured by: Functionality: The early visibility the business gained through the end of sprint demonstrations made sure that all the functionality the team developed stayed on track and provided . . .
What do task hours add to the overall process in scrum? This was a question that has arisen from all team members in both instances that I’ve helped teams switch over to scrum. The benefits of artefacts like the comparative story point estimation, the 2-week sprints, stand-ups and the end of sprint demo have been self-evident to the team, but as one I think every team member has expressed dismay when it comes to task . . .
There are many articles on the web about how to do good code reviews, with mostly all of them either discussing their merits or how to obtain maximum value from them. In a new role, I’ve recently helped introduce and roll out the agile process and to start with as part of each story we always added a task to “code review” all work. We made sure that differences from source control were used to . . .