Apium Hub

Table of Contents

Introduction

In the list of activities in the Scrum software development life cycle ranked by their popularity amongst developers, “attending meetings” is perhaps locked in a perpetual battle only with “writing documentation” for the position of last place. It’s quite understandable: meetings can easily become very boring – especially when a participant does not have anything to contribute to the meeting at hand – and are often perceived as having little value (if at all) compared to conducting actual code-writing in the software development project. However, these meetings can and do provide value to the project, even if the members of the team do not perceive it:

Sprint refinements enable a product owner and the team to plan out development tasks in the weeks/months to come as well as identify whether any task might need further examination and/or design. Sprint plannings define

To read the full article click on the 'post' link at the top.