Skip to main content

Agile and roadmaps

Last post 01:20 pm May 1, 2018 by Timothy Baffa
4 replies
09:24 am April 28, 2018

Hi

1) Traditionally, we've had our Service Manager define roadmaps for a Product.

How does this work with Agile, is it the Product owner or the Development team.

2) Traditionally, we've had this concept where  Service Manager liases with the business for requirements. These requirements are then passed over to the architecture team who then pass to the development who code the software, then pass over to an Operations team. Each step is more and more removed from the customer.

With Agile, is it the case that the developers work very closely with the business?

 

 


02:31 pm April 29, 2018



Hi Jason,

I have working in an environment that looks like yours. Couple of years ago we have change our way of working and adopting scrum.

We have done the following:

1. Introduced the role of product owner, responsible for stakeholder management and gathering wishes, setting vision, resulting in a backlog full of userstories. Basically what your service manager seems to do right now.

2. Further, we have made the development team responsible end-to-end (both operations as change) for the product.

3. This means that the team estimates the amount of work, the complexity, that they foresee for implementing the user stories on the backlog. The architect is only giving guidelines and 'boundaries' where the team can work in. There is no tollgate or such for design or implementation.

4. What my experience is, is that while estimating the work, direct contact with the customers is preferred. Even better, have the customers participate during development of the feature that is implemented.


04:01 pm April 30, 2018

Yes, to some extent the developers should work close (depends on definition) with the business, but in general the Service Manager responsibilities you provided do seem to resonate with these of a Product Owner.


09:19 pm April 30, 2018

With Agile, is it the case that the developers work very closely with the business?

Yes, although there may be roles with clear responsibilities. In Scrum the Product Owner would be accountable for product value, including any roadmap for delivery and authoritative representation of business interests.


01:20 pm May 1, 2018

The 4th Principle of the Agile Manifesto reads:

Business people and developers must work together daily throughout the project.

 


By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.