background preloader

Scrum / Agile

Facebook Twitter

Roman's Agile Product Management Tools.


Media Clips. Tools. Training Accreditation. Team. Scrum Role Playing. Scrum is very explicit in its clarification of roles and responsibilities.

Scrum Role Playing

Scrum has only three roles; together they cover the responsibilities needed to ensure a successful project. The Product Owner represents the customer and sets the vision, goals and priorities of the project. The PO then works collaboratively with the team to determine the details during each sprint, accepting work as it is completed. The team members are responsible for determining what can be done within a sprint, making a commitment for a sprint’s worth of work and then organising themselves to deliver the functionality needed.

Sprint Planning Meeting. Agile Story Card Templates - SolutionsIQ. Help Drive Consistency Simplicity – maximizing the amount of work not done – is an essential aspect of achieving organizational agility, and also happens to be one of the twelve Agile Principles behind the Agile Manifesto.

Agile Story Card Templates - SolutionsIQ

A quick way to make your team’s space a little more simple is by having consistent looking Story Cards up on the wall. Why waste time trying to remember the story’s name – always have it in the same place. The same can go for the size, priority and other key elements of a story as well. Our story card templates are designed not only to ensure all key aspects of a User Story are present, but also help you achieve consistency across each of the cards on your wall. What do they look like? 5 Common Mistakes We Make Writing User Stories. Most of the issues with gathering requirements in agile software development and agile testing derive from issues with User Stories.

5 Common Mistakes We Make Writing User Stories

Somehow expressing requirements in such a simple form causes a lot of trouble to agile teams. Of course art of writing good User Stories is the most difficult for new teams starting with a new agile project or these, which freshly transformed development methods to agile software development methodologies. Mistakes made at that point lead to wrong Test Cases, wrong understanding of requirements, and the worst of all wrong implementation which can be direct cause of rejecting the deliverables of the iteration. Lets take a look at the five most common mistakes people make writing User Stories. Introduction to User Stories. FBI's Sentinel Project: 5 Lessons Learned. Agency used agile development and private sector know-how to finish its long-delayed digital case management system.

FBI's Sentinel Project: 5 Lessons Learned

American Red Cross Social Media Command Center (click image for larger view and for slideshow) After six years of development, the FBI says its next-gen digital case management system, Sentinel, is finally up and running. FBI agents can now use the system to manage records electronically, with document templates, drop-down menus, and many other PC-like features. Sentinel had been a case study in federal IT projects gone awry--missed deadlines, budget overruns, feature shortcomings, and a benchmark test last October that pooped out. Keep in mind that Sentinel has roots in an earlier IT project failure, the so-called Virtual Case File system. Whether the system will work as advertised and be accepted by the agency's rank and file remains to be seen. 1. FBI Sentinel Project. Executive Summary: Virtual Case File (or VCF) was a software application developed by the United States Federal Bureau of Investigation(FBI) between 2000 and 2005.

FBI Sentinel Project

The project was not close to completion when it was officially abandoned in January 2005, having turned into a complete fiasco for the FBI. In addition to wasting at least US $100 million, the failure brought widespread criticism to the bureau and its director, Robert S. Mueller III. Key Takeaways: $575 million dollars wasted on the first two attempts at the projectScrum Studio was set up in the basement of the Hoover BuildingStaff reduced from 400 to 40, and in 1 year and $30 million, they were code complete, at a cost savings of more than 90 percent If an organization like the FBI can do this, why can’t yours? Full Case Study: Manifesto for Agile Software Development. Winston W. Royce. Winston Walker Royce (August 15, 1929 – June 7, 1995) was an American computer scientist, director at Lockheed Software Technology Center in Austin, Texas.

Winston W. Royce

He was a pioneer in the field of software development,[1] known for his 1970 paper from which the Waterfall model for software development was mistakenly drawn.[2] Biography[edit] Born in 1929, Royce entered the California Institute of Technology, where he received his BS in physics, his MS in aeronautical engineering and in 1959 his PhD in aeronautical engineering under Julian David Cole[3] with the thesis Transonic flow over a non-lifting, slender body of revolution. Prioritizing Product Backlog Agile Development Practices 2010. Nexus Framework. What is Nexus?

Nexus Framework

Nexus is a framework that drives to the heart of scaling: cross-team dependencies and integration issues. It is an exoskeleton that rests on top of multiple Scrum Teams who work together to create an Integrated Increment. It builds on the Scrum framework and values. The result can be an effective development group of up to 100 people. For larger initiatives, there is Nexus+, a unification of more than one Nexus. Overview - Large Scale Scrum (LeSS) Home -