Archive for the ‘Project Methodology’ Category

White Paper on Project Performance Management

Saturday, September 24th, 2011

During the last 10 years Project and Portfolio Management (PPM) technology has greatly matured offering the desperately needed platform to facilitate the challenge of managing project information, improving collaboration among stakeholders and delivering critical status reports for multi-project environments. Like so many enterprise systems, PPM solutions are excellent at easily capturing the information needed.

Where these offerings vary is the effectiveness in extracting and communicating relevant project information to improve the decision making capabilities of project management practitioners. A solid PPM strategy understands the power of analytics and how it can be leveraged to not only track project progress, but more importantly track project performance.

In this paper, I will be exploring the importance of solid analytics in a PPM strategy that can take your organization to the next level by developing a performance management strategy that will impact your project’s success.
Read more…

White Paper on the Theory of Constraints

Thursday, May 26th, 2011

This white paper is courtesy of Roopesh Kuma.  It is about gaining control of your project using the theory of constraints. The Theory of Constraints is a management philosophy that was introduced by Dr. Eliyahu M. Goldratt, in his 1984 book titled ‘The Goal’. It assists businesses in achieving their goals by providing a mechanism to gain better control of their initiatives. According to Goldratt, the strength of any chain, either a process or a system, is only as good as its weakest link [1]. TOC is a systemic way to identify constraints that hinder system’s success and to effect the changes to remove them.  Read more…

Portfolio Management Case Study

Thursday, February 17th, 2011

Recently we worked with a client introducing Portfolio Management. This white paper explains our approach and how we introduced it to the organisation. It also covers our approach to rating the projects against strategy. Click here to read more.

Software Testing Career

Thursday, January 27th, 2011

This is a contribution from one of our visitors.  Janet Fleming is a software testing professional and has some comments to make on a career in testing.

Are you going to benefit from entering a Computer Software Testing Profession?
This is a good question….firstly we should see if you have the type of personality to accomplish software testing. You ought to be organized, logical and thorough. Hypothetically a tester should test 100% of the software but in real life the tester only tests that the software does what it expected to do by the user.

Then you have to implement those tests – often repeatedly. Your aim is always to be sure that no software goes out to customer without all the bugs found. It’s rarely achievable, but this should be your main goal. I sometimes believe your 2nd goal must be to have every developer hate you because you keep finding bugs inside their code 🙂

The answer if software testing is an excellent career option is dependent upon who’s asking the question. I’ll answer it as if my audience is definitely an engineer. I will be both flip, and sincere. My working experience has shown to me that the theory of software development never happens in reality.

Theoretically, software testing is: – Validating and recording that software performs the functions it’s supposed to. – Confirming and showing that it doesn’t do anything whatsoever it is not designed to

This presupposes you have been told what it’s supposed, and not supposed to do. People you’re working for don’t always do this. They might suspect you will run away with their secrets.

Because software packages are a business solution (except when you are doing work for the military) business principles apply a lot more strongly than engineering guidelines. Software testing is expensive, and so the choices about goals and how much to do can be highly dependent on ROI considerations.
From the end-user perspective, the user’s acceptance isn’t necessarily directly related to the physical world. It is not related to how robustly designed, or how elegantly coded. In fact it is the user’s perception of whether your system works that finally rules within the minds of management, whose job is purely to ensure no one is complaining regarding the software.

Therefore, the truly practical explanation of software testing may be summarized as 3 goals:
1. Verify the consumers that use software believe it’s doing whatever they demand it to do
2. Verify the software doesn’t do anything immediately detectable that is not desirable for the user.
3. Verify that any undesirable behavior has a sufficient period that the software will appear to perform properly for you to make it to another round of VC financial commitment or sell the organization 🙂

So do you consider Software Testing could be the right career path?

About the writer: Janet Fleming is writing for the software testing course for beginners blog, her personal and non-commercial in nature hobby web site to give free tips for software testing novices/pros to enable them to find a new work.

White Paper on Discipline in Projects

Wednesday, December 15th, 2010

A constant complaint from those involved in projects is that there is too much bureaucracy. A process has been set up and it must be followed regardless of the size or complexity of the project. One size fits all. This white paper covers some of the things to consider when deciding how much rigor to apply to a project. Read More