Home
Mairon Croes's Library tagged → View Popular
Implementing Scrum
From site: "There are a lot of great sites out there about Scrum and Agile Software Development. This site gives you real solutions on how to start conversations about delivering working software to your customers on a regular basis."
10 Free SVN & Project Hosting Services @ Straw Dogs
From site: "Here’s a rundown of 6 free SVN hosting and project management offerings I like the look of. UPDATED: As of Nov 4th 2008 (Now with 10 services reviewed!)"
Slashdot | Agile Software Development with Scrum
A person's review of a book on Scrum and Scrum itself with comparisons to XP (eXtreme Programming).
-
You have the Scrum Master, who is more or less half technical lead and half project manager.
-
The book is careful to point out that any and all of these "missing" practices (refactoring, unit testing et al) may be used but that Scrum does not prescribe them. And that's fine, but I'm evaluating it on what it actually does prescribe - if Scrum can take credit for what it does not prescribe, they it can lay claim to infinite credit after all. This is maybe a small point but it's important to what follows. Because Scrum does not tell us what to do in these areas, I'm assuming that they are free to vary.
- 5 more annotations...
InfoQ: Case study: Distributed Scrum Project for Dutch Railways
From site: "In this article, we describe how we successfully executed a large (20 man-years, 100.000+ lines of code) Scrum project, one which had already been scrapped once under a traditional approach, and which included developers in both India and the Netherlands."
-
We applied automated testing during the project to allow us to deliver tested software at the end of each Sprint, without regression bugs. Even as the system grew we managed to do this with only one tester per eight-person Scrum team while maintaining high quality: the external testing team found less than 1 defect per KLOC.
We automated tests on two levels: unit tests and acceptance tests. For the former, we used JUnit and measured code coverage using Clover, using a target for server-side code of 80% coverage. Acceptance tests were automated using FitNesse. For every implemented user story, a set of acceptance tests was written in FitNesse. Having an extensive test suite, regression bugs were usually found and fixed during the Sprint. Another advantage of this approach is that the testers can be effective from the start of the Sprint, creating test cases before the user story is implemented.
There was one area where we struggled with automated testing. Part of the system was an application with a complicated rich user interface. Automating tests for this proved to be harder than automating server-side tests. Therefore we largely depend on manual testing for user interface-specific functionality. As the system grew, regression testing took more and more time. Even worse, external testers found regression bugs only in this part of the system. Having automated tests could have prevented this. The lesson learned is that, even though automating tests may sometimes be hard, it will pay off when it counts, late in the project.
-
Thanks for sharing your success story. I have a doubt about scrum approach. When a sprint is completed and at the end still there are some bugs which could not be fixed during sprint period, these bugs will be items in one of next sprints based on priority; what happens to the output from previous sprint? Is it deployed with accepted bugs or it is held back till the next workable output? I understand that low priority bugs might not prevent feature release but what approach is taken for feature release which has still some critical/major bugs pending resolution?
Which techniques did you use for estimation?
If there is considerable difference in high level estimation done at the time of story writing (product backlog) and planning poker during sprint planning, what approach would you suggest?
Thanks in advance. I ma learning to use Scrum :) - 3 more annotations...
InfoQ: Scrum Checklists
From site: "The SPRiNT-iT coaches, including Scrum Trainer Boris Gloger, have abstracted the basics from the major Scrum books and added their collective experience to produce the Scrum Checklists mini-book. This compact collection of checks and actions will enable team members to facilitate all Scrum Meetings and create the Scrum artifacts."
InfoQ: Version Control for Multiple Agile Teams
From site: "This paper describes an example of how to handle version control in an agile environment with multiple teams - it is the scheme that we migrated to at the company described in "Scrum and XP from the Trenches"."
Codehaus: Minglyn
From site: "This project is an eclipse plugin to connect to the Mingle Project Management tool. Mingle is a project collaboration and management tool for Agile software development."
Agile PM Tools (Hosted) - Blogpost
Blogpost with a list (with description) of agile software project management tools.
Agile PM Tools (self-Hosted) - Blogpost
Blogpost with a list (with description) of self-hosted agile software project management tools.
Agile PM Tools (self-Hosted)
A list (with description) of self-hosted agile software project management tools.
Agile PM Tools (Hosted)
A list (with description) of agile software project management tools.
ExtremePlanner - Agile Project Management and Issue Tracking for Distributed Software Teams
From site: "ExtremePlanner is a browser-based Agile project management solution for modern software development teams that work from different locations. Unlike traditional project management tools that focus primarily on task lists, ExtremePlanner concentrates on planning and tracking the progress of features (or user stories) that have actual business value to customers."
Acunote - Welcome!
From site: "Acunote is an Agile project management tool.
It is built on the innovative lightweight Scrum process and is focused on the day-to-day steps needed to achieve the goal."
Agile Software Lifecycle Management
Fom site: "Rally scales your software agility by promoting the same lean and adaptive principles championed by Toyota and Dell to dramatically shorten development cycles, increase quality and speed value delivery. You can rely on Rally's leadership to help your organization break free of older, plan-based methodologies that are too risky, slow and wasteful for today's business climate."
Agile software development - Wikipedia, the free encyclopedia
From site: "Agile software development is a conceptual framework for software engineering that promotes development iterations throughout the life-cycle of the project."
VisionProject :: Web based tool for project management, issue tracking, task tracking, bug tracking and customer support
From site: "VisionProject is a web based software that makes it easy to manage all your internal or clients projects in an efficient way saving you time and money. VisionProject supports the agile way to manage projects but can also be used in projects managed in a more traditional way "
TRICHORD is a team centered Agile project management Tool.
From site: "TRICHORD is a simple Agile project management tool that helps developers and managers track project status at a glance from three viewpoints (Time, Task, Team), using "Kanban Board" (a Just-In-Time pull control method in Toyota Production System)."
Accelerating Software Development | Assembla
From site: "Use Assembla spaces for rapid software development, and agile team collaboration. Get free workspaces with unlimited team size and integrated tools like wiki, discussion, alerts, chat, ticketing, Trac, Git and Subversion."
Selected Tags
Related Tags
Sponsored Links
Top Contributors
Groups interested in scrum
-
Méthode analyse
six sigma, lean, lean 6 sig...
Items: 37 | Visits: 32
Created by: Stéphane Bertho
-
SCRUM
about agile SCRUM
Items: 1 | Visits: 12
Created by: Mattias Schertell
Highlighter, Sticky notes, Tagging, Groups and Network: integrated suite dramatically boosting research productivity. Learn more »
Join Diigo