Group 1: Early Development

TEAM MEMBERS

AJAY BALAMURUGADAS
MAURA GARVEY
VIDYA MURTHY
VOJTECH ZBYTOVSKY
 Project Statement

You have joined the development team very early in the

project.
The project manager has asked you to test along with the
programmers as they write code.
She wants to mitigate the implementation-related risks in
the project and
hopes you can help her understand them and help her staff
control them.
 1. Very early in the project

 How long is the expected project duration?

 When was the project started?
 How much progress has been made?
 Are there any specifications or any documents relating to this
project? If yes,
 Are the specifications complete or being modified at regular
intervals?
 Is the development team staffed right or they are still on the look
out for members for the development team
 Are we so early into the project that no progress has been made?
 2. Test along with development

 Do we (QA team) test with the Dev team or as a separate

independent group?
 Do we do unit tests or are we limited to System level tests
 Do we track the defects in a separate bug tracker?
 Do we do regression tests?
 Are we planning for automation?
 What is the release cycle to QA if it is an independent
activity.
 3. Mitigate the implementation-related risks

 What risks does the PM perceive?

 What risks dos the development team perceive?
 What is your preparation level to mitigate the risks?
 Do you understand the importance of mitigation of the
risks?
 Are you ready to do the needed changes?
 How focused is the management in enforcing timelines and
usage?
 4. Help PM and Dev team understand and control the risks

 Project Risks:
 Are you dealing with insufficient resources?
 How easy it is to incorporate new changes in the project?
 How strong is the communication channel within the team and the
organization?
 Control Risks:
 Are we working with unfamiliar technology?
 Do we understand our objectives clearly? Are they well-defined?
 Do we understand the big picture of the project?
 How do we deal with incompatible interfaces?

 Benefit Risks:
 How accountable are we for the success/failure of the project?
 What are our measurement standards?
 Do we care enough for the business cases?
 General Questions

 Is there a project plan approved by the client?

 What milestones influencing testing are there in the time plan?
 Are there any user/client requirements?
 Is there any specifications?
 How detailed is it, how internally coherent is it, does it well reflect the
requirements?
 Any other input documentation for testing?
 Which of the input documentation is binding for testers as oracles? (Which are
only supportive?)
 Are there any other oracles to be used, e.g. legacy product, similar products on
the market, internal coherence within the product, general principles of any
kind? How binding are they for testers?
 What level of quality is expected? Is it a mission critical software? Is it life
critical?
 Is there any previous project which is similar to the current project? Can we take
help of those who worked on that project?