5/3/2019 Project managers.

docx

Project managers are the point person in charge

of a specific project or projects within an
organization
Planning Project Resources: The project manager’s first role is
making a feasible plan that achieves the goals and objectives of the
project and aligns with the organization’s overall business strategy.
Project manager is responsible for the direction, coordination,
implementation, executive, control and completion of project
· Time Management: Time is always ticking towards the
project deadline. While communications is key to addresses
changes and make sure everyone is doing what they need to
do when they need to do it, the project manager must also
define, schedule and accurately estimate the task duration
to develop and maintain a realistic schedule.
Reporting and Documentation: Reporting is one of ways you
communicate with your team and stakeholders. While teams need
more detailed information and stakeholders are looking for broader
data to check the project’s progress, both are essential tasks for the
project manager

· Plan and implement projects

· Help define project scope, goals and deliverables
· Define tasks and required resources
· Collect and manage project team
· Manage budget
· Allocate project resources
· Create schedule and project timeline
· Track deliverables
· Support and direct team
· Lead quality assurance
· Monitor and report on project progress
· Present to stakeholders reports on progress as well as
problems and solutions
· Designing and following appropriate project management
standards.
· Managing the production and progress of project
deliverables. This can be done with the help of Sinnaps project
management software online which visually portrays a project’s
progress to all involved.
· Planning and monitoring the project. Planning can be done
with the involvement of team members and sponsors, who will be
happy to give input and e motivated by the inclusion.
· Maintaining the project on track and keeping up to date with
required reports. This is a very important responsibility of a project
manager.
· Managing project risks. This can be done through the
development of contingency plans which set out how a risk will be
dealt with when it turns into a likely threat. Risks are important to

https://webapp1.syntelinc.com/OWA/WebReadyView.aspx?t=att&id=RgAAAAAbfMIGAI8fSoQ99h5ycixBBwCUaKknkLF7Sqr3ac3w3%2balAAAAF… 1/8
5/3/2019 Project managers.docx

monitor and manage because if they are left unattended, they can
cause real harm to a project.
· Monitor overall progress and resource use. It is important for
project managers to take corrective measures where needed.
Sinnaps online scheduling app allows managers to spot
bottlenecks in the project before they cause damage and to correct
anything that needs correcting.
· Keeping in consideration certain interdependencies with other
on-going projects and their potential impacts. This responsibility of
a project manager can essentially make or break a project.
· Making sure that appropriate technical and quality standards
are applied.
· Finding and obtaining the appropriate support and advice
required for the running of the project.
· Managing stakeholder expectations and
feedback. Stakeholder have a significant stake in projects and
make clear what they expect and they expect to be kept up to date.
Project stakeholders roles and responsibilities also play a part in
project management.
·
A statement of work (SoW) is a document routinely employed in the field of project
management. It defines project-specific activities, deliverables and timelines for a vendor
providing services to the client. The SOW typically also includes detailed requirements
and pricing, with standard regulatory and governance terms and conditions

The Project Management Life Cycle is a series of various activities/tasks

that are crucial for accomplishing project objectives or targets. This helps
in structuring the efforts and simplifying them into a series of logical and
manageable steps. The Project Management Life Cycle consists of four
simple phases which are listed below:
1. Initiation
It’s the first and most vital step in the life-cycle of your project
where the initial scope of the project gets defined and resources
are committed. This process group ensures the success of your
project.
2. Planning
In this process group, an appropriate level of detail is jotted for the
project to plan time, cost and resources. It estimates the work
needed and manage risk effectively.
3. Executing
This process group consists of the processes which are used to
complete the work defined in the project management plan. It’s
about achieving the project’s objectives. It also involves tracking,
reviewing and regulating the performance of the project. Also, you
need to identify potential problems quickly and take corrective
actions.
4. Risks are the potential problems that can have either a positive
or negative impact on the project resulting in a deviation of the final
result from the original plan.
is the process of identifying, analyzing and then responding to
any risk that arises over the life cycle of a project to help
the project remain on track and meet its goal.

5. Actions are the task that you perform throughout the project.
6. Issues are the hurdles that you might face in the course of the
project which must be successfully resolved or it might derail the
project or cause the project to fail.
7. Decisions are your choice of actions/tasks in the project.

