Amber Hunt - Sprint 3 Paper 2 - Planning the release

TABLE OF CONTENTS

1.1   INTRODUCTION

1.2   PLANNING THE RELEASE SCHEDULE

1.3   DELIVERING WITHOUT SCOPE

1.4   INVITING THE RIGHT GROUPS

1.5   CONCLUSION

1.1 Introduction

In Agile, planning the release schedule, delivering without scope, and inviting the right groups can be a bit hectic, but it can nonetheless, be done. These things play a major role in driving productive agile meetings. Agile environments are faster paced but still require organizing and order. The steps above, will help in the understanding of planning the release schedule within an agile project. 1.2 Planning the release schedule

A release plan depicts how much scope the agile team plan to have by the deadline. With planning a release schedule, the time limit is definite. A release backlog is an agreement with the product owner. It ends up committing to solid deliverable sprint dates. Release backlogs are “slippery slopes” back to waterfall. (Lynda.com – from LinkedIn, 2017) It is important to always remember that, else one can fall into the traditional project style.

1.3 Delivering without scope

In an agile environment, the scope is known as the variable. Traditional projects, the scope is tied in with the schedule and budget. If one is changed, all must change. Agile, cost and schedule come first. The sponsor decides when they want the product finished and how much they will pay. After, then the team deals with the scope accordingly. In agile, the team has wiggle-room to top-up the scope with the most important elements.

1.4 Inviting the right groups

Inviting the right groups is extremely important in an agile project. From the very beginning, the scrum master might divide the room into sitters and talkers. This helps to keep things going. A sitter is a person who is interested in activities, but does not have much to say. A talker on the other hand is a person who is supposed to be active and contributing in their team. Dividing into these teams help meetings/activities to go by on schedule/on time.

1.5 Conclusion

It is vital to keep in mind that the authority of agile comes from its potential to make recurrent changes. All the guidelines stated above, are there to make agile planning easier. The release is about value, not features. Delivering the scope is the opposite of what it was in a traditional project. And inviting the right group members can be crucial.

Reference

Google.com. (2017). ''planning the release schedule - Google Search''. [online] Available at: https://www.google.com/search?q=planning+the+release+schedule&rlz=1C1CHWA_enUS628US628&source=lnms&tbm=isch&sa=X&ved=0ahUKEwiVucTBqcbXAhUM8CYKHb-yByEQ_AUICygC&biw=1517&bih=735#imgrc=6lorYBKzjXtf8M: [Accessed 17 Nov. 2017].

Lynda.com - from LinkedIn. (2017). Delivering without scope. [online] Available at: https://www.lynda.com/Business-Skills-tutorials/Delivering-without-scope/175075/437995-4.html [Accessed 16 Nov. 2017].

Lynda.com - from LinkedIn. (2017). Inviting the right groups. [online] Available at: https://www.lynda.com/Business-Skills-tutorials/Inviting-right-groups/175075/437996-4.html [Accessed 16 Nov. 2017].

Lynda.com - from LinkedIn. (2017). Planning the release schedule. [online] Available at: https://www.lynda.com/Business-Skills-tutorials/Planning-release-schedule/175075/437994-4.html [Accessed 16 Nov. 2017].