The Scrum approach to agile software development marks a dramatic departure from waterfall management. Scrum and other agile methods were inspired by its shortcomings. Scrum emphasizes collaboration, functioning software, team self management, and the flexibility to adapt to emerging business realities.

9th
NOV

Strategic Vision and Scrum

Posted by admin under Agile and Scrum, Agile Manifesto, Agile Principles, Scrum Basics, Scrum Discussion, Scrum Transitions

When organizations adopt an agile approach to development like Scrum there is so much focus on the iterative nature of agile development that long range vision and strategic product design can get lost. Jimi Fosdick is doing a webinar on November 28 to discuss the need to include long term product vision, coherent user experience and User Centered design and architecture along with specific best practices for achieving a coherent product that delights users.

Topics will include:
• Discussion of Product Vision and approaches to crafting a compelling overall vision for products
• Discussion of User-Centered/Value-Driven design and approaches to incorporating user experience (UX) and software architecture early in the development process
• Explanation of the pitfalls of a lack of vision and so-called “hybrid” models for incorporating UX and architecture into Scrum Projects

You can register for the webinar here

Tags: , , , , , , , , , , , ,

24th
OCT

Scrum User Stories

Posted by admin under Scrum Basics

In Scrum, work is typically expressed in the Product Backlog as user stories. A team may write its user stories in a number of ways as long as they are written from the perspective of the end user. Team members are encouraged to think of their work from the perspective of who will use it (hence “user” story). A team can express a story as a noun (i.e. “text message” on a cell phone project) or a sentence or phrase (i.e. “debug GPS tracking system”).

Many Scrum teams have adopted the user story template popularized by Rachel Davies and Mike Cohn, which identifies who the end user is, what the end user wants, and why in a single sentence. This model of the user story is often written like this: “As a [end user role], I want [the desire] so that [the rationale].

User stories are intended to help teams and Product Owners focus on the customer. Thus, it would be inappropriate to write “As a Product Owner I want ___” or “As a software architect I want ____.” Work that doesn’t directly serve a customer need is better expressed as a Sprint Task related to a User Story. These are identified during the Sprint Planning Meeting.

Watch a Product Owner and Scrum Team write user stories. (Around the 7 minute mark.)

User_story

Tags: , ,

Scrum Training Courses