Project Management

Please login or join to subscribe to this thread

Requirement Gathering for Devops automation Requirements?

linkedin twitter facebook   Agile   Consulting   Requirements Management  
avatar
Sadeesh Narendran Business Analyst| Oracle Bangalore, Karnataka, India
I am part of Devops team automating many production support activities. I need a good template o procedure on how to collect complete requirement of an automation from Product Owner.
Sort By:
avatar
Kiron Bondale Retired | Mentor| Retired Welland, Ontario, Canada
Sadeesh -

Assuming this is an existing manual procedure, wouldn't there be a procedure guide or other type of Standard Operating Procedure (e.g. build book) artifact which would provide a starting point for the discussion with the PO?

I'd also expect you'll need to engage more stakeholders than just the PO - the overall solution lead and key control partners (e.g. IT security) might need to also provide their requirements...

Kiron
...
1 reply by Sadeesh Narendran
Aug 09, 2018 4:01 AM
Sadeesh Narendran
...
Thanks Kiron! At present we dont have any documentation work. Once a ticket is raised developer starts working on the requirement, initially to understand the requirement. So my search is to find if there is any better way than just raising the requirement as ticket, is there any document which we can request PO to provide so that developer would be in a better position to start of.
avatar
Sadeesh Narendran Business Analyst| Oracle Bangalore, Karnataka, India
Aug 08, 2018 3:17 PM
Replying to Kiron Bondale
...
Sadeesh -

Assuming this is an existing manual procedure, wouldn't there be a procedure guide or other type of Standard Operating Procedure (e.g. build book) artifact which would provide a starting point for the discussion with the PO?

I'd also expect you'll need to engage more stakeholders than just the PO - the overall solution lead and key control partners (e.g. IT security) might need to also provide their requirements...

Kiron
Thanks Kiron! At present we dont have any documentation work. Once a ticket is raised developer starts working on the requirement, initially to understand the requirement. So my search is to find if there is any better way than just raising the requirement as ticket, is there any document which we can request PO to provide so that developer would be in a better position to start of.
avatar
Tim PM Project Manager| NHS Yes, United Kingdom
Hi Sadeesh, how about using Jira? https://www.atlassian.com/software/jira
avatar
Sergio Luis Conte Helping to create solutions for everyone| Worldwide based Organizations Buenos Aires, Argentina
From your answer to Kiron I understand that your focus is to solve the problem to "accelerate" the understanding of a requirement when the developer take it. Let me say you never get requirements. You take needs/wants/desires/ etc that somebody must "translate" into requirements. Or better said, well formed requirements. I can write a lot because I have practical experience, not only theorical (in fact, in my actual work place, I am in charge to solve this type of things but my recommendation is reading and understanding this IEEE standard: IEEE Std 1233, You will find it into the internet. Just to comment while your focus is this take into account that the whole impacts are above on that.

Please login or join to reply

Content ID:
ADVERTISEMENTS

"All progress is based upon a universal innate desire on the part of every organism to live beyond its income."

- Samuel Butler

ADVERTISEMENT

Sponsors







Vendor Events

See all Vendor Events

Newsletters

Jun 3: The Career Problem Facing New PMs
May 20: Your PM Career as a Project Life Cycle
May 13: The Big Lie After Layoffs

See all newsletters