Posts

How can you become a great developer, tester, and product owner?

There was a time when product owner/business analyst would gather requirements from customers and write up a detailed business requirement document (BRD). Based on that requirement document, system architecture team would design the architecture of the system. After overall architecture of the system is designed, developers would write code based on the concrete requirements from BRD. When developers are done coding, then they would throw everything over the wall for QA to test. Even though some developers would write unit/integration tests before they hand off the system to QA folks for testing, majority of the developers would just think that QA folks are responsible for testing the quality of the product. After spending 2-3 months testing the system (based on the release date), QA folks would log all bugs and developers would fix those defects and hand over to QA again. Then, at the end product owner and QA would use variety of testing approaches (stress testing, acceptance testing...
Post a Comment
Read more

Top Down Or Bottom Up Development Order?

               It has been a while since I have posted anything in my blog, so here goes the topic of the day - top down or bottom up development order. Usually, most of the companies develop software following either one of these development orders. Since both of these development orders have pros and cons, one should pick the right development order that fits their situation. Companies/teams usually consider the answers from the following questions before deciding the development order they want to follow: ·         how clear and concrete are the requirements? ·         how far is the deadline of the project? ·         which software development methodology is your team following - agile or waterfall?                Let's begin b...
Post a Comment
Read more

Project Failure and Ways To Minimize the Risks

               Project management is certainly not an easy task as it requires great vision, excellent planning, and great collaboration among stakeholders, customers and project members. Therefore, it is not unusual to believe that almost  60% of the IT projects fail due to budget overruns, poor requirements gathering process, unrealistic project goals and poor project management skills. In order to be considered a project successful, it should deliver the quality product within the estimated budget and deadline. If a project deviates severely from the estimated budget and deadline, it will eventually lead to project failure. For this reason,  projects should be carried out under triple constraints - cost, time and scope. Triple constraints mainly emphasizes that projects must be delivered within cost and time, projects meeting its scope and customer quality requirements. Below are some of the guidelines that could help to minimize...
Post a Comment
Read more

Hello!

I have joined the bandwagon of my fellow bloggers by creating my own blog. In this blog, I will be posting my thoughts/ideas on wide variety of topics - technology, sports, project management, software development methodology, and software automation. Currently, I have been actively researching on Agile/Scrum methodology and my research focuses on how organizations should adopt Agile/Scrum methodology to deliver a quality product to its customers in a timely manner. I will share my findings with you all as I make progress.
Post a Comment
Read more