User Stories / Story Points

User stories are one of the primary development artifacts for Scrum teams. They are a short description of the feature as told from the perspective of the person (stakeholder) who desired some new capability from a current service, system or application. Many Scrum teams have adopted the user story template developed by Mike Cohn, which identified who the end user is, what the end user wants and why in a single sentence. This template is most often written like this: "As a (type of user), I want (some goal) so that (some reason)." Example: As an Incident Process Owner, I want to see a release of known errors in order to do appropriate service desk staff training. In this way team members are encouraged to think of their work from the perspective of who will use it, ensuring requirements get met and value is delivered.

User stories are narrative texts that describe an interaction of the user and the service. It focuses on the value that a user gains from utilizing the service. A user story is a simile for the work being done. They are often written on index cards or sticky notes and arranged on walls or tables to facilitate planning and discussion, the end result being collaboration and just in time definition over documentation.

A good user story uses the "INVEST" model:

Independent. Reduced dependencies = easier to plan
Negotiable. Details added via collaboration
Valuable. Provides value to the customer
Estimable. Too big or too vague = not estimable
Small. Can be done in less than a week by the team
Testable. Good acceptance criteria

Story point is a subjective measure used by Scrum teams. It is used to measure the work required to implement a story. In simple terms it's a number that tells the team how hard the story is. Hard could be related to complexity, unknowns and effort. Teams can use a modified version of a Fibonacci sequence (https://www.mathsisfun.com/numbers/fibonacci-sequence.html) to help understand the amount of effort that any given story will entail. Story points do not relate to hours, so if that will be a requirement (most of the time it is) then you shouldn't use story points within project management.

To gain knowledge and certifications in DevOps Foundation follow this link: http://www.itsmacademy.com/dofnd/

Comments

The Four Ps of Service Design - It’s not all about Technology

People ask me why I think that many designs and projects often fail. The most common answer is from a lack of preparation and management. Many IT organizations just think about the technology (product) implementation and fail to understand the risks of not planning for the effective and efficient use of the four Ps: People, Process, Products (services, technology and tools) and Partners (suppliers, manufacturers and vendors). A holistic approach should be adopted for all Service Design aspects and areas to ensure consistency and integration within all activities and processes across the entire IT environment, providing end to end business-related functionality and quality. (SD 2.4.2) People: Have to have proper skills and possess the necessary competencies in order to get involved in the provision of IT services. The right skills, the right knowledge, the right level of experience must be kept current and aligned to the business needs. Products: These are the technology managem

What Is A Service Offering?

The ITIL4 Best Practice Guidance defines a “Service Offering” as a description of one or more services designed to address the needs of a target customer or group . As a service provider, we can’t stop there! We must know what the contracts of our service offering are and be able to put them into context as required by the customer. Let’s explore the three elements that comprise a Service Offering. A “Service Offering” may include: Goods, Access to Resources, and Service Actions Goods – When we think of “Goods” within a service offering these are the items where ownership is transferred to the consumer and the consumer takes responsibility for the future use of these goods. Example of goods that are being provided in the offering – If this is a hotel service then toiletries or chocolates are yours to take with you. You the consumer own these and they are yours to take with you. Note: Goods may not always be provided for every Service Offe

What is the difference between Process Owner, Process Manager and Process Practitioner?

I was recently asked to clarify the roles of the Process Owner, Process Manager and Process Practitioner and wanted to share this with you. Roles and Responsibilities: Process Owner – this individual is “Accountable” for the process. They are the goto person and represent this process across the entire organization. They will ensure that the process is clearly defined, designed and documented. They will ensure that the process has a set of Policies for governance. Example: The process owner for Incident management will ensure that all of the activities to Identify, Record, Categorize, Investigate, … all the way to closing the incident are defined and documented with clearly defined roles, responsibilities, handoffs, and deliverables. An example of a policy in could be… “All Incidents must be logged”. Policies are rules that govern the process. Process Owner ensures that all Process activities, (what to do), Procedures (details on how to perform the activity) and the

Search