public marks

PUBLIC MARKS from tadanderson with tag rup

This year

Agile Product Owner Secrets Book Review

I highly recommend this book to all those moving towards an agile approach, but especially those moving towards an agile method that includes the product owner role.

2013

The Essence of Software Engineering: Applying the SEMAT Kernel Book Review

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.

2012

Disciplined Agile Delivery: A Practitioner's Guide to Agile Software Delivery in the Enterprise Book Review

All in all I found the book to be an excellent resource for the agilist looking to move beyond small develop teams. It is an absolute must read for enterprise architects and other senior management working in the IT shop.

Software Engineering Best Practices: Lessons from Successful Projects in the Top Companies Book Review

This is one of those books that should be read by every person with a relationship to IT. Testers, CIOs, CFOs, developers, architects, project managers, and agilists will benefit from this book. I highly recommend reading it. You will come out the back end of it with a complete new perspective on Software Engineering.

Why is Scrum so widely adopted and so very dangerously deceptive

Just because it looks like a duck and quacks like a duck, doesn’t mean it’s a duck

.NET Architecture and Development Book Recommendations for 2012

Another year has gone by. Happy New Year everyone. It is time to update my book recommendation blog. There have been a ton of books come out this year both good and bad.

2011

Software Development Processes Out of Balance

I find a lot of software development environments out of balance. It only takes one area of the environment to be out of its element to throw off the entire software development environment.

2010

Documenting Software Architectures: Views and Beyond (2nd Edition) Book Review

This book is the bible of documenting software architectures. It is a mandatory read for all software architects.

2009

The Process of Software Architecting Book Review

If you are involved in software development in anyway, you should read this book. It is the story of how it is supposed to be.

Architecting Software Intensive Systems: A Practitioners Guide Book Review

This book does an excellent job of introducing the reader to the soft skills needed to succeed as a software architect.....

2008

Visual Development Case UML Profile for SPARX Enterprise Architect (EA)

This Visual Development Case UML Profile for SPARX Enterprise Architect is intended to make creating a development case easier and more of a visual process.

2007

Implementing the IBM Rational Unified Process and Solutions Book Review

This book is a must have for anyone implementing the RUP. It hits on a lot of key pieces of the puzzle that go far beyond the configuration of process material and process instancing.

Agile Development != Low Ceremony && The Movement Needs to Die

Low ceremony does not have anything to do with being agile. Agile is an enabled state that is only accomplished through experience. It can be learned, but absolutely not by doing less.

Cool Links III- .NET 3.0, 3.5, Acropolis, TFS, AJAX, Visual Studio 2008, CAB, WPF, Silverlight, WCF, SQL Server 2008

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...

if(Money == RUP || $$$ == IBM || RMC == Cash){Your Golden}else{Go OpenUP};

Wow... IBM's pricing for using the Rational Unified Process and the Rational Method Composer stinks. If you can see it, you got to pay for it.

When will Microsoft Sew their Nose Back On???

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.

Thinking Software Development Process Implementation is Free means the Blind are Leading the Blind, but there are Ruby Slippers that may Help.

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.