Agile 2.0 Review / Identification of customized Agile processes
Import
·
Feb 12, 2018
·
article
I have done some research on Agile 1.0/2.0 and found out that after upgrading to Agile 2.0 in DEV, some of modules from previous version (Agile 1.0):-
- Have been de-activated
- Have been removed.
- Some new modules have been introduced.
So for the things which have been de-activated, we can activate those as they are already there and for the things which have been removed, we can capture those from other instances as we still have Agile 1.0 in other instances. I have documented the things which have been de-activated or removed.
List of Agile Modules in Agile 1.0 & Agile 2.0
| Module Name | Agile 1.0 | Agile 2.0 |
|---|---|---|
| Administration | Available | Available |
| All RIDAC | Available | Available |
| All Stories | N/A (Introduced in Agile 2.0) | Available |
| Assigned to me (table = Story [rm_story]) | Available | De-Activated in Agile 2.0 |
| Assigned to me (table = Scrum task [rm_scrum_task]) | Available | De-Activated in Agile 2.0 |
| Assigned to me Defect [rm_defect] | Available | De-Activated in Agile 2.0 |
| Assigned to me Enhancement [rm_enhancement] | Available | De-Activated in Agile 2.0 |
| Backlog | N/A (Introduced in Agile 2.0) | Available |
| Create Agile Group | N/A (Introduced in Agile 2.0) | Available |
| Create New Story [rm_story] | Available | De-Activated in Agile 2.0 |
| Create New Defect [rm_defect] | Available | Available |
| Create New Defect [rm_defect] | Available | De-Activated in Agile 2.0 |
| Create New Enhancement [rm_enhancement] | Available | De-Activated in Agile 2.0 |
| Daily Stand Up Boards | N/A (Introduced in Agile 2.0) | Available |
| Defects Defect [rm_defect] | N/A (Introduced in Agile 2.0) | Available |
| Defects | Available | Available |
| Enhancements Enhancement [rm_enhancement] | N/A (Introduced in Agile 2.0) | Available |
| Enhancements | Available | Available |
| Epics Epic [rm_epic] | N/A (Introduced in Agile 2.0) | Available |
| Getting Started | Available | Available |
| Group Backlog Story [rm_story] | N/A (Introduced in Agile 2.0) | Available |
| Groups Group [sys_user_group] | N/A (Introduced in Agile 2.0) | Available |
| My Products | Available | De-Activated in Agile 2.0 |
| Open Defects | Available | Removed in Agile 2.0 |
| Open Enhancements | Available | Removed in Agile 2.0 |
| Open Epics | Available | Removed in Agile 2.0 |
| Open Releases | Available | Removed in Agile 2.0 |
| Open Sprints | Available | De-Activated in Agile 2.0 |
| Open Stories | Available | Removed in Agile 2.0 |
| Open Tasks | Available | De-Activated in Agile 2.0 |
| Planning | Available | Available |
| Planning Board | Available | De-Activated in Agile 2.0 |
| Products | Available | Available |
| Properties | Available | Available |
| Release Backlog | N/A (Introduced in Agile 2.0) | Available |
| Release Planning | N/A (Introduced in Agile 2.0) | Available |
| Releases | N/A (Introduced in Agile 2.0) | Available |
| Sprint Planning | N/A (Introduced in Agile 2.0) | Available |
| Stories | Available | Removed in Agile 2.0 |
| Story Progress Board | N/A (Introduced in Agile 2.0) | Available |
| Tasks | Available | De-Activated in Agile 2.0 |
| Task Progress Board | N/A (Introduced in Agile 2.0) | Available |
| Themes | Available | Available |
Some Additional Changes in Agile 2.0:-
- In Agile 2.0 'Product' field on story form is not mandatory while it is mandatory in Agile 1.0.
- Type of 'Acceptance Criteria' field on Story form in Agile 2.0 is HTML while in Agile 1.0 it is of String type.
View original source
https://www.servicenow.com/community/developer-articles/agile-2-0-review-identification-of-customized-agile-processes/ta-p/2329804