Which issues we had at the beginning of our journey?
-
Lack of unification (Jira projects, workflows, permissions)
-
No Jira administration and monitoring
-
QA complains
-
ZERO documentation
-
Problems with reporting
.. and many others
What we accomplished?
-
Workflow unification
– Almost all projects in our Company Space have the same Workflow
– PMs are responsible for adding this Workflow when they start new Project -
Permission schemes
– Closed & secured Project’s spaces
– Easy to add Client with restricted permissions -
Clean-up Jira items
– Cleaned Projects / Confluence space
– Actual Users & admins
– Add-ons clean-up -
Documentation
– Project Passport
– Handover check-list
– Communication (Internal, External)
– QA documentation for PMs
– Tracking documentation
– Reporting tips & tricks
– Planning, Estimation (in progress) -
Code Review process (in progress)
– Code Review discussions
– Workflow -
QA Process
– Divided QA resources by PMs
– Improved communication & engagement processes between QA – PM
– Better QA on projects → Higher project’s quality
– Made QA team happy -
Support process (in progress)
– Jira Service Management solution
– Support Workflow
– Documentation -
Researches, testing & researches again…
– Tracking tool – Tempo, Integration TD – Jira
– Reporting Coreteka
– Projectrak
– EazyBI
– Atomizations -
Mentoring
– Communication cases
– Weekly reports
– JIRA assistance, administration
What are the next steps?
-
Reporting system
-
Workload optimisation
-
Jira atomization
-
Improve documentation (repo)
Leave a Reply
You must be logged in to post a comment.