This post originated from an RSS feed registered with .NET Buzz
by Steve Hebert.
Original Post: Lean Thought: Microsoft Project and UML
Feed Title: Steve Hebert's Development Blog
Feed URL: /error.htm?aspxerrorpath=/blogs/steve.hebert/rss.aspx
Feed Description: .Steve's .Blog - Including .Net, SQL Server, .Math and everything in between
Here's a thought I just had - Microsoft Project is to Software Project Management as UML is to Code
UML is not architecture nor is it code design. UML is a static picture that describes intent
at a given point in time. These diagrams may have significant value at
certain points in time and zero value at other points. The final
code rarely looks like the intended UML because UML is not an
implementation tool. Just like inventory, the longer a UML
diagram sits, the more useless and irrelevant it becomes.
- To that point -
Microsoft Project describes a plan's intent. The final project steps rarely look like the actual steps over the course of a sizable software project.
So why do teams create designs with UML and plan with Project? Because
there is use in showing intent at different phases of a project
plan. However, mandating, measuring or driving to either during
the life of a project usually leads to unnecessary and costly work stoppages.
Previous Topic