https://webapp1.syntelinc.com/OWA/WebReadyView.aspx?t=att&id=RgAAAAAbfMIGAI8fSoQ99h5ycixBBwCUaKknkLF7Sqr3ac3w3%2balAAAAF… 2/8
5/3/2019 Project managers.docx

https://www.edureka.co/blog/interview-questions/top-30-project-
management-interview-questions-2016/

Q#1. What is Agile Testing?

Ans. Agile Testing is a practice that a QA follows in a dynamic environment
where testing requirements keep changing according to the customer needs. It is
done parallel to the development activity where the testing team receives
frequent small codes from the development team for testing.
Q#2. What is the difference between burn-up and burn-down chart?
Ans. Burn-up and burn-down charts are used to keep track of the progress of
the project.
Burn-up charts represent how much work has been completed in any project
whereas Burn-down chart represents the remaining work in a project.

Q#3. Define the roles in Scrum?

Ans. There are mainly three roles that a Scrum team have:
1. Project Owner – who has the responsibility of managing the product
backlog. Works with end users and customers and provide proper
requirement to the team to build the proper product.
2. Scrum Master – who works with scrum team to make sure each sprint
gets complete on time. Scrum master ensure proper work flow to the
team.
3. Scrum Team – Each member in the team should be self-organized,
dedicated and responsible for high quality of the work.
Q#4. What is Product backlog & Sprint Backlog?
Ans. Product backlog is maintained by the project owner which contains every
feature and requirement of the product.
Sprint backlog can be treated as subset of product backlog which contains
features and requirements related to that particular sprint only.

Q#5. Explain Velocity in Agile?

Ans. Velocity is a metric that is calculated by addition of all efforts estimates
associated with user stories completed in a iteration. It predicts how much work
Agile can complete in a sprint and how much time will require to complete a
project.
Q#6. Explain the difference between traditional Waterfall model and Agile
testing?
Ans. Agile testing is done parallel to the development activity whereas in
traditional waterfall model testing is done at the end of the development.
As done in parallel, agile testing is done on small features whereas in waterfall
model testing is done on whole application.

Q#7. Explain Pair Programming and its benefits?

Ans. Pair programming is a technique in which two programmer works as team
in which one programmer writes code and other one reviews that code. They
both can switch their roles.
Benefits:

1. Improved code quality: As second partner reviews the code

simultaneously, it reduces the chances of mistake.
2. Knowledge transfer is easy: One experience partner can teach other
partner about the techniques and codes.
Q#8. What is re-factoring?
Ans. Modification of the code without changing its functionality to improve the
performance is called re-factoring.

https://webapp1.syntelinc.com/OWA/WebReadyView.aspx?t=att&id=RgAAAAAbfMIGAI8fSoQ99h5ycixBBwCUaKknkLF7Sqr3ac3w3%2balAAAAF… 3/8
5/3/2019 Project managers.docx

Q#9. Explain the Iterative and Incremental Development in Agile?

Ans. Iterative Development: Software is developed and delivered to customer
and based on the feedback again developed in cycles or release and sprints.
Say in Release 1 software is developed in 5 sprints and delivered to customer.
Now customer wants some changes, then development team plan for
2nd release which can be completed in some sprints and so on.
Incremental Development:Software is development in parts or increments. In
each increment a portion of the complete requirement is delivered.
Q#10. How do you deal when requirements change frequently?
Ans. This question is to test the analytical capability of the candidate. Answer
can be-
Work with PO to understand the exact requirement to update test cases. Also
understand the risk in changing the requirement. Apart from this one should be
able to write generic test plan and test cases. Don’t go for the automation until
requirements are finalized.

Q#11. What is a test stub?

Ans. A small code which mimics a specific component in the system and can
replace it. Its output is same as the component it replaces.
Q#12. What qualities should a good Agile tester have?
Ans.
1. Agile tester should be able to understand the requirements quickly.
2. Agile tester should know Agile concepts and principals.
3. As requirements keep changing, he should understand the risk involve
in it.
4. Agile tester should be able to prioritize the work based on the
requirements.
5. Communication is must for a Agile tester as it requires a lot of
communication with developers and business associates.
Q#13. What is difference between Epic, User stories & Tasks?
Ans. User Stories:User Stories defines the actual business requirement.
Generally created by Business owner.
Task: To accomplish the business requirements development team create tasks.
Epic: A group of related user stories is called an Epic.
Q#14. What is a Task board in Agile?

