Professional Documents
Culture Documents
What is Agile?
Agile is a collection of principles used in software development and project management. Agile
focuses on enabling teams to deliver work in small, workable increments, thus delivering value to
their customers with ease. Evaluation of the requirements, plans, and results take place
continuously. This helps the team in responding to changes in a quick manner.
Agile Principles
To make a process Agile, the following principles need to be satisfied.
1. Customer Satisfaction
The customer needs to be satisfied with the quick delivery of the product.
2. Welcome Change
3. Deliver Frequently
Page 1 of 14
4. Work Together
The business and development team need to work together through the course
of the project.
5. Motivated Team
6. Face-
to-face
7. Working Software
Having working output is an indication of the progress made towards the final
product.
8. Constant Pace
9. Good Design
Page 2 of 14
10. Simplicity
The amount of time where work isn’t being done needs to be reduced.
11. Self-Organization
These types of teams provide the best designs, requirements, and architectures.
Advantages of Agile
Agile enables a large amount of collaboration and interaction between the client and the
project team.
Thanks to this, clients have improved transparency, and therefore a clearer understanding of
the phases of the project is present.
The product is delivered predictably, or sometimes earlier than expected.
The cost of the project is predictable and follows a rigid schedule.
Changes can refine and re-prioritize the product backlog.
Enables the client to prioritize different features, allowing the team to ensure maximum
project value.
The project is broken down into smaller units, providing high-quality development, testing,
and collaboration.
When implementing a workflow for the team, always start simple. Fight the
temptation to spend weeks (over-)engineering it. Overly complex workflows
Page 3 of 14
are hard to understand and adopt–not to mention adapt. For software teams,
we recommend these basic workflow states:
In an issue tracker, these statuses flow from one to the next using transitions that
structure the workflow.
Page 4 of 14
Agile Workflow Using Azure DevOps
Azure Boards: agile planning, work item tracking, visualisation and reporting tool.
Azure Pipelines: a language, platform and cloud agnostic CI/CD platform with
support for containers or Kubernetes.
Azure Repos: provides cloud-hosted private git repos.
Azure Artifacts: provides integrated package management with support for Maven,
npm, Python and NuGet package feeds from public or private sources.
Azure Test Plans: provides an integrated planned and exploratory testing solution.
Page 5 of 14
You access Azure DevOps services through the left pane, as shown in the following
image. To jump to information for each major service, see the associated articles.
Dashboards
Wiki
Boards
Repos
Pipelines
Test Plans
Artifacts
Dashboards
From Dashboards, you gain access to user-configurable dashboards.
Page 6 of 14
You can do the following tasks in Dashboards:
So here we follow Agile Process to track our Epics ,User stories, Task and Test plan
and Test case
Page 7 of 14
DevOps Board:
After Login you will see following window , Click on Board > Board Option
Board display the different columns which having different User stories
Page 8 of 14
When you add a user story, bug, task, or feature,
you create a work item. Add epics to track
significant business initiatives. Add features to
track specific applications or set of work. Define
user stories to track work that you'll assign to
specific team members, and bugs to track code
defects. Lastly, use tasks to track even smaller
amounts of work for which you want to track time
either in hours or days.
The Agile process provides several work item types—for example, user stories, tasks, bugs,
features, and epics among others—to plan and track work. We recommend you start by
adding user stories. If you need to group them into a hierarchy, you can define features. If
you want to track additional details of work, you can add tasks to a user story.
The User Stories Kanban board is the best tool for quickly adding user stories and child tasks.
To open, choose Boards>Boards.
Page 9 of 14
The Features Kanban board is the best tool for quickly adding features and user stories that
are children of those features. To open the Features board from the Stories board,
choose Features from the board selector.
Page 10 of 14
2. Enter return and the system assigns a work item ID to the user story.
3. To track the work you want to manage, add as many user stories that you need.
For example, here we assign the story to Raisa Pokrovskaya and we add a discussion note,
at-mentioning Raisa. Choose Save & Close when done.
Page 11 of 14
Update status
The State field tracks the status of a work item. With the board, you can quickly update the
status of backlog items by dragging and dropping them to a different column. This feature
requires that you have Basic access or higher.
As work starts, drag the user story card from the Backlog column to the Active column.
Once work is ready for review, move to the Resolved column. After it is reviewed and
accepted, move to the Closed column. You can add or rename columns as needed,
see Customize your board.
Add tasks
1. To start adding tasks, choose the actions icon for the story and select the Add
Task option.
2. Enter a title for the task and type Enter when done.
Page 12 of 14
3. If you have a number of tasks to add, simply keep typing your task titles and type
Enter.
4. You can mark a task as done, expand or collapse the task checklist, or reorder and
reparent tasks.
Mark a task as done Reorder and reparent tasks Expand or collapse the
checklist
Page 13 of 14
Add details to a task
If you have details you want to add about a task, choose the title, to open it. Change
one or more field values, add a description, or make a note in the Discussion section.
Choose Save & Close when done.
Page 14 of 14