Back to Forum

Scoping and Scrum

Last post 08:03 pm May 25, 2018 by Vikram panmand
2 replies
Melissa Foley
07:09 pm May 24, 2018

Hi,

I work for a Salesforce consulting company and we implement Salesforce (and other solutions) for clients.  We have a very difficult problem to solve that we've been trying to address for about a year. Our consultants operate as scrum teams during client engagements but we often run into hours issues on the projects, ie. they take more hours than initially scoped. Project timelines aren't usually a problem as the scrum pace helps support delivery. We're trying to change the way our Sales team scopes in order to support our scrum process but having problems making this shift. Has anyone accomplished this? We've tried creating user stories during the scoping process to get clients thinking about the process but that still isn't giving us accurate "scopes" (mostly because experts aren't consulted during that initial user story creation). It seems pointless to scope for scrum but if we don't scope, what do we give to clients?

 

Thanks for any input or suggestions!

Melissa Foley

Ian Mitchell
10:10 pm May 24, 2018

It seems pointless to scope for scrum but if we don't scope, what do we give to clients?

Why not offer them the ability to change scope in a complex and uncertain environment, so value delivery can be evidenced by means of empirical control?

If that isn't what your sales team are selling, it might be instructive to find out why not.

Vikram panmand
08:24 am May 25, 2018

Hi Melissa,

You need to modify many process to get the delivery from agile 

We were having the same problems initially however we asked the sales team to create user stories for 2 weeks.

These stories were used as Product backlog for n+2 sprint  given n is the current sprint, So the time line for sales team was same as 2 weeks to create user stories.

Once the user stories have been updated we ask the SME/Client to review them asap and close out any reviews in the same week.

Next week these user stories were Estimated and we are in (n+1 sprint). so were good with creating the product backlog with the sales team.

Remember you need to be good with estimation technique, you need to use a good method for estimation.

Also the team is not delivering as they didnt see the user stories before the start of sprint.

Please let me know if this helps so that i can suggest what more changes needs to be donw

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.