Project Management

Please login or join to subscribe to this thread

DevOps use

linkedin twitter facebook   Agile   Requirements Management  
avatar
Constance Fiorito Agile Project Manager Intern| Sword Group France
Hello,

I am starting an intern position as Scrum Master and have to implement the agile methodology within a small software development team using DevOps.

First, I need to restructure the architecture of the work items because for now User Stories of all sorts are created randomly and there is no link to any Features or so.
Some Features have already been created but they are, in fact, no more no less the functionalities of the software in development.

I read on Microsoft Support that Features in DevOps should be shippable.
I was wondering if the way they are using Features was okay to get the best out of DevOps tool or if I had to change the whole use/definition of it as long as those Features won't be Done or "delivered" at some point and are just continuously improved.

I hope my question is clear enough.

Thank you for any thoughts.

Constance
Sort By:
avatar
Aaron Porter
Community Champion
IT Director| Blade HQ Payson, UT, United States
Features can be made up of smaller increments, which should be shippable.

Why is your first step to restructure the architecture of the work items?

You could be right, however, it would be worthwhile to understand the value stream and how work is performed in the value stream. There may be other obstacles that could be handled more quickly that bring you closer to CI/CD. Unless the current architecture of work items is impeding the delivery of value, it may just be fine tuning.
...
1 reply by Constance Fiorito
Feb 08, 2022 3:47 AM
Constance Fiorito
...
Aaron,
Thank you a lot for your answer.

I thought the architecture of work items was important as long as it would at least impact progress reports.
Of course other elements like tests integration will play a major role into bringing us closer to CI/CD.
avatar
Kiron Bondale Retired | Mentor| Retired Welland, Ontario, Canada
Constance -

Have you ever explored user story mapping? If not, you might want to read Jeff Patton's book on the subject as it is a good way to connect "the forest" to "the trees" of your product...

Kiron
...
1 reply by Constance Fiorito
Feb 08, 2022 10:30 AM
Constance Fiorito
...
Kiron,

For now the visual story mapping is empty as long as there is no link between work items.
I will have a look at Jeff Patton’s book.
Thank you!
avatar
Constance Fiorito Agile Project Manager Intern| Sword Group France
Feb 07, 2022 3:21 PM
Replying to Aaron Porter
...
Features can be made up of smaller increments, which should be shippable.

Why is your first step to restructure the architecture of the work items?

You could be right, however, it would be worthwhile to understand the value stream and how work is performed in the value stream. There may be other obstacles that could be handled more quickly that bring you closer to CI/CD. Unless the current architecture of work items is impeding the delivery of value, it may just be fine tuning.
Aaron,
Thank you a lot for your answer.

I thought the architecture of work items was important as long as it would at least impact progress reports.
Of course other elements like tests integration will play a major role into bringing us closer to CI/CD.
avatar
Sergio Luis Conte Helping to create solutions for everyone| Worldwide based Organizations Buenos Aires, Argentina
We are using MS Azure DevOps to manage our life cycle and trazability between features and user stories is supported in the tool.
avatar
Constance Fiorito Agile Project Manager Intern| Sword Group France
Feb 07, 2022 5:58 PM
Replying to Kiron Bondale
...
Constance -

Have you ever explored user story mapping? If not, you might want to read Jeff Patton's book on the subject as it is a good way to connect "the forest" to "the trees" of your product...

Kiron
Kiron,

For now the visual story mapping is empty as long as there is no link between work items.
I will have a look at Jeff Patton’s book.
Thank you!
avatar
Kamal Deep Pareek SEO Analyst| Dev Technosys USA, United States

Hi Constance,



You're on the right track. In Azure DevOps, Features should ideally be shippable increments that deliver customer value. If existing Features are merely functional areas and not tied to delivery, it's best to redefine them. Consider organizing work hierarchically: Epics → Features → User Stories → Tasks. Align Features with valuable deliverables or milestones, even if continuously improved. Use tags or Areas to group ongoing capabilities if needed. This structure will enhance traceability, planning, and reporting in DevOps. Gradually refactor the backlog to reflect this model without disrupting current workflows.



Best of luck in your Scrum Master journey!

Please login or join to reply

Content ID:
ADVERTISEMENTS

"I never thought much of the courage of a lion-tamer. Inside the cage he is at least safe from people."

- George Bernard Shaw

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