You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/devops-practices/continuous-planning/agile-development/Delivery-Plan.md
+7-9Lines changed: 7 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,8 @@
1
1
# Delivery Plan
2
2
3
-
## Goals
3
+
## Overview
4
4
5
-
While Scrum does not require and discourages planning more than one sprint at a time. Most of us work in enterprises where we are dependent outside teams (for example: marketing, sales, support).
5
+
While Scrum does not require and discourages planning more than one sprint at a time. Most of us work in enterprises where we are dependent outside teams (for example: marketing, sales, support or other development teams).
6
6
7
7
A rough assessment of the planned project scope is achievable within a reasonable time frame and resources. The goal is to have a rough plan and estimate as a starting point, not to implement "Agile-fall or Wagile."
8
8
@@ -22,7 +22,7 @@ One approach you can take to accomplish is with stickies and a spreadsheet.
22
22
Step 1: Stack rank the features for everything in your backlog
@@ -32,16 +32,14 @@ Step 2: T-Shirt Features in terms of working weeks per person. In some scenarios
32
32
33
33
Step 3: Calculate the capacity for the team based on the number of weeks person with his/her start and end date and minus holidays, vacation, conferences, training, and onboarding days. Also, minus time if the person is also working on defects and support.
34
34
35
-
Step 4: Based on your capacity, you know have the options
35
+
Step 4: Based on your capacity, you now have the options
36
36
37
37
- Ask for more resources. Caution: onboarding new resources take time.
38
38
- Reduce the scope to the most MVP. Caution: as you trim more of the scope, it might be valuable anymore to the customer. Consider a cupcake which is everything you need. You don't want to skim on the frosting.
39
39
- Ask for more time. Usually, this is the most flexible, but if there is a marketing date that you need to hit, this might be as flexible.
40
40
41
-
## Tools
42
-
43
-
You can also leverage one of these tools by creating your epics and features and add the weeks estimates.
41
+
Delivery Plans provide a schedule of stories or features your team plan to deliver. Delivery Plans show the scheduled work items by a sprint (iteration path) of selected teams against a calendar view.
44
42
45
-
The [Plans (Preview) feature on Azure DevOps](https://docs.microsoft.com/en-us/azure/devops/project/navigation/preview-features?view=azure-devops) will help you make a plan. Delivery Plans provide a schedule of stories or features your team plan to deliver. Delivery Plans show the scheduled work items by a sprint (iteration path) of selected teams against a calendar view.
43
+
## Tools
46
44
47
-
Confluence JIRA, Trello, Rally, Asana, Basecamp, and Github Issues are other similar tools in the market (some are free, others you pay a monthly fee, or you can install on-prem) that you can leverage.
45
+
Delivery Plans (part of Azure DevOps), Confluence & JIRA, Trello, Rally, Asana, Basecamp, and Github Issues are just some of the best Agile planning tools in the market (some are free, others you pay a monthly fee, or you can install on-prem) that you can leverage.
Copy file name to clipboardExpand all lines: docs/devops-practices/continuous-planning/agile-development/Team-Agreements/team-engagements.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,4 @@
1
-
# Engagement Team Development
1
+
# Team Engagements
2
2
3
3
In every engagement or project, dynamics are different & so are the team requirements. Based on transfer learning among teams, we aim to build right "code-with" environments in every team.
4
4
@@ -11,7 +11,7 @@ However those phases can be extremely fast or sometimes mismatched in teams due
11
11
12
12
In order to minimize the risk and set the expectations on the right way for all parties, an identification phase is important to understand each other. Some potential steps in this phase may be as following (not limited):
0 commit comments