Technical archives - Quality Assurance and Project Management
Home > IT Blogs > Quality Assurance and Project Management >

Quality Assurance and Project Management:

technical

Jul 28 2009   10:00AM GMT

Five Technical Details to understand before performing Load Testing on a software product



Posted by: Jaideep
technical, load testing, testing, software product, framework, Software application, .Net, J2EE, server, server application, presentation server, application server, database server, MS SQL Server, Oracle, Apache, Websphere, IIS, OS, operating system, hardware configuration, RAM, processor, harddisk, LAN, dial-up

1. Framework: What is the framework being used in the application? For example it may be .Net or J2EE or any other.

2. Servers: What all server services you are using to run/ use this application? What standard server applications are used for Presentation, Application and Database level? Some examples could be MS SQL Server, Oracle, Apache, Websphere, IIS etc.

3. Number of machines: Are these servers running on same machine or different machines. If different machines how many machines and what servers specfically on which machine.

4. Details of these machines: The details of the machines running all these server applications or server services. Details would include Operating System, Hardware configuation – like Hard disks, RAM, processors etc.

5. Access details: Last but not the least important point is how the users will be accessing the application – via LAN, through dial-up, through internet, through some specific port and third party tool etc.

AddThis Social Bookmark Button     0 Comments     RSS Feed     Email a friend

Feb 11 2009   11:04AM GMT

Project Management – Tasks vs. Milestones



Posted by: Jaideep
Project Management, project manager, Software Project, project task, project milestone, software team, programmer, developer, technical, coder, coding, programming, Development, Project Development, project progress, project completion, PM

A new project is always divided into small tasks and based on the resources available, the task(s) are allocated to individuals by the project manager (PM). A simple metrics is important to follow to monitor (and manger) the completion of tasks and thereby figuring out at any moment of time – the progress of the project. Completion of all tasks automatically declares the completion of the project.

Customer and management will never be interested to go into the detail of each task, PM (you) and your team may be and should be. But your one of the major task during a project is to keep customer and management updated on what is happening, regarding the progress of the project.

Your team of individual developers, programmers, coders or other technical related functions, although have accountability for the tasks assigned to them in individual for which they put in all their efforts to meet your/their completion plans as per the targets set.

So far so good, but as far as satisfaction, and feel of achievement is concerned, you need to group a set of tasks (the important ones that really give sense of achievement) into milestones. The customer and management will be interested in milestones achieved instead of tasks completed. Your team members will feel motivated, inspired and cheerful on achieving these milestones. And above all you will have time to appreciate and celebrate your team’s achievements that you can not do rightfully in case of tasks.

Milestones have more visibility as compared to tasks.

AddThis Social Bookmark Button     0 Comments     RSS Feed     Email a friend