Ans. Task board is dash board which shows progress of the project. It contains:
1. User Story: which has the actual business requirement.
2. To Do: Tasks that can be worked on.
3. In Progress: Tasks in progress.
4. To Verify: Tasks pending for verification or testing
5. Done: Completed tasks.
Q#15. What is Test Driven Development (TDD)?
Ans. It is Test-first development technique in which we add a test first before we
write a complete production code. Next we run the test and based on the result
refactor the code to fulfill the test requirement.
Q#16. How QA can add a value to an agile team?
Ans. QA can provide a value addition by thinking differently about the various
scenarios to test a story. They can provide quick feedback to the developers
whether new functionality is working fine or not.
Q#17. What is Scrum ban?
Ans. It is a software development model which is combination of scrum and
kanban. Scrumban is considered for maintenance projects in which there are
frequent changes or unexpected user stories. It can reduce the minimum
completion time for user stories.
Q#18. What is Application Binary Interface?
Ans. Application Binary Interface or ABI defines an interface for complied
application programs or we can say it describes the low level interface between
an application and the operating system.
Q#19. What is Zero sprint in Agile?
Ans. It can be defined as pre step to the first sprint. Activities like setting
development environment, preparing backlog etc needs to be done before
starting of the first sprint and can be treated as Sprint zero.
https://webapp1.syntelinc.com/OWA/WebReadyView.aspx?t=att&id=RgAAAAAbfMIGAI8fSoQ99h5ycixBBwCUaKknkLF7Sqr3ac3w3%2balAAAAF… 4/8
5/3/2019 Project managers.docx

Q#20. What is Spike?

Ans. There may be some technical issues or design problem in the project which
needs to be resolved first. To provide the solution of these problem “Spikes” are
created. Spikes are of two types- Functional and Technical.
Q#21. Name some Agile quality strategies.
Ans. Some Agile quality strategies are-
1. Re-factoring
2. Small feedback cycles
3. Dynamic code analysis
4. Iteration
Q#22. What is importance of daily stand up meeting?
Ans. Daily stand up meeting is essential for any team in which-
1. Team discuss about how much work has been completed.
2. What are the plans to resolve technical issues.
3. What steps need to done to complete the projects etc.
Q#23. What is tracer bullet?
Ans. It can be defined as spike with the current architecture or the current set of
best practices.
The purpose of a tracer bullet is to examine how an end-to-end process will work
and examine feasibility.

Q#24. How the velocity of sprint is measured?

Ans. If capacity is measured as a percentage of a 40 hours weeks then
completed story points * team capacity
If capacity is measured in man hours then Completed story points / team
capacity

Q#25. What is Agile manifesto?

Ans. Agile manifesto defines an iterative and people-centric approach to
software development. It has basically 4 key values and 12 principals.
Q13) What does story point mean in the scrum?
The unit that is used to estimate the total effort which is needed to finish or do a
particular work or implementing a backlog is referred to a story point in the scrum.
Q14) What do you mean by the X and Y axis of the burndown chart?
In the burndown chart, the X-axis represents the working days and the Y axis stands for
showing the remaining efforts.

Q15) Describe the main roles in the scrum.

· Scrum team - It is consist of an individual person who is in charge of

working collectively to complete a certain task.
· Scrum Master - this person is responsible for the paper execution of end
result of the scrum team.

https://webapp1.syntelinc.com/OWA/WebReadyView.aspx?t=att&id=RgAAAAAbfMIGAI8fSoQ99h5ycixBBwCUaKknkLF7Sqr3ac3w3%2balAAAAF… 5/8
5/3/2019 Project managers.docx

· Product owner - he or she has the responsibility of delivering a whole

