Professional Documents
Culture Documents
Internal Guide, Dr. K V A BALAJI Professor and HOD Department of Mechanical Engineering External Guide, KRISHNARAJ C K Senior Design Engineer GE-HCIT By, ARAVINDA H S (4JC10MEM01)
DEFINITION
Agile software development is a group of Software development methodologies based on iterative and incremental development, where requirements and solutions evolve through collaboration between Self-organizing, Cross functional teams. It promotes adaptive planning, evolutionary development and delivery, a time-boxed iterative approach, and encourages rapid and flexible response to change.
Present Methodology
Classical methods of software development have many disadvantages:
Huge effort during the planning phase at the start of the project.
Agile methods: Scrum Extreme Programming Adaptive Software Development (ASD) Dynamic System Development Method (DSDM)
Proposed Methodology
Short release cycle (1 to 6 months) Issues are identified well in advance through the daily meetings and hence can be resolved in speedily Agile methods adapt to change, as at the end of each stage, the logical programme, designed to cope and adopt to new ideas from the outset, allows changes to be made easily. With Agile, changes can be made if necessary without getting the entire programme rewritten. Agile scrum helps the company in saving time and money
Scrum
Scrum Framework
Product Owner
Define the features of the product Decide on release date and content Be responsible for the profitability of the product (ROI) Prioritize features according to market value
Scrum Team
Team is cross-functional and consists of 5-9 people
Meetings
2. Sprint
3. Daily Scrum 4. Sprint Review Meeting
Sprint
product functionality
NO outside influence can interfere with the Scrum team during the Sprint Each Sprint begins with the Daily Scrum Meeting
Sprint Planning
Meeting
Daily Scrum
Held every day(15minutes) during a Sprint
Asks Three questions during meeting: What did you do yesterday? What will you do today? What obstacles are in your way?
Product Owner
Other engineers
Questions- What went well and what can be improved? Participants - Scrum Master - Team - Product owner
Product Backlog
A list of all desired work on the project List is prioritized by the Product Owner Typically a Product Manager, Marketing, Internal Customer, etc. Requirements for a system, expressed as a prioritized list of Backlog Items Is managed and owned by a Product Owner
Sprint Backlog
Scrum values
Transparency - visibility to everyone Commitment - willing to commit to a goal Courage - courage to commit, open, and to embrace change Focus focus on the work you have committed
% COMPLETED 05 % 10 % 15 % 30 % 35 % 50%
PROJECT ACTIVITIES
Statement of problem Synopsis evaluation Literature review Questionnaires design 2nd phase presentation Data collection
February
March
April
May
June
55 %
70% 80% 85 % 95 % 100 %
Data interpretation
Data processing Report writing 3rd Phase presentation
Draft Report 1,2,3 submission