Month: September 2012

More about Agile practices

Following is interesting article which explains the soft skills that the agile teams to have to drive the project to success. It is not all about technology. It is how you collaborate and what factors are required to establish effective and successful collaboration.
This article also discuss about following three factors where agile teams relies heavily on establishing the successful collaboration.

Read more from the following link: The softer side of Agile: Leading collaborative teams to success

Five common mistakes to watch out in database design

Following is a TechRwpublic article which highlight five common mistakes that we tend to do in some situations.

Five common mistakes in database design

I have seen in many cases that the teams unintentionally doing these mistakes, but the catch is here that we can’t always go by the rules. We have to consider the other factors such as time lines, business value, end user expectations, performance, cost, quality etc. What I believe is that we as part of the development team needs to have a balance in all aspects related to software development. That is if we would try to implement rules to avoid mistakes mentioned in the above article we may well have to sacrifice many other things. So the knowledge of the business domain, the technology used and the capability of the team will determine the successful end product.

But as a convention we must always take all the necessary measures to make no mistakes at design level so take as much time as possible to do it right at the first place.

Agile practices solve many issues…

Following is one good example how Agile practices have impacted the software development and how it is beneficial to the team and for the end users.

Sloppy code why its not always the developers fault is a tech replublic article that I came accross which explains the issues with delivery and how continous delivary with agile practices will improve the process.

The agile practices will also help the Managers to focus more on the business value of the end product and as a end result we have a happy customer. So agile has put the software development to new heights by making our lives easier.

Do Project Managers need to have Technical Knowledge?

Different people might have different opinion on this topic. According to my understanding there are definitely pros and cons of a PM having a technical background. As we all know traditional project management is all about managing resources, Gant Charts, Mile Stones, etc. I’m not going to write about that here. But in the recent past with the implementation of Agile Practices this traditional project management has been put to a new and challenging level.
With my experience in the past with agile projects, I have seen more advantages of PM having technical knowledge than disadvantages. Why I am saying this is that I have worked with several PMs who don’t know what exactly the team is doing and they didn’t have any idea whether the time lines given by the developers and QA team are realistic or not. They simply became a facilitator. Of course they should be facilitators, but it should be more than that just passing the ball here and there. They always needed the help of the developers to update the top management and I have seen that majority of the developers don’t like this at all.