Archive for the ‘Process’ Category

Case Study: Functional and UI testing for moveme.com

Monday, June 1st, 2009

Continuing the topic of software testing, in this post we would like to present you a case study describing a project in which Softheme provided functional and UI testing services to moveme.com, a UK-based web portal.

A new web startup from London, moveme.com, which provides an online moving organizer for home-owners in the UK, turned to Softheme with the need to test their online tool. Since it is the company’s primary business application, they needed the testing to be performed very carefully and within established timeline which was accomplished by Softheme successfully.

moveme.com

(more…)

Defining Stakeholders for a Project

Friday, April 24th, 2009

Whether you are in outsourcing or any other kind of business, when doing a project, it is very important to understand who the main stakeholders for the project are. First of all, we need to clarify that the stakeholders are the people who are going to benefit from or lose something in the project. The project team, among others, should also be included in the list of stakeholders by this definition. However, if we take all of the extensive effects of doing nearly any project into account, we will understand that there actually may be a lot of stakeholders. Our main concern is connected with the “key” stakeholders and their identification. The most prevailing technique that can be used is to get seven to ten members of the project team together and then using one of the group dynamics techniques define the names of all the stakeholders for the project.

There is one more technique for stakeholders’ identification that recently gets more and more popularity. It is called the Crawford slip. Under this technique, each person in the group receives ten pieces of paper. Then the facilitator asks the question, “Who is the most important stakeholder in this project?” Each of the group participants must come up with the best response he or she can think of. After a one minute pause the facilitator asks the same question again and so on. Each time the question is asked, the participants must answer the question writing down more and more variants. Each participant cannot use the answer more than once.

(more…)

IPR Protection and Softheme NDA Agreement

Friday, April 17th, 2009

Ensuring and protecting client’s intellectual property (IP) rights is highly critical for any outsourcing business. Softheme understands how important for our customers is to secure their IP rights, and this is why we put an emphasis on signing any requested non-disclosure agreements (NDAs) by our clients and NDAs with our employees. Below you will find an excerpt from our standard NDA signed between Softheme and our employees:

This non-disclosure agreement, hereinafter – “Agreement”, is signed and shall enter into force between Party 1, in the person of the representative of Softheme LLC, the Owner of the Confidential Information, hereinafter – “Owner”, and Party 2, hereinafter named as “Consultant”, who renders (or plans to render) services of informational-consultative nature to Softheme LLC.

In connection with business relations between Parties, the Owner and the Consultant realize the necessity for the Owner to disclose to the Consultant some confidential information which belongs to the Owner; to be used for the sole purpose of planning and execution of business activities; and protect confidential information of this sort (hereinafter – “Commercial Secret”) from unauthorized use and disclosure.

(more…)

What is Project Charter Document

Monday, April 13th, 2009

Any of our projects start their life as soon as Softheme’s project manager creates a formal document called the project charter. The latter is a small document prepared to state the project name and the purpose of the project. It should also contain other important project-related information, namely, the business case for doing the project and a rough schedule and budget for the project. Besides, it should describe the needs and expectations of the stakeholders and list the assumptions and constraints that are recognized at the current point in the project.

(more…)

Project Scope Management: Softheme View

Wednesday, April 8th, 2009

In the next several posts we would like to discuss the basics of scope management since it is one of the most important parts of project management which we at Softheme pay special attention to. Due to proper application of scope management approaches to the projects of our clients, Softheme is so successful and productive in delivering projects of various complexity levels. So we believe it would be useful to share our experience regarding this matter.

Scope management is a starting point for any project. However, with web being a more dynamic sphere of development, we believe that scope management is better applicable to application development which usually requires a more thorough approach.

It is needless to say that the most common reason behind project failures is poor scope definition. This means that the expectations of the stakeholders, mainly of the client or sponsor, and the expectations of the project team are quite different. Being a most difficult problem, it is nevertheless critical to the success of the project. Projects fail due to many reasons, and understanding them does a good job in helping to avoid failures.

(more…)