The Artima Developer Community
Sponsored Link

Agile Buzz Forum
Why MS Project Sucks for Iterative Development? Part II

0 replies on 1 page.

Welcome Guest
  Sign In

Go back to the topic listing  Back to Topic List Click to reply to this topic  Reply to this Topic Click to search messages in this forum  Search Forum Click for a threaded view of the topic  Threaded View   
Previous Topic   Next Topic
Flat View: This topic has 0 replies on 1 page
Michael

Posts: 1010
Nickname: targetp
Registered: Sep, 2004

Michael is a leader of TargetProcess.com project
Why MS Project Sucks for Iterative Development? Part II Posted: Feb 2, 2006 4:18 AM
Reply to this message Reply

This post originated from an RSS feed registered with Agile Buzz by Michael.
Original Post: Why MS Project Sucks for Iterative Development? Part II
Feed Title: TargetProcess Blog
Feed URL: http://feeds2.feedburner.com/Targetprocess
Feed Description: Agile development and processes, project management, programming practices, patterns, XP(eXtreme Programming), SCRUM, Crystal, TargetProcess news, what else?
Latest Agile Buzz Posts
Latest Agile Buzz Posts by Michael
Latest Posts From TargetProcess Blog

Advertisement
Hummer and Warm Wax See Part I. Let's take an average software project with full plan created up-front. It appeast that it is hard to support project plan in actual state using MS Project. It is hard to reflect real progress. But why? MS Project is great software, it should be easy. And it is easy in many cases, but not in software development. MS Project is useful when: Project is very small

Read: Why MS Project Sucks for Iterative Development? Part II

Topic: SubFork and ThreadedSUnit Previous Topic   Next Topic Topic: Smalltalk Experience at LWNW/Smalltalk Solutions

Sponsored Links



Google
  Web Artima.com   

Copyright © 1996-2019 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use