Agile Courses Online

About

Agile software development is a group of software development methodologies based on iterative and incremental development, where requirements and solutions evolve through collaboration between self-organizing, cross-functional teams. There are many specific agile development methods. Most promote development, teamwork, collaboration, and process adaptability throughout the life-cycle of the project.

Agile methods break tasks into small increments with minimal planning, and do not directly involve long-term planning. Iterations are short time frames (timeboxes) that typically last from one to four weeks. Each iteration involves a team working through a full software development cycle including planning, requirements analysis, design, coding, unit testing, and acceptance testing when a working product is demonstrated to stakeholders. This minimizes overall risk and allows the project to adapt to changes quickly. 

Content

• History
  • Predecessors
  • Agile Manifesto
• Characteristics
• Comparison with other methods
• Agile methods
  • Method tailoring
• Measuring agility
• Experience and reception
  • Suitability
  • Experience reports

About

Agile software development is a group of software development methodologies based on iterative and incremental development, where requirements and solutions evolve through collaboration between self-organizing, cross-functional teams. There are many specific agile development methods. Most promote development, teamwork, collaboration, and process adaptability throughout the life-cycle of the project. Agile methods break tasks into small increments with minimal planning, and do not directly involve long-term planning. Iterations are short time frames (timeboxes) that typically last from one to four weeks. Each iteration involves a team working through a full software development cycle including planning, requirements analysis, design, coding, unit testing, and acceptance testing when a working product is demonstrated to stakeholders. This minimizes overall risk and allows the project to adapt to changes quickly. 

Content

• Introduction
  • Introduction to Approach
  • Iteration 1: Understanding
  • Iteration Two: Functional Delivery
  • Iteration Three: Robust Delivery
• Whole process
• Iteration One
• Iteration One/System metaphor
• Iteration One/Planning game
  • Requirements and the Planning Game
  • What is a requirement?
  • Language
  • The Agile Approach
  • What is a user story?
• Iteration Two
  • Overview Iteration Two
  • Functional Requirements
  • Interaction Design
  • Design Specifications
  • Implementation
  • Evaluation
• Iteration Two/Good requirements
• Requirements Specification
  • Functional Requirements
  • Non-Functional Requirements
• Iteration Two/Fishing
• Iteration Two/Data modelling
• Iteration Two/Process modelling
• Iteration Two/Context
• Iteration Two/Tasks
• Iteration Two/Interaction design/Data model
• Iteration Two/Interaction design/Interactivity
• Iteration Two/Test based development
• Iteration Three/Style guide

About

In software development, agile (sometimes written Agile) practices involve discovering requirements and developing solutions through the collaborative effort of self-organizing and cross-functional teams and their customer(s)/end user(s). It advocates adaptive planning, evolutionary development, early delivery, and continual improvement, and it encourages flexible responses to change.

Most agile development methods break product development work into small increments that minimize the amount of up-front planning and design. Iterations, or sprints, are short time frames (timeboxes) that typically last from one to four weeks. Each iteration involves a cross-functional team working in all functions: planning, analysis, design, coding, unit testing, and acceptance testing. At the end of the iteration, a working product is demonstrated to stakeholders. This minimizes overall risk and allows the product to adapt to changes quickly. An iteration might not add enough functionality to warrant a market release, but the goal is to have an available release (with minimal bugs) at the end of each iteration. Through incremental development products have room to "fail often and early" throughout each iterative phase instead of drastically on a final release date. Multiple iterations might be required to release a product or new features. Working software is the primary measure of progress.

Content

• History

• The Manifesto for Agile Software Development

  • Agile software development values

  • Agile software development principles

• Overview

  • Iterative, incremental, and evolutionary

  • Efficient and face-to-face communication

  • Very short feedback loop and adaptation cycle

  • Quality focus

• Philosophy

  • Adaptive vs. predictive

  • Agile vs. waterfall

  • Code vs. documentation

• Agile software development methods

  • Agile software development practices

  • Method tailoring

  • Large-scale, offshore and distributed

  • Regulated domains

• Experience and adoption

  • Measuring agility

    • Internal assessments

    • Public surveys

  • Common agile software development pitfalls

    • Lack of overall product design

    • Adding stories to an iteration in progress

    • Lack of sponsor support

    • Insufficient training

    • Product owner role is not properly filled

    • Teams are not focused

    • Excessive preparation/planning

    • Problem-solving in the daily standup

    • Assigning tasks

    • Scrum master as a contributor

    • Lack of test automation

    • Allowing technical debt to build up

    • Attempting to take on too much in an iteration

    • Fixed time, resources, scope, and quality

    • Developer burnout

• Agile management

  • Applications outside software development

About

Lean software development is a translation of lean manufacturing principles and practices to the software development domain. Adapted from the Toyota Production System, it is emerging with the support of a pro-lean subculture within the Agile community. Lean offers a solid conceptual framework, values and principles, as well as good practices, derived from experience, that support agile organizations.

In this course, we will investigate lean ideas and cover a portion of the normal Lean strategies and procedures like Kanban, Value Stream Mapping, and so on 

In this course, we will likewise learn strategies like Lean Startup and Design Thinking that can assist groups with learning client and market needs a lot quicker and less expensive. 

As a feature of this course, you will likewise apply the information acquired in this course to anecdotal contextual investigations. These tasks will help you acquire an insight to unquestionably apply these methods in the genuine world. 

Toward the finish of the course, you will have the option to apply lean procedures/techniques to programming advancement. You will likewise have the option to apply strategies to find out about your clients and market needs a lot quicker and less expensive.

Content

• Origin

• Lean principles

  • Eliminate waste

  • Amplify learning

  • Decide as late as possible

  • Deliver as fast as possible

  • Empower the team

  • Build integrity in

  • Optimize the Whole

• Lean software practices

About

Taiga is a project management application that can handle both simple and complex projects for startups, software developers, and other target teams. It tracks the progress of a project. With Taiga, you can use either Kanban or Scrum template, or both. Backlogs are shown as a running list of all features and User Stories added to the project.

Taiga integrates video conferencing functions with the use of third party services like Talky.io and Appear.in. Group and private chat is done via HipChat.

This project management system can interface with web-based version control repositories like GitHub and Bitbucket. Taiga also provides several importers to facilitate migration from other proprietary software platforms.

Content

• Overview
• How it works
• Requirements
• Installation
• API
• Webhooks
• Themes