concept of what to build and then convey the idea to the team.
[Related Article:: Learn Agile Project Management with Scrum]
Q16) What is Zero sprint in Agile?
It can be defined as pre-step to the first sprint. Things like setting up the development
environment, preparing backlog etc needs to be done before starting of the first sprint
and can be treated as Sprint zero.
Q17) What do you mean by product burndown chart?
Product burndown chart is the graphical representation of a description that shows
implementation and the non-implemented product backlog.
Q18) What do you mean by sprint burndown chart?
It is a graph that is used to describe the number of non-implemented or implemented
sprint in scrum cycle.
Q19) What do you mean by release burndown chart?
Release burndown chart represents the pending releases that were planned earlier.
Q20) What do you mean by defect burndown chart?
It is the representation of a number of defects that are identified and then removed.
Q21) What do you mean by sprint planning meeting?
The meeting that is joined by all the entities like product owner, scrum master and the
whole scrum team is known as sprint planning meeting. It is done to discuss the
important feature of the team and also the items of the product backlog.
Q22) What do you mean by sprint retrospective meeting?
Sprint retrospective meeting is the last part of the sprint. It is probably done after the
review meeting of a sprint. The whole teams along with scrum master participate in this
discussion and it lasts for 2 to 3 hours.
Q23) What does build breaker mean?
There are certain times when the developer accidentally commits a bug in the software.
This bug might stop the process of compilation or generated warring. It is the cause of
failure during normal execution of testing. In such cases, it is said that the build is
broken. The main priority of the tester now is to rectify the bug.
Q24) What do you know about Kanban?
A tool which is used in helping the team to overlook the work which includes its progress
is known as Kanban. Along with progress, the status of the current development story is
also described by Kanban and it is done by Kanban board.
Q25) What are the places where Scrum and Kanban are used?
When there is a need for shifting towards appropriate and prominent process then you
use Scrum. When you need to improve the process that is running provided that there
are not many changes then Kanban is used.
Q26) Why do user stories are not estimated in man hours?
It is not preferred to do an estimation of user stories in terms of man hurt because it will
mean lack of concentration on the product quality which is to be delivered to the
customer. In case of man-hour, more concentration is given on budget and cost of

https://webapp1.syntelinc.com/OWA/WebReadyView.aspx?t=att&id=RgAAAAAbfMIGAI8fSoQ99h5ycixBBwCUaKknkLF7Sqr3ac3w3%2balAAAAF… 6/8
5/3/2019 Project managers.docx

management. This is the reason why story point is used because it gives concept
regarding both efforts required and also the complexity of the work.
Q27) What are the three other agile frameworks?
The three agile frameworks are:-

· Test-driven development
· Feature driven development
· Kanban
Q28) What is your view on scrum master removing impediments for the scrum
team?
The scrum master can remove impediments on behalf of the scrum team but he should
not do that. The scrum master should not pamper nor overrule the scrum team. Also, the
scrum team should be able to make their own decisions.
Q29) What is the process in which a master recommends following up on action
items?
The best way to do this is by establishing a follow up of the works that are to be done by
the members of the team. The information is to be collected by the scrum master.
Q30) What are the most important agile Matrices?
The following are the important agile Matrices.

· Velocity - To have a clear about your progress, capacity and many more
keeping track of the velocity is important. It can be measured by adding all
the estimates of the stories that are approved.
· Work category allocation - the work category allocation will provide a clear
idea about where you are investing your time and also about the priority of
the work.
· Defect removal awareness - the active members can produce quality
products.
· The cumulative flow diagram - the uniform flow of work can be checked
thought this diagram of cumulative flow. Here the x-axis represents time and
the y-axis stands for the number of effort.
· The sprint burndown matric - it helps in keeping track of the completion of
the work with the sprint.
· Business value delivered - this is an entity that is concerned with the work
efficiency of the team. It is used to measure and 100 points are associated
with every project.
· Time coverage - it is defined as the amount of time that is given to a code
while it is being tested. This is measured with the help of ratio of the number
of lines of code that is called by the test suite by the number of relative lines
of codes.
· Defect resolution time - this is a term which is concerned with the process in
which team members detect bugs and also fixes them. There are a number
of processes involved in fixing a bug.
1. clearing the picture of the bug
2. Schedule a fix

https://webapp1.syntelinc.com/OWA/WebReadyView.aspx?t=att&id=RgAAAAAbfMIGAI8fSoQ99h5ycixBBwCUaKknkLF7Sqr3ac3w3%2balAAAAF… 7/8
5/3/2019 Project managers.docx

3. Fixation of a defect is done.

4. Report of resolution is handed.

https://webapp1.syntelinc.com/OWA/WebReadyView.aspx?t=att&id=RgAAAAAbfMIGAI8fSoQ99h5ycixBBwCUaKknkLF7Sqr3ac3w3%2balAAAAF… 8/8