Agile Development Guidelines

Agile Manifesto, Principles and the SDLC

Subway Map to Agile Practices

Agile Project Management Tools

Epics, Features, User Stories and Tasks

Versions, Milestones and Bugs

Sprint Iterations and Gantt Charts

Git Best Practices & Workflows

References

The Agile Manifesto and SDLC

Individuals and interactions over processes and tools

Working software over comprehensive documentation

Customer collaboration over contract negotiation

Responding to change over following a plan

SDLC

We are uncovering better ways of developing software by doing it

and helping others do it. Through this work we have come to value:

That is, while there is value in the items on the right,

we value the items on the left more.

Software

Development

Life

Cycle

1. Planning

2. Analysis

3. Design

4. Implementation

5. Testing and Integration

6. Maintenance

12 Principles Behind Agile Manifesto

Subway Map to Agile Practices

Agile Project Management Tools

Open Project

Project planning and scheduling

Task management tools

Product roadmap and versioning

Timeline and Gantt Chart tools

Agile work package item types

Forums and Wiki per project

Bug and Milestone tracking

Git repository integration

Dynamic project scheduling

https://openproject.com/

Agile Scrum Project Tools

Open Project

Clone Git repository on server

Install Bash script for Slack

Plan Sprints with work package items

GitHub

Create GitHub Issues referencing OpenProject or Asana ticket URL(s)

Create Feature Branches referencing GitHub Issue number for automation

Use GitHub Project Boards for Scrum/Kanban management of issues

Follow peer review team model using Pull Requests and Reviewers

Use GitHub Guides and Agile Alliance best practices and terminology

Commit code and schema changes incrementally to show change history

Use Labels, Tags and Semantic versioning to manage development

https://www.openproject.org/plugins/

https://github.com/marketplace/

Agile Glossary for Scrum/Kanban

Epic –A very global and not very well defined aspect of the application

Feature –A definition of a capability for the application

User Story –A specific use case scenario from the user’s perspective

Task –A required item to be done usually as a prerequisite

Version –A collection of work items for Sprint iteration cycles

Milestone –A predetermined date and collection of versions

Bug –An issue with the application or project that needs resolution

Agile Features

Feature

Defines and describes a capability or function of the application

Typically a feature is a broad application or technical requirement

Features tend to have User Stories as children to describe different use

case scenarios where the Feature varies based on the user’s role.

Should not have any parent or children Features associated.

Usually a child of an Epic however may be used anywhere appropriate.

Written from a technical perspective in respect to the application.

Editing the customer information via the web portal

Agile Epics

Epic

Comprise a very global and not very well defined aspect of the

application and are very broad in nature and scope.

Epics are broken down into smaller User Stories and Features in order to

make sense and fit into Agile iterations like Versions and Milestones.

User Stories and Features are more specific in functionality, that can be

easily tested with acceptance and unit tests during Sprint iterations.

Themes are another way to describe Epics as they include many

collections of User Stories and Features to deliver the user experience.

Epics are always a top level parent in the project tree hierarchy

Allow the customer to manage their own account via the web

Agile User Stories

User Story

Always written from the perspective of the user interacting with the

application either for achieving a specific result or describing an ability.

Stories should be specific to the role or access privileges of the user.

User stories can have Features and Tasks nested as children to expand

the details needed to describe the story and experience.

Should not have any User Stories as children or parents.

Belong to a Feature or an Epic, but can also be a top level parent.

As a bank clerk,

I want to be able to modify the customer information

so that I can keep it up to date.

Agile Tasks

Task

A required action item or requisite to as part of the work packages at any

level in the project tree hierarchy.

May be part of any Epic, User Story or Feature and even top level.

Tasks can be nested having sub-tasks as children like any to-do list.

Good practice is to associate the task with the required work item.

Tasks differ from other work types as they are needed steps for the

project and not any part of the user’s experience or feature request.

Configure and deploy a staging server for testing

- Connect AWS S3 file storage buckets

- Configure LAMP stack and SSL certificates

Versions, Milestones and Bugs

Version

A collection of work items to be completed using Sprint iteration cycles

and accepted as a done set of features and user stories.

Work package items can be assigned and re-assigned to different

versions to accommodate the story points and work efforts required.

Project Scope, Skeleton or Alpha, Beta, Release Candidate, Tagged

Milestone

A preset date and collection of work items and versions to be done.

UAT –User Acceptance Testing 10/01/2020

Bug

A repeatable defect issue with the application or project design.

Cannot upload a document when auto detect is selected

Sprint Iterations and Gantt Charts

Sprint Iteration

Collection of work items from a Version to be completed typically in a

short amount of time during the development phases usually.

Based upon the related work items and total story points allotted to the

tasks at the time of the Sprint Planning Meeting.

Reviewed during the Sprint Review Meeting and marked as done if

completely tested and carried over to next sprint if incomplete.

Complete Skeleton version work items in two Sprint cycles

Gantt & Timeline Charts

Used to estimate the work items to be completed both during the total

project scope as well as individual versions and milestones.

Adjust work items to fit version or milestone using drag & drop

Git Best Practices

Use Issue Templates

Create an issue using template and then replace the default placeholder

text with actual OpenProject or GitHub task item URL(s).

Maintain consistency with GitHub Flavored Markdown (gfm) by creating

To-Do items unchecked when opening issue to indicate work being done

on the feature branch or sprint assigned from OpenProject or Asana.

Use Feature Branches and Pull Requests

Never commit or work directly upon the master trunk.

Always keep code commits and schema changes within an issue ticket

Submit a Pull Request when branch has been tested ready for review

Do NOT merge your own Pull Requests unless otherwise instructed

Resolve any open comments or code discussions before merging

Commit code and schema changes incrementally and push frequently

References

Agile Essentials

Agile Glossary

GitHub Best Practices

GitHub Hello World

YouTube –GitHub Pull Requests, Branches & Merging

Download Agile Development Guidelines PowerPoint Presentation

© 2022 Directional Consulting