Managing an Agile Team

Start Date: 07/05/2020

Course Type: Common Course

Course Link:

About Course

While agile has become the de facto standard for managing digital innovation teams, many wonder if they’re doing it ‘right’. Twitter is full of jokes about how teams say they do agile but don’t ‘really’ do it. The reality is that getting the most out of agile is less about observing specific procedures and more about how a team focuses and measures their progress. Rather than just boring you with an accounting of agile methodologies, this course focuses on helping you better charter your team’s focus, definition of success, and practice of agile. While learning about agile mainstays like Scrum, XP, and kanban, you’ll also learn to help your team ask the right questions about how they’re working and facilitate good answers on how agile can help. As a Project Management Institute (PMI®) Registered Education Provider, the University of Virginia Darden School of Business has been approved by PMI to issue 20 professional development units (PDUs) for this course, which focuses on core competencies recognized by PMI. (Provider #2122) This course is supported by the Batten Institute at UVA’s Darden School of Business. The Batten Institute’s mission is to improve the world through entrepreneurship and innovation:

Course Syllabus

This week we’ll introduce the four major jobs of software development and help you think through where to focus on each of them for successful outcomes. Then we’ll step through the leading agile methodologies--Scrum, XP, and kanban. You’ll finish the week with a deeper understanding of how to pair your project’s most important facets with the best of what agile has to offer.

Coursera Plus banner featuring three learners and university partner logos

Course Introduction

Managing an Agile Team This course will help you build effective teams by understanding the key roles and responsibilities of senior management, the role of the customer, the role of the architect, the role of the product management, and the role of the design team. You’ll also understand the adoption strategies and techniques used to manage teams in agile process development. This course is part of the iMBA offered by the University of Illinois, a flexible, fully-accredited online MBA at an incredibly competitive price. For more information, please see the Resource page in this course and 1: Introduction to Agile Module 2: Customer Value Module 3: Architecting a Team Module 4: Managing the Product Mastering US Business Writing This course will help you master the craft of writing in the United States. You will learn why professional writers must be active, and what influences can be a hindrance. You will be able to develop a skill at identifying and concealing the essential elements of writing, as well as craft effective language to convey ideas. You will also learn how to write well-developed business documents. This course is part of the iMBA offered by the University of Illinois, a flexible, fully-accredited online MBA at an incredibly competitive price. For more information, please see the Resource page in this course and onlinemba.ill

Course Tag

agile product management Agile Software Development backlog management Kanban XP

Related Wiki Topic

Article Example
Agile leadership Within Agile Business Management, the primary job of an Agile Leader is to encourage and empower cross-functional teams. This demands that team members are granted sufficient personal responsibility, accountability and authority to deliver the customers’ requirements. An Agile Leader can support this in three ways:
Agile testing Agile development recognizes that testing is not a separate phase, but an integral part of software development, along with coding. Agile teams use a "whole-team" approach to "baking quality in" to the software product. Testers on agile teams lend their expertise in eliciting examples of desired behavior from customers, collaborating with the development team to turn those into executable specifications that guide coding. Testing and coding are done incrementally and interactively, building up each feature until it provides enough value to release to production. Agile testing covers all types of testing. The Agile Testing Quadrants provide a helpful taxonomy to help teams identify and plan the testing needed.
Managing editor A managing editor is a senior member of a publication's management team. Typically, the managing editor (ME) reports directly to the Editor in Chief and oversees all aspects of the publication.
Agile software development There are also agile self-assessments to determine whether a team is using agile practices (Nokia test, Karlskrona test, 42 points test).
Agile Architecture Several attempts have been made to specify what makes up an agile approach to architecture. According to the SAFe framework, the principles of agile architecture are:
Agile testing Agile testing is a software testing practice that follows the principles of agile software development. Agile testing involves all members of a cross-functional agile team, with special expertise contributed by testers, to ensure delivering the business value desired by the customer at frequent intervals, working at a sustainable pace. Specification by example is used to capture examples of desired and undesired behavior and guide coding.
Agile management Agile management, or agile process management, or simply agile refers to an iterative, incremental method of managing the design and build activities of engineering, information technology and other business areas that aim to provide new product or service development in a highly flexible and interactive manner; an example is its application in Scrum, an original form of agile software development. It requires capable individuals from the relevant business, openness to consistent customer input, and management openness to non-hierarchical forms of leadership. Agile can in fact be viewed as a broadening and generalization of the principles of the earlier successful array of Scrum concepts and techniques to more diverse business activities. Agile also traces its evolution to a "consensus event", the publication of the "Agile manifesto" in 2001, and it has conceptual links to lean techniques, kaizen, and the Six Sigma area of business ideas. The Agile Manifesto, is centered on four values: communication with parties is more important than standard procedures and tools, focus on delivering a working application and less focus on providing thorough documentation, collaborate more with clients, and last be open to changes instead of freezing the scope of the work.
Scaled Agile Framework All SAFe teams are agile teams. There is more than one type of team for example there may be a Systems Team and architectural teams, and the more common Agile development teams which are called "Agile Teams" in the SAFe methodology.
Agile application An Agile Application is the result of Service Oriented Architecture and Agile Development paradigms. An Agile Application is distinguished from average applications in that it is a loosely coupled set of services with a decoupled orchestration layer and it is easily modified to address changing business needs and it is scalable by design.
Agile software development In 2011 the original Agile Alliance created the Guide to Agile Practices, an evolving open-source compendium of the working definitions of agile practices, terms, and elements, along with interpretations and experience guidelines from the worldwide community of agile practitioners.
Agile software development Teams and organizations choosing to adopt more agile ways of working typically undertake an "agile transformation" with the support of one or more agile coaches. The agile coach guides teams through the transformation. There are typically two styles of agile coaching: push based and pull-based agile coaching.
Agile Business Intelligence Bruni in her article 5 Steps To Agile BI outlines the five elements that promote an Agile BI enterprise environment.
Agile software development Under an agile business management model, agile techniques, practices, principles and values are expressed across five domains.
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 Marketing Agile Marketing is an organizational effectiveness strategy that drives growth through focusing team efforts on those that deliver value to the end-customer. This emerging practice in marketing applies key principles of agile software development to increase speed, quality, flexibility, and effectiveness of a marketing department. Ownership and execution of work is managed by self-organizing, highly iterative, cross-functional, and flexible teams empowered to identify and deliver customer value.
Scaled Agile Framework A Systems Team is a specialised team which is responsible for maintaining the development environment used by the Agile Teams and for testing solutions end-to-end.
Scaled Agile Framework Scaled Agile Framework (or SAFe) is an Agile software development framework designed by Scaled Agile, Inc. It consists of a knowledge base of integrated patterns intended for enterprise-scale Lean-Agile development. Its proponents consider SAFe to be scalable and modular, allowing an organization to apply it in a way that suits its need.
Agile (horse) Agile (1902–after 1912) was an American Thoroughbred racehorse that was the winner of the 1905 Kentucky Derby. Agile won the Sapphire Stakes as a two-year-old and the Phoenix Stakes as a three-year-old.
Agile Communications In late 2003, Agile began a rollout of a national network, an Optic Fibre based IP network running on STM-1 Packet over Sonet (POS) links to connect all Agile POPs across Australia.
Agile Marketing Agile methods and tools developed for product-focused Agile are relevant to Agile Marketing, but important distinctions exist. Agile Marketing's complexity reflects the complexity of supporting marketing's deliverables, which: