{"id":20,"date":"2018-11-05T08:45:07","date_gmt":"2018-11-04T22:15:07","guid":{"rendered":"http:\/\/blogs.flinders.edu.au\/digital-research-services\/?p=20"},"modified":"2019-02-13T14:59:31","modified_gmt":"2019-02-13T04:29:31","slug":"demystifying-agile","status":"publish","type":"post","link":"https:\/\/blogs.flinders.edu.au\/digital-research-services\/2018\/11\/05\/demystifying-agile\/","title":{"rendered":"Demystifying Agile"},"content":{"rendered":"

\ufeff<\/span>People who work in Information Technology often get accused of using too many acronyms and esoteric concepts. Today we would like to take the time to explain a way of working that you may of heard of and that we personally love \u2013 Agile.<\/p>\n

So what is Agile?<\/strong><\/p>\n

\"\"<\/p>\n

Agile isn’t just getting together for 15 minute team meetings every day (stand-ups) or using a Trello board. Infact agile isn’t even a noun – it\u2019s an adjective.<\/span><\/p>\n

When used to talk about software development (or any process that that creates an outcome really)\u00a0 it\u2019s a set of\u00a0<\/span>values\u00a0<\/span><\/strong>and<\/span><\/strong>\u00a0principles<\/span><\/strong>\u00a0that forms the approach in how the work will be delivered.<\/span><\/p>\n

The Four Values (of Agile Software development)<\/span><\/strong><\/p>\n

1.Individuals and Interactions Over Processes and Tools<\/span><\/p>\n

Valuing people more highly than processes or tools is easy to understand because it is the people who respond to business needs and drive the development process. If the process or the tools drive development, the team is less responsive to change and less likely to meet customer needs. Communication is an example of the difference between valuing individuals versus process. In the case of individuals, communication is fluid and happens when a need arises. In the case of process, communication is scheduled and requires specific content.<\/span><\/p>\n

\u00a0<\/span><\/p>\n

2. Working Software Over Comprehensive Documentation<\/span><\/p>\n

Historically, enormous amounts of time were spent on documenting the product for development and ultimate delivery. Technical specifications, technical requirements, technical prospectus, interface design documents, test plans, documentation plans, and approvals required for each. The list was extensive and was a cause for the long delays in development. Agile does not eliminate documentation, but it streamlines it in a form that gives what is needed to do the work without getting bogged down in minutiae.<\/span><\/p>\n

3.Customer Collaboration Over Contract Negotiation<\/span><\/span><\/p>\n

Negotiation is the period when the customer and the product manager work out the details of a delivery, with points along the way where the details may be renegotiated. Collaboration is a different creature entirely. The Agile Manifesto describes a customer who is engaged and collaborates throughout the development process, making. This makes it far easier for development to meet their needs of the customer. Agile methods may include the customer at intervals for periodic demos, but a project could just as easily have an end-user as a daily part of the team and attending all meetings, ensuring the product meets the business needs of the customer.<\/span><\/p>\n

4.Responding to Change Over Following a Plan<\/span><\/p>\n

Traditional software development regarded change as an expense, so it was to be avoided. The intention was to develop detailed, elaborate plans, with a defined set of features and with everything, generally, having as high a priority as everything else, and with a large number of many dependencies on delivering in a certain order so that the team can work on the next piece of the puzzle. Agile\u2019s view is that changes always improve a project; changes provide additional value.<\/span><\/p>\n

\u00a0<\/span><\/p>\n

The Twelve Principles<\/span><\/strong><\/p>\n

    \n
  1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.<\/span><\/li>\n
  2. Welcome changing requirements, even late in\u00a0development. Agile processes harness change for\u00a0the customer’s competitive advantage.<\/span><\/li>\n
  3. Deliver working software frequently, from a\u00a0couple of weeks to a couple of months, with a\u00a0preference to the shorter timescale.<\/span><\/li>\n
  4. Business people and developers must work\u00a0together daily throughout the project.<\/span><\/li>\n
  5. Build projects around motivated individuals.\u00a0Give them the environment and support they need,\u00a0and trust them to get the job done.<\/span><\/li>\n
  6. The most efficient and effective method of\u00a0conveying information to and within a development\u00a0team is face-to-face conversation.<\/span><\/li>\n
  7. Working software is the primary measure of progress.<\/span><\/li>\n
  8. Agile processes promote sustainable development.\u00a0The sponsors, developers, and users should be able\u00a0to maintain a constant pace indefinitely.<\/span><\/li>\n
  9. Continuous attention to technical excellence\u00a0and good design enhances agility.<\/span><\/li>\n
  10. Simplicity–the art of maximising\u00a0the amount\u00a0of work not done–is essential.<\/span><\/li>\n
  11. The best architectures, requirements, and designs\u00a0emerge from self-organising\u00a0teams.<\/span><\/li>\n
  12. At regular intervals, the team reflects on how\u00a0to become more effective, then tunes and adjusts\u00a0its behaviour\u00a0accordingly.<\/span><\/li>\n<\/ol>\n

    \u00a0<\/span><\/p>\n

    What does this mean for DRS? \u00a0It means that our focus is on collaborating with our customers to understand their needs and prioritise our work to deliver the highest value to our customers. It means that in every step of our process we try to put customer value first and strive to deliver value quickly through iterative cycles. It means we take the time to frequently review how we are working as a team and with our customers and ask ourselves \u2018is there anything we could improve?. We welcome feedback and seek it out because as Mark Twain once said\u00a0\u2018Continuous improvement is better then delayed perfection.\u2019<\/em><\/p>\n

    <\/h2>\n","protected":false},"excerpt":{"rendered":"

    \ufeffPeople who work in Information Technology often get accused of using too many acronyms and esoteric concepts. Today we would like to take the time to […]<\/p>\n","protected":false},"author":1587,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[42,88,1],"tags":[],"class_list":["post-20","post","type-post","status-publish","format-standard","hentry","category-agile","category-drs","category-drs-blog-post"],"post_mailing_queue_ids":[],"_links":{"self":[{"href":"https:\/\/blogs.flinders.edu.au\/digital-research-services\/wp-json\/wp\/v2\/posts\/20","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.flinders.edu.au\/digital-research-services\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.flinders.edu.au\/digital-research-services\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.flinders.edu.au\/digital-research-services\/wp-json\/wp\/v2\/users\/1587"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.flinders.edu.au\/digital-research-services\/wp-json\/wp\/v2\/comments?post=20"}],"version-history":[{"count":0,"href":"https:\/\/blogs.flinders.edu.au\/digital-research-services\/wp-json\/wp\/v2\/posts\/20\/revisions"}],"wp:attachment":[{"href":"https:\/\/blogs.flinders.edu.au\/digital-research-services\/wp-json\/wp\/v2\/media?parent=20"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.flinders.edu.au\/digital-research-services\/wp-json\/wp\/v2\/categories?post=20"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.flinders.edu.au\/digital-research-services\/wp-json\/wp\/v2\/tags?post=20"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}