AGILE: Agile is iterative & incremental approach for planning and guiding project process where more focus is on functionality rather than comprehensive documentation.
- Individuals and interactions over processes and tools.
- Working software over comprehensive documentation.
- Customer collaboration over contract negotiation.
- Responding to change over following a plan.
TERMS IN AGILE:
1) User Story - Requirement
2) Epic - Collection of user stories/ Requirements
3) Product Backlog - SRS/BRD/ All requirements
4) Sprint - Time period for complete releasing the functionality
5) Sprint Planning Meeting - First meeting for considering the user stories for every sprint.
6) Sprint Backlog: Committed user stories
7) Scrum Meeting: Daily stand up calls for 15 minutes
8) Sprint retrospective meeting
9) Story point: Estimation of user story using Fibonacci series(11235...)
Eg: It can be 1 hr/ 1 day
10) Sprint Review: Review of functionality delivered
11) Burndown chart : To track progress
12) Burnup chart: To track release progress and to estimate when MVP (Minimum Viable product) can be provided
13) Scrum Board
14) Ceremonies: Meetings
Eg: Sprint Planning Meeting/Scrum Meeting/Sprint retrospective meeting
-------------------------------------------------------------------------------------------------
Scrum is an agile development methodology/framework used in the development of Software based on an iterative and incremental processes. Scrum is adaptable, fast, flexible and effective agile framework that is designed to deliver value to the customer throughout the development of the project.
It assures that Agile principles are followed.
Extreme Programming (XP) is an agile software development framework that aims to produce higher quality software, and higher quality of life for the development.
A kanban board is an agile project management tool designed to help visualize work, limit work-in-progress, and maximize efficiency.
- Not much structured like Scrum
- Focus on Work In progress
------------------------------------------------------------------------------------------------------------------
SCRUM TEAM
The key responsibilities of a Product Owner include:
- Scrum backlog management
- Release management
- Stakeholder management
The role of Scrum Master:
- Facilitating the daily Scrum and Sprint initiatives.
- Communicating between team members about evolving requirements and planning.
- Coaching team members on delivering results.
- Handling administrative tasks such as conducting meetings, facilitating collaboration, and eliminating hurdles affecting project progress.
- Shielding team members from external interferences and distractions.
DEVELOPMENT TEAM MEMBERS:
- Product designer
- Writer
- Programmer
- Tester
- UX specialist
STAKE HOLDERS:
- The end user of the product
- Business executives
- Production support staff
- Investors
- External auditors
- Scrum team members from associated projects and teams
ADDITIONAL ROLES:
- Technical and domain experts with the knowledge of technology as well as a wide variety of stakeholder requirements or expectations.
- An independent testing and audit team may join the Scrum team members and work throughout the product development lifecycle.
- An Integrator may be required among large teams that work on independent but closely coordinated subsystems for a project. The responsibility for the Integrator would include integration of the subsystems as well as testing that may be performed by external testing teams.
- An Architect Owner may be required for architectural envisioning, planning and decision making.
-------------------------------------------------------------------------------------------------
VELOCITY & CAPACITY
Team Capacity: is a product of the total number of Scrum team members multiplied by the number of team productive days.
Eg:
Sprint Velocity = 32 & 6 Team members working 8 hrs/day
FOCUS FACTOR: 32 /(6*8) = 0.67
Team effective capacity would be 0.67 * (6*8*10) = 321.6 hours
FOCUS FACTOR *(NO. OF RESOURCES*HOURS*DAYS)
FOCUS FACTOR: 32 /(6*8) = 0.67
Team effective capacity would be 0.67 * (6*8*10) = 321.6 hours
FOCUS FACTOR *(NO. OF RESOURCES*HOURS*DAYS)
-------------------------------------------------------------------------------------------------
1) Poor resource planning
2) Limited documentation
3) Fragmented output
4) No finite end
5) Difficult measurement
-------------------------------------------------------------------------------------------------
RISK BASED TESTING: This testing is done in case there are chances of negative impact on production envt., which may happen due to,
1) Time constraint
2) Budget constraint
3) Resource constraint
To overcome this, approach which can be used is: Priotizing Technique, where important/critical features & TC's are prioritized and has to be made sure whether it is completed or not.
-------------------------------------------------------------------------------------------------
REGRESSION SCOPE:
It depends on,
a) Project nature: Landing page/Professional page
b) Project scope:
Small (Manual)/ Medium(Manual+automation) / Large (Manual+automation)
c) Stability of the project
Then final approach can be decided as,
1) Partial Regression
2) Full Regression
-------------------------------------------------------------------------------------------------
PROJECT REPORTING:
AGILE:
1) Burndown Chart : User Stories(Target User Stories) Vs Time (Started Time to Target time)
2) Burnup chart:
3) Sprint Report
4) Velocity Report: Committed Vs Completed
5) Cumulative flow diagram: No. of issues Vs Time
6) EPIC report
7) Epic burndown
8) Release burndown
DEVOPS:
9) Deployment frequency - DevOps
ISSUE ANALYSIS:
10) CREATED VS RESOLVED ISSUES
11) Resolution time report
FORECAST & MANAGEMENT:
11) Time tracking report
12) User Workload report
-------------------------------------------------------------------------------------------------
READY & DONE:
READY:
1) User story is understood by the team
2) Story is written in simple format (As a User.....I want to.....So that...)
2) User story has clear business value
3) User story is estimated
4) User story dependencies are identified
5) User stories are small
6) User story Acceptance criteria is defined
DONE:
1) Code is completed
2) Code is merged to main branch
3) Code review for code merge completed
4) Unit tests for story completed
5) User story is tested against the Acceptance Criteria
6) User story is demoed to the stake holders
7) Accepted by product owner
8) Documentation is updated
-------------------------------------------------------------------------------------------------
No comments:
Post a Comment