Implementing an Agile Project

Once an Agile project gets started, it is generally a self-sustaining process. However, there are certain practices in place to keep development functioning efficiently. With these guidelines in place, a Scrum team can stay on track and maintain productivity.

Deliverables

In an Agile environment, a “Deliverable” is a working piece of software that the Scrum team gives to the stakeholders. While a deliverable is not as useful on its own as it would be with the finished product, it does work alone. The biggest benefit of deliverables is that stakeholders get to see and use real software during the development process. Instead of waiting until the very end of the contract period to see what developers have created, they get regular updates to their working software.

But how do deliverables have any bearing on the implementation of an Agile project? In this regard, deliverables are the basic unit of completed software. Instead of getting vague updates from the organization about how many hours of work they’ve logged, customers get a concrete indicator of completed development. Each new feature is one that they can physically use. This gives an obvious metric for the pace of development. The Scrum team can look back and see how many and which deliverables they finished in each Sprint.

The Scrum team creates these deliverables simply by finishing tasks for a request. Some tasks are part of a singular bigger deliverable, in the form of an epic. Other tasks are their own, individual deliverable. In either case, once a feature has been developed and tested, it is packed into the next version of software for the customer to use.

Recommended Further Reading

The following materials may assist you in order to get the most out of this course: