Agile Development Specialization

Start Date: 07/04/2021

Course Type: Specialization Course

Course Link: https://www.coursera.org/specializations/agile-development

About Course

In this Specialization, you'll gain an understanding and appreciation of the principles and practice of agile management. You'll learn to coordinate all aspects of the agile development process, including running design sprints, managing teams, and fostering a culture of experimentation. In the final Capstone Project, you'll apply what you've learned to guide a real-world software development project to successful completion. UVA Darden

Course Syllabus

Agile Meets Design Thinking
Running Product Design Sprints
Managing an Agile Team
Hypothesis-Driven Development

Coursera Plus banner featuring three learners and university partner logos

Course Introduction

Drive to Value with Agile Methods . Master an adaptive approach to product development Agile Development Specialization In this Specialization, we will use the agile process to develop software. We will use the agile process to get a sense of what it is, what it is for, and how you can use it. We will also discuss different techniques for developing software. We will also look at how to think through your project plans and possible problems that may arise as a result. We’ll cover topics such as project initiation, project management, project monitoring, software quality, and software licensing. At the end of this Specialization, you will be able to: - implement agile projects into your own workflows - apply agile process techniques into your project plans - communicate with stakeholders - manage project scope and risk - use agile project initiation and management - use agile project monitoring and software qualityManagement, Quality Control, and Software Licensing To get the most out of this Specialization, you will need to do some of the activities outlined in the "About" section below. Also, you will need to complete the "What is", "Where is", and "What can I do" quizzes to pass the course. In this Specialization, we will use the agile process to get a sense of what it is, what it is for, and how you can use it. We will also discuss different techniques for developing software. We will also look at how to think through your project plans and possible problems that may arise as a result

Course Tag

Product Development Persona (User Experience) Agile Management Agile Testing Design Sprint

Related Wiki Topic

Article Example
Agile software development The term "agile" was first coined for this in 2001, in the "Manifesto for Agile Software Development ("Agile Manifesto")," and is usually written as "Agile" (with a capital "A").
Agile software development Organizations and teams implementing agile development often face difficulties transitioning from more traditional methods such as waterfall development, such as teams having an agile process forced on them. These are often termed "agile anti-patterns" or more commonly "agile smells". Below are some common examples:
Agile software development A survey performed by Version One found respondents cited insufficient training as the most significant cause for failed agile implementations Teams have fallen into the trap of assuming the reduced processes of agile development compared to other methodologies such as waterfall means that there are no actual rules for agile development. Agile development is a set of prescribed methodologies, and training/practice is a requirement.
Agile software development A similar survey, the State of Agile, is conducted every year starting in 2006 with thousands of participants from around the software development community. This tracks trends on the benefits of agile, lessons learned, and good practices. Each survey has reported increasing numbers saying that agile development helps them deliver software faster; improves their ability to manage changing customer priorities; and increases their productivity. Surveys have also consistently shown better results with agile product development methods compared to classical project management. In balance, there are reports that some feel that agile development methods are still too young to enable extensive academic research of their success.
Agile software development Organizations that adopt agile development see more frequent releases; which led to the concepts of continuous delivery and DevOps. While DevOps and agile software development both embody many Lean philosophies, such as collaboration and communication, they are distinct concepts. While agile principles represent a change in thinking, DevOps seeks to implement actual organizational cultural change.
Agile software development Popular agile software development frameworks include (but are not limited to):
Agile software development Agile methods have been extensively used for development of software products and some of them use certain characteristics of software, such as object technologies. However, these techniques can be applied to the development of non-software products, such as computers, motor vehicles, medical devices, food, clothing, and music; see Flexible product development. Agile methods have been used in non-development IT infrastructure deployments and migrations. Some of the wider principles of agile have also found application in general management (e.g., strategy, governance, risk, finance) under the terms business agility or agile business management.
Agile software development Agile methods support a broad range of the software development life cycle. Some focus on the practices (e.g., XP, pragmatic programming, agile modeling), while some focus on managing the flow of work (e.g., Scrum, Kanban). Some support activities for requirements specification and development (e.g., FDD), while some seek to cover the full development life cycle (e.g., DSDM, RUP).
Agile software development Development methods exist on a continuum from "adaptive" to "predictive". Agile methods lie on the "adaptive" side of this continuum.
Agile software development Some of the authors formed the Agile Alliance, a non-profit organization that promotes software development according to the manifesto's values and principles. Introducing the manifesto on behalf of the Agile Alliance, Jim Highsmith said,
Agile software development Agile development is supported by a number of concrete practices, covering areas like requirements, design, modelling, coding, testing, planning, risk management, process, quality, etc. Some notable agile practices include:
Agile software development The best agile practitioners have always emphasized sound engineering principles. As a result, there are a number of agile best practices and tools for measuring the performance of product development and teams.
Agile software development Because of the short iteration style of agile software development, it also has strong connections with the lean startup concept.
Agile software development Agile methodologies can be inefficient in large organizations and certain types of developments. Many organizations believe that agile methodologies are too extreme and adopt a hybrid approach that mixes elements of agile and plan-driven approaches. Some methods, such as Dynamic systems development method (DSDM), have combined elements of agile and plan-driven approaches in a disciplined way, without sacrificing the fundamental principles that make agile work.
Agile software development When agile software development is applied in a distributed setting (with teams dispersed across multiple business locations), it is commonly referred to as distributed agile development. The goal is to leverage the unique benefits offered by each approach. Distributed development allow organizations to build software by strategically setting up teams in different parts of the globe, virtually building software round-the-clock (more commonly referred to as follow-the-sun model). On the other hand, agile development provides increased transparency, continuous feedback and more flexibility when responding to changes.
Agile software development Agile methods have much in common with the Rapid Application Development techniques from the 1980/90s as espoused by James Martin and others. In addition to technology-focused methods, customer-and-design-centered methods, such as Visualization-Driven Rapid Prototyping developed by Brian Willison, work to engage customers and end users to facilitate agile software development.
Agile software development In 2008 the Software Engineering Institute (SEI) published the technical report "CMMI or Agile: Why Not Embrace Both" to make clear that the Capability Maturity Model Integration and agile methods can co-exist. Modern CMMI-compatible development processes are also iterative. The CMMI Version 1.3 includes tips for implementing CMMI and agile process improvement together.
Agile modeling Agile modeling is a supplement to other agile development methodologies such as Scrum, extreme programming (XP), and Rational Unified Process (RUP). It is explicitly included as part of the disciplined agile delivery (DAD) framework. As per 2011 stats, agile modeling accounted for 1% of all agile software development.
Agile software development Agile development paradigms can be used in other areas of life such as raising children. Its success in child development might be founded on some basic management principles; communication, adaptation and awareness. Bruce Feiler has claimed that the basic agile development paradigms can be applied to household management and raising children. In his TED Talk "Agile programming – for your family", these paradigms brought significant changes to his household environment, such as the kids doing dishes, taking out the trash, and decreasing his children's emotional outbreaks, which inadvertently increased their emotional stability.
Agile software development Incremental software development methods can be traced back to 1957. Evolutionary project management and adaptive software development emerged in the early 1970s. During the 1990s, a number of "lightweight" software development methods evolved in reaction to the prevailing "heavyweight" methods that critics described as heavily regulated, regimented, and micro-managed. These included: from 1991, rapid application development; from 1994, unified process and dynamic systems development method (DSDM); from 1995, Scrum; from 1996, Crystal Clear and extreme programming (XP); and from 1997, feature-driven development. Although these originated before the publication of the Agile Manifesto in 2001, they are now collectively referred to as agile methods.