"People who wants ur Product may tell something bad about your product or about yourself.
People who understand your product may tell some concerns about your product.
People who did something like your product may tell something different about your product idea.
People who neglect your product may not tell anything about your product.
Bottom line is : People are people. they will tell anything that they usually understand, dont understand or trying to understand. Listen and understand to what is productive.. Listen and let go to what is useless. Prepare a filtering system in your brain, train that everyday , and keep that updating continuously..
Scrum is an iterative and incremental agile software development method for managing software projects and product or application development. In the present time agile software development is a hot cake in the software development companies. A large number of companies in the software industry are implementing the agile software development without any previous experience and without a trainer as well. In many case they become successful but they always lose a handsome number efficiency. While working in the agile software development we closely observed the gap and the miscommunication between the development and quality assurance people. So here we are going to propose a managed approach which will going to improve the communication between the development and the quality people and in a fact in among the whole team members.
The agile methodology is a quite common software development method. Many famous and successful companies got a good rate of success by following the agile software development methodologies. Most folks know that agile was a direct response to the dominant project management paradigm, waterfall, and borrows many principles from lean manufacturing. Now the IT market is very much competitive so that we see most of IT companies compete heavily with the others in the market. This is quite interesting thing is that all the companies claim that they always deliver bug free software, high quality, reliability, scalability, etc. But the reality is that there are no products that are free of bug. So that what we can do is try to eliminate the bugs from the product by following worthwhile processes and methodologies. We ensure that the product is stable enough and sanity checked. This is the key factors that determine the success of a project. Just run to the project deadlines or completing those well ahead of schedule without any proper process in place will definitely result rework that will cost the customers a lot more and finally company will lose that customer. In the traditional way when we are implement the agile software development then, often we are falling down or lagging because lack of a solution. Personally when I was closely working in the Agile software development then I found many stressful gaps between software quality assurance, software quality control and Agile software development methodologies. From my experience I gather the knowledge and finally designed a more efficient process that will reduce the gap between these three terms in to the minimum. The main goal of any business is the customer. So the industry has to produce a product with very low percentage of bugs that can be discovered in unusual environments or impossible scenarios. This is the corner stone of quality, success and repeat business
In software outsourcing industry, to win a contract, outsourcing companies need to consider the price that they will introduce to customers. Therefore, estimation has played an important role in any type of software project and as well as for test projects. Particularly, the estimation of testing has been more critical and magnitude as companies need to present or bid their prices on the project to win the outsourcing contract. Wrong estimation can negatively affect the company sales in both ways. On the one side, the profit margin could be reduced or hurt when the bidding is less than that real effort. On the other side, the company could lose the project when the bidding is higher than that of competitors. Therefore, it is extremely necessary to apply economic and systematic estimation model or process to enhance the accuracy in estimation. The integration of highly skilled workforce and accurate test effort estimation software will provide significant benefits to companies. Up to now, there are various existing models of test effort estimation, yet use case point estimation is one of the most popular models in the agile software development industry. The present paper aims to investigate the use case point estimation model. Following the analysis, we have developed two important elements namely, efficiency and risk factor based on a new layer in the model developed by us. The benefit of the new model is to increase the performance and effectiveness of the use case point estimation model.
I am Masud Parvez. Working as IT Senior Project Manager for RMIT University. Previously I built and run a distributed Test Center. My success was to turn that in to one of the most successful business units of the company.