Category:Project Management

From LentzWiki

Jump to: navigation, search

Project management is the discipline of defining and achieving targets while optimizing the use of resources (time, money, people, space, etc). Thus, it could be classified into several models: time, cost, scope, and intangibles.

Of particular interest here are distributed development/business environments, for instance the meta-national RDBMS company MySQL AB, but actually also many Open Source projects (not that I dare suggest that most of these projects are actually managed in any way ;-)


Contents

Agile Project Management with Scrum

Scrum is an agile, lightweight process that can be used to manage and control software and product development using iterative, incremental practices.

  • The Scrum Development Process - Mountain Goat Software
  • Earned-Value and Burn Charts by Alistair Cockburn - Burn charts have become a favorite way to give visibility into a project's progress. They are extremely simple and astonishingly powerful. They reveal the strategy being used, show the progress made against predictions, and open the door to discussions about how best to proceed, including the difficult discussions about whether to cut scope or extend the schedule.

Companies/Education

Tools

Scrum in Distributed Environments

  • Adaptive Engineering of Large Software Projects with Distributed/Outsourced Teams by Sutherland (PatientKeeper), Victorov (StarSoft), Blount (SirsiDynix) - Agile project management with Scrum derives from Takeuchi and Nonaka analyses of best practices in companies like Fuji-Xerox, Honda, Canon, and Toyota. Toyota routinely achieves four times the productivity and 12 times the quality of competitors. The Scrum development process was designed for complex adaptive systems and depends on self-organization of teams. Can Scrum achieve Toyota level performance for globally distributed engineering teams? Two Agile companies, SirsiDynix using Scrum, and StarSoft Development Laboratories using Scrum with some XP engineering practices, achieved comparable performance developing a Java application with over 1,000,000 lines of code. Their Horizon project is a completely new implementation of a library system with over 12,500 installed sites. During the most recent year of the project, a distributed team of 56 Scrum developers working from Provo, Utah; Waterloo, Canada; and St. Petersburg, Russia, delivered 671,688 lines of production Java code. Using XP refactoring techniques they then systematically eliminated 275,000 lines of code to achieve better usability, performance, reliability, and maintainability. At 15.3 function points per developer/month, this is one of the most productive projects ever documented. SirsiDynix best practices are similar to those observed on distributed Scrum teams at IDX Systems, radically different than those promoted by PMBOK, and counterintuitive to some practices advocated by the Scrum Alliance. This paper analyzes and recommends new best practices for globally distributed Agile teams.
  • Bridging the Distance by Scott Ambler - Dispersed and distributed development teams may span the globe, but they can be linked through the agile movement's main principle: communication. The two approaches differ: In distributed development, it's the subteams that work at different locales; in dispersed evelopment, individual developers work remotely. This article explores how to overcome the inherent challenges in an agile manner.
  • Distributed Agile (PDF) by Christoph Steindl - A presentation on distributed agile teams. It is focused on the challenges of distributed agile and countermeasures against being distributed.


Tools

Other Resources

Subcategories

There is one subcategory to this category.

S

Pages in category "Project Management"

There are 2 pages in this category.

M

R

Retrieved from "http://wiki.lentz.com.au/Category:Project_Management"
Personal tools