Hello,
recently completed solution architect training and got process assessment toll document from training.
My requirement is to give timeline for project which i am going to start in few days.
Project in short - i need to fetch ticket data using API from Jira and need to work on data in Jira and again update ticket with status and comment. need to process total 4 workorders in Jira.
can you please help me how to use this document and how to get timeline for project.
Break your project into tasks (API connection, data processing, updating tickets). Use the assessment tool to rate each task’s complexity and estimate effort. Add extra time for testing and issues. Add all times to get your total timeline. Since it’s only 4 workorders, the timeline should be relatively short.
on highlevel number of APIs, number of screens , formatting and manipulations any extra reports needed are to be considered and
for Easy - 2-4 weeks
Medium - 4-6
Complex-6-8
High - 8+
process assessment tool has these as fields fill the data and it would show complexity and you can get time
cheers
Process Assessment Tool.xlsx (102.3 KB)
i can see so many tabs here ,exactly which tab i need to utilize and what to enter please guide
Assessment Sheet
This is the main input. Fill one row for your Jira process. Enter process name, frequency, volume (4 workorders), average handling time, error rate, and how stable Jira/API is. Keep values realistic and simple.
Scorecard
Don’t change much here. This sheet auto-calculates based on what you enter in the Assessment Sheet. Just review the feasibility and automation potential scores.
Assumptions Effort
Here you estimate effort in days or hours. Add rough numbers for development, testing, deployment, and buffer. This is where your project timeline mainly comes from.
Multiple Process Assessment
You can mostly ignore this since you have only one process. It’s used when comparing many processes together.
In short: fill Assessment Sheet properly → check Scorecard → estimate days in Assumptions Effort → that becomes your project timeline.
At a high level, factors like number of APIs, screens involved, data formatting/manipulation, and additional reporting requirements are considered during assessment. Based on these inputs, the Process Assessment Tool automatically determines complexity and estimated timelines: Easy (2–4 weeks), Medium (4–6 weeks), Complex (6–8 weeks), and High (8+ weeks). This helps standardize effort estimation and planning.
Use Assessment Sheet sheet to fill data for your process.
For your Jira API process, select Digital and Structured.
You’re working with API data (JSON), no documents or human interpretation involved, and the data format is consistent. The other options are for paper-based, email, PDF, or mixed inputs, which don’t apply here.
When the data is structured (fixed design)-- You can select structured.
Digital means - when its a non-scanned pdf (basically you can copy data from pdf directly) and vice-versa for non-digital.
Since your’s is API data, select Digital and Structured.
Yes, that’s correct.
Structured means the data follows a fixed format, and digital means it’s machine-readable (not scanned). Since your data is coming directly from an API and follows a defined structure, the right choice here is Digital and Structured.
not understood below question
1]What is the volume of transactions/frequency (number of times the process is ran/selected frequency)?
2]What is the average time it takes for the process to be ran once (average handling time/transaction)?
so we are getting around 20 tickets daily mans around 100 tickets in a week and for each tikcet we need to process around 5-10 users.so what i need to answer 1 st question?
2 nd question is about mnual process? or automation process? manually it takes around 15-20 mins and with automation it will get done in 5 mins so exactly what i need to answer
Q1 is about how many times the process runs. Treat one Jira ticket as one transaction, so answer around 20 tickets per day (or ~100 per week).
Q2 is about the current manual effort, not automation. So enter the manual handling time per ticket, which is about 15–20 minutes.
not understood assumption sheet
so our pocess includes project manager who is not directly involved in development or documentation but he is process owner, then comes business analyst so they are now manually working on tikcets and have idea about process so will create document and i am as a senior developer and one developer/architect under me who is working on all infra,development ,testing. so how can i give number hours or days? please give example
Your process fits Low to Medium effort. You’re not expected to give exact hours, just approximate involvement.
Example you can assume:
Select the closest values in the Low or Medium effort column. The sheet will auto-calculate duration and total effort.
ok i have updated as per you and rest i have kept as 0 and medium and high kep as it is
what is the average duration and what i need to put in that?
and now we have updated hour wise right?
so 224 hours = 9 days 488 - 17 days and 1296 - 54 days this is how the calculation is am i right?
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.
