PUBLIC MARKS from tadanderson with tag EssUP

The SEMAT Kernel provides a set of tools that enable those, that would normally not have enough experience to recognize when the project is going off-track, to be able to.

I posted a few sets of links a few months ago. Here is another list. There has been a ton of new info to keep up with. Topics - .NET 3.0, 3.5, Acropolis, TFS, AJAX, Visual Studio 2008, CAB, WPF, Silverlight, SQL Server 2008, Architecture, WCF, LINQ, MVP, Repository Factory, etc...

I have to say I have never seen such a nonproductive movement before. At this point I don't think I would even trust their material. How can a company that can't implement a delivery process successfully, be trusted to deliver a process framework made to enable delivery?

A few years ago Microsoft decided to cut off its nose to spite its face. The war on UML started with the DSL movement. Although Microsoft still claimed to see UML as an essential tool, they stopped trying to compete with the rest of the market and tried to lead us down a new path that did not include UML.

The EssUP (Essential Unified Process) is over a year (almost 2 now) past dates promised for the Process Template for Team Foundation Server. We have been reading the articles that have been coming out and enjoying all the publicity around the non-existent process, but we are done waiting on it.

Two processes to keep an eye on in the upcoming months are the EssUP (Essential Unified Process) and PLE (Product Line Engineering).....

What makes people think a Software Development Process can be implemented in an organization at no upfront cost (including time and money)? Of course the number one culprit is lack of experience. The inexperienced have no understanding of what is involved in process engineering, and they usually have the belief that process is a luxurious overhead that is only to be thought about when there is complete downtime or during hours above billable hours.