![]() may, but is not obliged to, monitor submissions. Forum members who post content deemed unsuitable by may have their access revoked at any time, without warning. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Unsuitable post content includes, but is not limited to, Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. may, at its discretion, remove any post that it deems unsuitable for these forums. does not endorse user-submitted content or the content of links to any third-party websites. 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. For privacy concerns, we cannot allow you to post email addresses. Please note that the first and last name from your member profile will be displayed next to any topic or comment you post on the forums. There are definitely good reasons to separate out spikes and enablement from Product Backlog Refinement, depending on the needs of the team and the organization.īy posting on our forums you are agreeing to our Terms of Use. Enablement work that delivers new infrastructure or architectural changes may need to be tracked and have traceability as part of change management and compliance or for coordination across multiple teams. Spike work that require a significant (to be defined by the team or organization) amount of effort beyond the normal Product Backlog Refinement work may need to be made visible on a Product Backlog so dependencies between that and other work can be made transparent to stakeholders when discussing order and priority. However, there are cases where I can see it being used to identify and explicitly track "spike" or "enablement" work and not just simply call it part of Product Backlog Refinement. Capacity for Spike-like work is built into each and every Sprint and is considered during the Sprint Planning. In cloud architecture, automation is used to easily scale up system resources to accommodate a spike in demand for compute power, deploy applications to. This probably accounts for a lot of work that would normally be considered a Spike in Extreme Programming terminology. Scrum calls for a percentage of time allocated to each Sprint for Product Backlog Refinement. If it does neither convincingly, the so-called “enabler” could be a euphemism for a staged activity in which at least some development work is being waterfalled out. If you find an item being described as an “enabler”, it may be worth querying what value it delivers itself, or how it would otherwise cause the product to be inspected and adapted. To track such work items, in a ticketing system, a new user story can be set up for each spike, for organization purposes.įollowing a spike, the results (a new design, a refined workflow, etc.) are shared and discussed with the team.I’d suggest you may wish to consider a “spike” as a Product Backlog refinement activity a time-boxed technical investigation which is just enough to allow an item to be estimated and brought to “ready”. A functional spike is used to determine the interaction with a new feature or implementation. The technical spike is used more often for evaluating the impact new technology has on the current implementation.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |