There may be situations (like a startup, a small biz or even an average one) when some Project Management functionality is needed, for a better management of the tasks, in order to scale up the biz or to control it in a better manner.

    When the developing environment is Agile, the projects will be managed by an Agile Project Manager. Thus, the development will be iterative and compliant with all the Agile values, including those from Agile Manifesto.

    The main benefit of Agile Project Management is the responsiveness to changes during the project course. Following this way, the business values will be easier followed, so the customer satisfaction will increase.

    In one of my previous posts, I mentioned that the Business Analyst is in charge with "what to do", while the Project Manager is responsible with "how to do". This is a very simple approach and it is true from start-ups to big companies. This pair will "bridge" in a better way the biz needs with the IT needs, they will form a stronger Biz-IT Bridge.

    How to sort these differences? How to understand the basics of this issue, often discussed in some environments? Simply, the Business Analyst is in charge with "what to do" while the Project Manager is responsible for "how to do it".

    When trying to link two concepts which apparently have nothing in common, we can actually reach an incredible best result. I think this is the case for Six Sigma in Project Management, too.