This document provides tips for improving project analysis skills. It recommends reading requirements line-by-line to understand what is being asked. Then develop a list of functional and technical questions, diagram how different services will be implemented and identify dependencies. Estimation involves determining time estimates, assigning story points based on effort, complexity and risk, and calculating velocity. The document concludes by thanking the reader.

1. How to improve your project
analysis skills
(W1D5: 9Dec, 9PM)

2. Whenever the
requirements are
discussed,
later perform this
exercise on those
requirements
The more you spend time in analyzing, the
more you would become better
1. Read requirement end-to-end -
line/by/line.
2. Do you understand what is being asked?
3. Come up with list of functional questions.
4. Technical highlevel - how will you
implement this.
5. How many services should be involved
6. Service diagram
7. (service1) ===> (Server2) => (Serv3)
8. DB(SQL/NoSQL), Caching, Async,
9. Cron
10. List down technical questions
11. Identify dependencies
12. Impact analysis
13. Estimation - Time estimate
14. Estimation - Story Point

3. Estimation - To happen during Internal Grooming
Estimation - (X hrs) - (Original Estimate)
● UI development (8hrs)
● UI Unitesting (4hrs)
● Server Development (16h)
● Server Unitesting (8h)
● UI-Server integration (2-3hr)
● QA Testcases (4h)
● QA Execution (8h)
StoryPoints Estimate (1, 2, 3, 5, 8, 13, ...):
(StoryPoint)
● Velocity (Per sprint, how much story point of
work)
● Comparison with existing tickets
● Efforts + Complexity + Risk
● 3 + (0.5/1/1.5) + (0.5/1/1.5)
● ManDays / 2 + Complexity + Risk
● 1.5 + 1 + 1
● 3.5 (SP: 3)

4. Thank You
Tausief S
7842717511
https://www.linkedin.com/in/tausiefs/