Attachment J5 - Agile SDLC at the Library.pdf

Agile at the Library Welcome to Agile at the Library

Agile software development refers to a group of software development methodologies based on iterative development, where requirements and solutions evolve through collaboration between self-organizing, cross-functional teams. Agile methods or Agile processes generally promote a disciplined project management process that encourages frequent inspection, adaptation, and improvement, a leadership philosophy that encourages teamwork, self-organization and accountability, a set of engineering best practices intended to allow for rapid delivery of high-quality software, and a business approach that aligns development with customer needs and company goals. Agile development refers to any development process that is aligned with the concepts of the Agile Manifesto.

Why Agile Works

Agile software development provides opportunities to assess the direction of a project throughout the software development lifecycle (SDLC), including creating a vision for the product and visualizing the work required to make it. Planning allows teams to identify the amount of work needed for a shippable product and when the product can potentially be released. Regular cadences of work allow teams to deliver incrementally. By focusing on the repetition of abbreviated work cycles as well as the functional product they yield, development teams are able to provide finished product frequently and continuously improve on the way the work is completed. In waterfall, development teams only have one chance to get each aspect of a project right. In an agile paradigm, every aspect of development — requirements, design, etc. — is continually revisited throughout the SDLC. When a team stops and re-evaluates the direction of a project every two weeks, there’s always time to steer it in another direction.

Topics:

The Agile Manifesto 12 Principles of Agile

Agile Frameworks:

Scrum Kanban Scaling Agile at the Library DevOps https://staff.loc.gov/wikis/display/AT/The+Agile+Manifesto https://staff.loc.gov/wikis/display/AT/12+Principles+of+Agile https://staff.loc.gov/wikis/display/AT/Scrum

The Agile Manifesto - Agile At The Library - Wikis https://staff.loc.gov/wikis/display/AT/The+Agile+Manifesto 1/1

Dashboard / Agile at the Library

The Agile Manifesto

The Manifesto for Agile Software Development was created by a group of 17 experienced software development practitioners in 2001. Us their combined experience and expertise, and despite differing views, the signatories of the Manifesto were solidly in consensus on four values that comprise the whole of the document, which is as follows:

"We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:

Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan

That is, while there is value in the items on the right, we value the items on the left more."

Further Reading Agile Essentials

No labels https://staff.loc.gov/wikis/collector/pages.action?key=AT&src=breadcrumbs-collector https://staff.loc.gov/wikis/display/AT/Agile+at+the+Library?src=breadcrumbs-parent https://staff.loc.gov/wikis/display/AT/The+Agile+Manifesto https://www.agilealliance.org/agile-essentials/ http://www.atlassian.com/

12 Principles of Agile - Agile At The Library - Wikis https://staff.loc.gov/wikis/display/AT/12+Principles+of+Agile 1/1

Dashboard / Agile at the Library

12 Principles of Agile

The 12 Principles behind the Manifesto for Software Development are guiding practices that support teams in successful adaption and implementation of agility in software development.

1. Customer satisfaction by early and continuous delivery of valuable software.

2. Welcome changing requirements, even in late development.

3. Deliver working software frequently (weeks rather than months)

4. Close, daily cooperation between business people and developers

5. Projects are built around motivated individuals, who should be trusted

6. Face-to-face conversation is the best form of communication (co-location)

7. Working software is the primary measure of progress

8. Sustainable development, able to maintain a constant pace

9. Continuous attention to technical excellence and good design

10. Simplicity—the art of maximizing the amount of work not done—is essential

11. Best architectures, requirements, and designs emerge from self-organizing teams

12. Regularly, the team reflects on how to become more effective, and adjusts accordingly https://staff.loc.gov/wikis/display/AT/Agile+at+the+Library?src=breadcrumbs-parent https://staff.loc.gov/wikis/display/AT/12+Principles+of+Agile http://www.atlassian.com/

The Sprint Cycle - Agile At The Library - Wikis https://staff.loc.gov/wikis/display/AT/The+Sprint+Cycle 1/1

Dashboard / Agile at the Library / Scrum

The Sprint Cycle

The Sprint Cycle is a timeboxed interval in which the Scrum Team completes their work During a Sprint with Agile@Library, the Scrum Team works in three-week intervals, called Sprint Cycles, during which the team completes their work and participates in the following Scrum Ceremonies:

Sprint Planning – Day 1 Daily Standup – Days 2-14 Sprint Review – Day 15 Sprint Retrospective – Day 15

Days 2-14 are considered working days and should be devoted to completing the work pulled into the Sprint Backlog The Scrum Master may ask for a health check midway through the Sprint to ensure the Scrum Team feels confident about meeting the Sprint goal Backlog Refinement should occur at least twice during a single Sprint Cycle https://staff.loc.gov/wikis/display/AT/Agile+at+the+Library?src=breadcrumbs https://staff.loc.gov/wikis/display/AT/Scrum?src=breadcrumbs-parent https://staff.loc.gov/wikis/display/AT/The+Sprint+Cycle https://staff.loc.gov/wikis/display/AT/Core+and+Extended+Scrum+Teams https://staff.loc.gov/wikis/display/AT/Scrum+Ceremonies https://staff.loc.gov/wikis/display/AT/Sprint+Planning https://staff.loc.gov/wikis/display/AT/Daily+Standup https://staff.loc.gov/wikis/display/AT/Sprint+Review https://staff.loc.gov/wikis/display/AT/Sprint+Retrospective https://staff.loc.gov/wikis/display/AT/Sprint+Backlog https://staff.loc.gov/wikis/display/AT/Scrum+Master https://staff.loc.gov/wikis/display/AT/Backlog+Refinement http://www.atlassian.com/