Scrum is an iterative incremental process of development commonly used with agile development. Although Scrum was intended for management of software development projects, it can be used to run software maintenance teams, or as a general project/program management approach.
uScrum (uncertainty Scrum) is an agile process developed by a small team at Altitude Software to manage the process of writing user documentation. uScrum manages uncertainty and the unknown, allowing writers to quickly react to changing conditions. uScrum uses orders of ignorance to understand the difficulty of tasks, allowing the team to effectively prioritize regular work together with difficult creative work.
In this article, I will describe Agile and attempt to illuminate a potential minefield for those who are swept up in the fervor of this development trend and want to jump in headlong. Then I will present how practices within User Centred Design (UCD) can mitigate the inherent risks of Agile and how these may be integrated within Agile development approaches.
The authors of this whitepaper have helped many hundreds of teams adopt Scrum. Here they share how CIOs can implement Scrum on an organization-wide basis - the challenges they will face as well as the rewards - and provides a playbook for adopting Scrum in enterprises where software, and lots of it, is the key to competitive success in the marketplace.
Scrum is a proven, Agile software management method that has been widely adopted by organizations seeking to reliably deliver higher quality software. Scrum is a simple process: it has a small set of interrelated practices and rules, is not overly prescriptive, can be learned quickly and produces productivity gains almost immediately.
Provides a brief overview of the Scrum method as well as 'playbook' of guidelines and tactics for enterprise-wide adoption of Scrum.
Rally's Hubert Smits provides a broad introduction to concepts of Agile software development and Agile methods. The talk is based on his experience as an Agile coach and Certified Scrum Master. Concepts that are known from waterfall or plan-driven development are transformed to an Agile perspective. Examples are release and iteration planning, progress reporting, meeting formats and scaling projects from 10 people teams to 300 people teams.
This tutorial brings Scrum to life by introducing Scrum principles, process, practices and roles in the form of an actual Sprint timebox. The prioritized, timeboxed topics are presented and delivered as arranged by the tutorial attendees.
In my project portfolio, our release manager—the one who instituted release scrums—wants to standardize on release notes across applications. Many of the projects are in a maintenance period, so releases are planned for each project every month or two on something of a rotating basis. These releases will include small enhancements and bug fixes. One of the challenges of standardizing on release notes is coming up with a release notes process that can efficiently turn out these documents within about a week.
Scrums are part of the particular flavor of Agile methodology project teams use in the portfolio I work in. The managers recently borrowed the scrum concept for release preparation because the projects in this portfolio are interrelated and often have to be released together. This means that a lot of coordination is needed so that there are no surprises for anyone. Because technical writers enjoy surprises as little as anyone else, I get invited to these scrums. This lets me know how much time I have to put release notes together and whether there are any last-minute changes I need to make to them or to any other documentation.