Agile Planning for Software Products

Start Date: 04/11/2021

Course Type: Common Course

Course Link: https://www.coursera.org/learn/agile-planning-for-software-products

About Course

This course covers the techniques required to break down and map requirements into plans that will ultimately drive software production. Upon successful completion of this course, you will be able to: - Create effective plans for software development - Map user requirements to developer tasks - Assess and plan for project risks - Apply velocity-driven planning techniques - Generate work estimates for software products

Course Syllabus

Welcome to the first module! In this module, you will be learning some basic principles that you will need for effective planning. You will start this module off with an introduction to planning. You will then learn about how planning, and the approach you take to planning, can reduce uncertainty in your project. We will then move onto learning how to breakdown a project into small, manageable pieces, and how to organize those pieces. Finally, we will go over the differences between estimates, targets, and commitments. Together, these lessons will build a good base for learning planning techniques at both the release and iteration level.

Coursera Plus banner featuring three learners and university partner logos

Course Introduction

Agile Planning for Software Products In this course we will provide an introduction to the concepts of the agile process, including an overview of the agile methodologies and processes. We will cover topics such as process management, project initiation, project scheduling, project delivery, and deliverables and delivery networks. We will also cover topics such as user stories, team development, and product management. We will also cover topics such as product lifecycles, and how these topics apply to software products. Learning Objectives This course teaches you agile concepts, tools, and processes 1. Describe processes associated with agile methods 2. Assess the similarities and differences of agile methods 3. Use agile methodologies for project planning 4. Set up a delivery schedule for your software products 5. Conduct project scheduling in a continuous flow method 6. Deliverables in an agile manner 7. Explain concepts and help you understand processes By the end of this course you should be able to: - Plan and set up an agile project plan - Coordinate your teams - Manage your projects and projects networks - Coordinate your projects and projects networks with other GCP - Explain the differences between agile and waterfall methods - Outline your project management plan - Coordinate your projects and projects schedules with other GCP - Explain the process of implementing agile projects - Outline your project scheduling plan - Coordinate your projects and projects schedules with other GCP

Course Tag

Software Development Agile Management Program Evaluation And Review Technique (PERT) Agile Software Development

Related Wiki Topic

Article Example
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 Frameworks Agile Frameworks provides software products and consulting services for civil engineering, engineering testing, construction services, and environmental testing firms.
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 Corporation In February, 2005, Agile Software Corporation acquired Cimmetry Systems Corporation, a privately owned software developer specializing in enterprise visualization, for approximately US$41.5 million in cash. Cimmetry Systems Corporation became a wholly owned subsidiary of Agile Software Corporation.
Agile software development Agile software development describes a set of principles for software development under which requirements and solutions evolve through the collaborative effort of self-organizing cross-functional teams. It advocates adaptive planning, evolutionary development, early delivery, and continuous improvement, and it encourages rapid and flexible response to change. These principles support the definition and continuing evolution of many software development methods.
Agile Architecture Agile architecture means how enterprise / system / software architects apply architectural practice in agile software development. A number of commentators have identified a tension between traditional software architecture and agile methods along the axis of adaptation (leaving architectural decisions until the last possible moment) versus anticipation (planning in advance). (Kruchten, 2010 )
Agile software development Potentially, almost all agile methods are suitable for method tailoring. Even the DSDM method is being used for this purpose and has been successfully tailored in a CMM context. Situation-appropriateness can be considered as a distinguishing characteristic between agile methods and traditional software development methods, with the latter being relatively much more rigid and prescriptive. The practical implication is that agile methods allow product development teams to adapt working practices according to the needs of individual products. Practices are concrete activities and products that are part of a method framework. At a more extreme level, the philosophy behind the method, consisting of a number of principles, could be adapted (Aydin, 2004).
Agile Software Corporation Agile Software Corporation operated as a public company, with shares trading on NASDAQ. On 15 May 2007, Oracle Corporation announced that it would acquire Agile Software Corporation through a cash merger for US$8.10 per share, or approximately US$495 million. On July 16, 2007, Oracle Corporation completed the acquisition of Agile, which became a wholly owned subsidiary.
Agile Project Management (book) Agile Project Management: Creating Innovative Products by Jim Highsmith discusses the management of projects using the agile software development methodology. The book has been recommended by different reviewers.
Agile Frameworks Agile Frameworks, LLC is an independent software vendor (ISV) that provides mobile and desktop-based applications and consulting services for construction services and engineering testing firms. Its products are used for field materials sampling, testing and reporting for construction sites.
Portable Flight Planning Software The Portable Flight Planning Software, or PFPS is a suite of software for planning air missions. The suite includes the FalconView mapping system, Combat Flight Planning Software (CFPS), Combat Weapon Delivery Software (CWDS), Combat Air Drop Planning Software (CAPS) and several other software packages built by various software contractors.
Agile Software Corporation Agile Software Corporation, was a San Jose, California based company that provided product lifecycle management (PLM) software.
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 software development Popular agile software development frameworks include (but are not limited to):
Consumer surplus for software products Consumer surplus for software products can be calculated differently from other products. Customers tend to buy products with greater consumer surplus. Software companies should know what measure in their market analysis to determine their consumer surplus so that create products that are better at fulfilling their customers. Messerschmitt and Szyperski have studied what factors affect the perceived consumer surplus in the software product market. The value a customer places on software is affected by things such as compatibility with complementary products, degree of adoption in the market, usability, increases in productivity, differentiation from competitors, and innovativeness. These can be customer satisfaction dimensions.
Planning poker Planning poker is a variation of the Wideband Delphi method. It is most commonly used in agile software development, in particular in Scrum and Extreme Programming.
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 modeling Agile modeling (AM) is a methodology for modeling and documenting software systems based on best practices. It is a collection of values and principles, that can be applied on an (agile) software development project. This methodology is more flexible than traditional modeling methods, making it a better fit in a fast changing environment. It is part of the agile software development tool kit.
Agile Automation Agile Automation software development has the potential to reduce the development lifecycle and at the same time, encompass automated unit testing. Something that the industry is calling for. In addition, the "don't repeat yourself" aspects of Agile object oriented software development encompassing extension of software classes through interfaces (Software class is open for extension but closed for modification) are very attractive in a regulated industry where software change validation is particularly expensive. Agile software development promotes true object oriented software programming which in turn results in software that is more amenable to change and less likely to break.
Agile software development Because of the short iteration style of agile software development, it also has strong connections with the lean startup concept.