Makino- Requirement Analysis and Estimation
- Ariya Krishnan
- Sharmendra Vishwakarma
- YUVARAJ KUNDASI (Unlicensed)
Story points estimation ref :
Makino Development plan
Start Date: 11-March-2022
On Hold date: 15-March-2022
Major requirements: @Sharmendra Vishwakarma
Some drop down list, for custom fields
Will add few more custom fields
More workflow status like - On Hold, etc..
No assignee at the time of creation of issues for contract issue.
Notifications & assigning tasks to users/groups when tasks are created.
Bulk notify when tasks are created & watchers.
User groups to track issue and get approvals.
Template creation for confluence based on Jira template creation. And as per the tasks in Jira it moves the documents to confluence inside the template.
Total estimation for templates: 20*15 = 300 hours @Karthikh Pandian
# | Main Tasks List | Deliverables | Description | Responsible/Owner | Start Date | End Date | Estimation In Story Points | Estimation( In Hours) |
|---|---|---|---|---|---|---|---|---|
1 | Project Template Creation (High level) - Contract review | Deliverable-1 |
| @YUVARAJ KUNDASI (Unlicensed) |
|
|
| 15 hours per template. |
1.1 | Create a projects (Template project for Contract review and Stock MC w/ Options)https://empyrajira.atlassian.net/browse/AP-2106 | Deliverable-1 |
| @YUVARAJ KUNDASI (Unlicensed) |
|
| 1 | 1 |
1.2 | Create a tasks for contract review Issue typehttps://empyrajira.atlassian.net/browse/AP-2107 | Deliverable-1 |
| @YUVARAJ KUNDASI (Unlicensed) |
|
| 3 | 4 |
1.3 | Create issues in the project for Stock MC w/ Options issue typehttps://empyrajira.atlassian.net/browse/AP-2108 | Deliverable-1 |
| @YUVARAJ KUNDASI (Unlicensed) |
|
| 3 | 4 |
1.4 | Create custom fields based on Makino listhttps://empyrajira.atlassian.net/browse/AP-2109 | Deliverable-1 |
| @YUVARAJ KUNDASI (Unlicensed) |
|
| 5 | 6 |
2 | Contract Review | Deliverable-1 |
| @Sharmendra Vishwakarma |
|
|
|
|
2.1 | UI Design | Deliverable-1 |
|
|
|
|
|
|
2.2.1 | Project Template Selection and Project Creation with Button | Deliverable-1 | Project Template ( Drop down), Project Name (Text Field) , Project Key (Text Field) and Button |
|
|
|
| 1 |
2.2.2 | Custom Field Addition | Deliverable-1 | Dynamic addition of Fields and Values ( Name of Custom Field, Value). Note: Only Text anNumber, Single select and multi-select fields are supported. Note: No Lookup fields supported.
|
|
|
|
| 12+7 =19 |
2.2 | Business Logic | Deliverable-2 |
|
|
|
|
|
|
2.2.1 | Getting the project template list | Deliverable-2 | Call APIs and get the details |
|
|
|
| 4 |
2.2.2 | Getting the issue type list | Deliverable-2 | Call APIs and get the details |
|
|
|
| 4 |
2.2.3 | Project key validation | Deliverable-2 | Call APIs and get the details |
|
|
|
| 4 |
2.2.4 | Business logic to store (List the custom field & value) | Deliverable-2 | Provision for the admin to add the custom field in the screen. In UI, we should have , add-add option with custom field and value |
|
|
|
| 12 |
2.2.4 | Create project logic with configurations | Deliverable-2 |
|
|
|
|
| 40 |
2.3 | Modular Testing(Contract Review Testing) | Deliverable-2 |
|
|
|
|
| 20 |
3 | SO Process | Deliverable-3 |
|
|
|
|
|
|
3.1 | UI Design | Deliverable-3 |
|
|
|
|
| 14 |
3.1.1 | Project Template Selection, Issue Type Selection, Target Project Selection, Create Issue Button | Deliverable-3 |
|
|
|
|
| 4 |
3.2 | Business Logic | Deliverable-4 |
|
|
|
|
|
|
3.2.1 | Getting the project template list | Deliverable-4 |
|
|
|
|
| 4 |
3.2.2 | Getting the issue type list | Deliverable-4 |
|
|
|
|
| 4 |
3.2.3 | Getting target project list | Deliverable-4 |
|
|
|
|
| 4 |
3.2.4 | Create Issues logic | Deliverable-4 | It will pull all the tasks against the selected issue types from the template.Copy all the contract per-defined fields values in issue screen |
|
|
|
| 40 |
3.3 | Modular Testing ( SO Process) | Deliverable-4 |
|
|
|
|
| 16 |
3.4 | Regression ( 1,2,3) | Deliverable-5 |
|
|
|
|
| 24 |
4 | Logger Implementation | Deliverable-1, Deliverable-2,Deliverable-3,Deliverable-4 |
|
|
|
|
| 32 |
5 | Build Process Pipeline |
| Develop a pipeline to process the request as series of steps ( Creation of projects and underlying issues with attachments) |
|
|
|
| 80 |
5 | UAT |
|
|
|
|
|
| 32 |
6 | Production Deployment | Deliverable-6 |
|
|
|
|
|
|
6.1 | Infa Readiness |
|
|
|
|
|
| 24 |
6.2 | Deployment |
|
|
|
|
|
| 16 |
6.3 | Post Deployment Check |
|
|
|
|
|
| 8 |
7 | Documentation |
|
|
|
|
|
|
|
7.1 | Deployment Doc |
|
|
|
|
|
|
|
7.2 | User Doc for App |
|
|
|
|
|
|
|
8 | Hyper-care |
|
|
|
|
|
| 40 |
| Total |
|
|
|
|
|
| 454 |
Assumptions
All the required fields should be mapped to Issue Type screen
If any changes are made in the “template” the changes will be reflected to newly created projects ONLY and not the existing project.
Customer will provide list of all the fields and issue types (Any field type inclusion other than Text /Number, Single select and multi-select fields will impact the deliverable timelines).
Link between Jira Cloud and Confluence Server is already in place
While uploading the document, user will mention label of the attachment as an optional parameter
No document search feature from Jira Cloud. User will need to go to Confluence Server to search the document.
Customer will host and maintain the infrastructure for custom app
Empyra will provide infrastructure and hardware requirements
Deliverables
Code Base
Deployment Doc
User Doc for App