Suppose you are working on any project and you have u do 50 hours work in 20 hours and you have to make delevery on tym then what will be your Approach??

Replies to This Discussion

Permalink Reply by Mohit S on March 28, 2011 at 5:15pm

In this critical situation first analyze the business critical s and focus area of the product. And break the product in small chunks and prioritize them as per client prospective. Then start working on as per priority. It is also know as risk based.

After that you will able to complete the delivery on time.

 

Basically this type of condition is not possible because everything would be predefined during the whole cycle.

And in typical Agile terminology , first all cross functional team member , product owner and scrum master set the delivery time as a "sprint" for given product on given release time with the approval of clients.

• ▶ Reply

Permalink Reply by Amira Soliman Ahmed on March 28, 2011 at 5:18pm

Risk Basked one

• ▶ Reply

Permalink Reply by Arunkumar Khannur on March 28, 2011 at 5:20pm

You need to work on Project Strategy which involves priotity-based scoping and incremental delivery.

• ▶ Reply

Permalink Reply by snehasish on March 28, 2011 at 5:24pm

Priority based testing

• ▶ Reply

Permalink Reply by John Najarian on March 29, 2011 at 3:31am

As per stated by other members, you have to prioritize and determine risk.  You should consider talking to the user and development teams when making this deliverable.  You should consider what the user's priorities (expectations) are along with the stability of the requirements and code.  If you do not get reasonable feedback, you will have to prioritize and provide a risk statement.  It sounds like you are in a somewhat challenging position as what you are describing indicates that the customer is setting limited timelines and from my perspective this indicates that this was not well planned out and the customer did not work with you to understand your estimates.  You should be able to follow the SDLC and test properly.  That said, test approach is to indicate the tests that you will focus on requirements that have the greatest value to the customer (detailed tests with good coverage) and risk is that the other requirements (lower importance such as usability) will have limited coverage.

• ▶ Reply