Thursday, January 25, 2007

Scrum vs. RUP - The winner is...

Let's first outline both the scrum and rational unified process.

According to WikiPedia:
Scrum is an iterative, incremental framework for project management often seen in agile software development, a type of software engineering. 
Although the Scrum approach was originally suggested for managing product development projects, its use has focused on the management of software development projects, and it can be used to run software maintenance teams or as a general project/program management approach.
Here is a video that talks about scrum and what the scrum master does:

Now for RUP and what WikiPedia says:

The Rational Unified Process (RUP) is an iterative software development process framework created by the Rational Software Corporation, a division of IBM since 2003. RUP is not a single concrete prescriptive process, but rather an adaptable process framework, intended to be tailored by the development organizations and software project teams that will select the elements of the process that are appropriate for their needs.

Here is a video that talks about RUP here:




So, which process is better? SCRUM OR RUP? 

Well, there isn't a magic bullet or a one size fits all development process for everyone, so we aren't going to declare a winner. However, here, at Axosoft, we are biased towards Scrum because OnTime was made to be great agile scrum software, we still believe in other development processes.  We would be interested in learning more about what your thoughts are on both development processes. Contact us or post in the comments.

This blog is finally active again, so please subscribe to our feed to get the latest info about scrum and scrum development!

Monday, October 16, 2006

5 Reasons for Project Management Failure

Change is always difficult, especially in a large organization that already has things set in stone. Even when an organization is not happy with their progress, the fear of change and the potential side effects of that change make things slow and challenging. Being agile, and implementing the methodologies of scrum will be a challenge, but a challenge worth taking on.

This original post has been altered, but we are creating new posts and can be viewed on the home page.

Wednesday, September 06, 2006

Changing the Mindset of an Organization

When it comes to changing any organization's mindset of altering processes and how things are done, it is difficult because of the possible side effects that could occur when the changes take place. You also have to consider the perspective that changing things takes time, which ultimately costs money. You have to defend against all of these things and make the case that the risks and cost don't outweigh the proposed agile changes.

Tuesday, September 05, 2006

Scrum Core Values

In any scrum team, there are a set of core values that everyone should keep in the back of their mind.

Commitment, Focus, Openness, Respect, and Courage.

    Thursday, August 31, 2006

    Eureka: The Daily Scrum

    The daily scrum standing meetings usually consist of talking about what you worked on the day before, what you plan on doing today, and what is stopping you from accomplishing your daily goals? Teams that do not run daily scrum meetings are not taking advantage of the great opportunities of communication and team atmosphere that is created by them.

    View our new posts about scrum by going back to the home page.