Agile software development. System development of Agile.pptx
- 1. Welcome to my presentation Course Title: Analysis and Design of Information Systems Topic : Agile Model OF (SDLC) Presented By :- Md.Tasin Kadir
- 3. Contents • Objective • Introduction • Why Use Agile • The Agile Manifesto • 12 Principles Of Agile • 4 Core Values of Agile • Characteristics • Popular Agile Frameworks • Advantages • Disadvantages . QNA
- 4. Objective To help you understand the principles of Agile software development and successfully implement the software development life-cycle on your projects
- 5. What Is Agile Agile development is a phrase used in software development to describe methodologies for incremental software development. Introduction Agile Software Development Methodology in software development is an efficient methodology that helps teams produce high- quality software quickly and with flexibility. Agile is not just a methodology; it's a mindset. At its core, Agile values individuals and interactions, working solutions, and customer collaboration over strict processes and comprehensive documentation. It acknowledges that the needs and priorities of a project may change, emphasizing the importance of adaptability and continuous improvement
- 6. 1 Click here to add content of the text Write your text here Click here to add content of the text Write your text here Click here to add content of the text Write your text here 3 2 4 Why use agile Agile as a Mindset: Promotes collaboration, flexibility, and a positive work culture. Quick Response to Change: Helps teams adapt quickly to changing needs Regular Demonstrations: Ensures transparency and keeps stakeholders informed. Cross-Functional Teams: Encourages teamwork and shared responsibility.
- 8. 3 2 4 Click here to add content of the text Write your text here 1 Agile Manifesto Working software over comprehensiv e documentatio n Individuals and interactions over processes and tools Customer collaboratio n over contract negotiation Responding to change over following a plan
- 10. 12 agile principles 1.Custom Satisfaction 2.Changing requirements 3.Frequent delivery 4.Communication Regularly 5.Support team member 6.Face to face communication 7.Measure work progress 8.Development process 9.Good design 10.Measure Progress 11.continue seeking result 12 Reflect and adjust regularly.
- 11. 1.Satisfaction and delivery The first principle of the Agile Manifesto prioritizes customer satisfaction through early and continuous delivery of valuable software. By releasing working products in short iterations, Agile teams gather feedback and adapt quickly, ensuring the final product meets customer needs and expectations.
- 12. 2.Welcome Changing Embracing change in Agile helps teams stay flexible, deliver value, and ensure success. 1. Customer Satisfaction: Adapts to customer needs through continuous feedback. 2. Adaptability: Responds quickly to changes in the environment. 3. Continuous Improvement: Learns and improves throughout the project. 4. Risk Mitigation: Detects and fixes issues early. 5. Collaboration: Encourages team communication and ownership. 6. Continuous Delivery: Delivers small, frequent updates. 7. Stake holder Engagement: Builds trust through involvement and feedback.
- 13. 3.Deliver Frequently The “deliver value frequently” principle in Agile focuses on providing working product features regularly throughout the project. Using short iterations called sprints (usually 1–4 weeks), teams deliver small, usable parts of the product. This allows for early feedback, quick improvements, and ensures the product stays aligned with customer needs.
- 14. 4.Communication Is the Key Agile encourages working together and breaking silos to improve collaboration, communication, and decision-making. Cross-functional teams bring diverse skills, enabling faster problem-solving and higher- quality outcomes. This approach fosters continuous feedback, shared understanding, and adaptability, ensuring the project aligns with customer and business needs while promoting trust and shared ownership.
- 15. 5.Environment & Trust Supporting self-organizing teams is important because it gives members the freedom to plan, decide, and work together effectively. This builds ownership, encourages creativity, and helps teams adapt quickly and improve continuously.
- 16. 6.Face to face communication Agile values face-to-face communication as the best way to share information. It improves clarity, speeds up decisions, and builds stronger teamwork. 1. Richer Communication:Uses expressions, gestures, and tone to enhance understanding. 2. Immediate Clarification:Doubts are cleared instantly, avoiding delays. 3. Building Relationships and Trust:Encourages connection and trust among team members. 4. Faster Decision-Making:Quick discussions lead to faster, smarter choices. 5. Better Collaboration:Promotes teamwork and shared responsibility.
- 17. 7.Measuring progress by soft In Agile, working solutions are the main measure of progress because they show real, usable outcomes. First, they provide clear, tangible proof of what the team has achieved, allowing stakeholders to evaluate and give feedback. Second, regular delivery of working software supports learning and quick adaptation based on real user input. This helps ensure the product meets evolving needs and stays on track. Time spent is less important than delivering actual value.
- 18. 8.Sustainable development Agile promotes a constant and sustainable pace to ensure long-term team well- being and consistent productivity. This steady rhythm helps avoid burnout, supports quality work, and enables continuous delivery. It fosters work-life balance, adaptability, and ongoing improvement—leading to better results and customer satisfaction.
- 19. 7. Attention to details In Agile, continuous focus on technical excellence ensures high-quality, maintainable, and adaptable software. It reduces technical debt, speeds up delivery, and improves reliability. This approach supports innovation, teamwork, and long-term success by enabling faster responses to change and easier future development.
- 20. 10.The power of less Simplicity in Agile boosts efficiency by avoiding unnecessary complexity, reducing waste, and focusing on valuable features. It improves clarity, communication, and collaboration while making solutions easier to maintain and adapt to change. This leads to faster delivery, better quality, and ongoing value for customers.
- 21. 11. Self-Organizing teams Self-organizing teams make the best decisions because they understand the work deeply, bring diverse perspectives, and take ownership. Their contextual knowledge, collective intelligence, and accountability lead. Contextual Knowledge: They understand the project goals and challenges well, helping them make informed decisions. Collective Intelligence: Diverse skills and perspectives lead to creative, effective solutions. Ownership and Accountability: Team members feel responsible, so they stay committed and make thoughtful choices.
- 22. 12. Adjusting at regular intervals Agile teams regularly reflect to improve their work processes and become more effective. This reflection helps identify strengths, challenges, and areas for improvement. It fosters a culture of learning, adaptation, and continuous improvement. By analyzing past work, teams can make necessary changes to enhance collaboration, productivity, and product quality. Regular reflection ensures the team stays aligned with project goals and responds better to customer needs and market changes.
- 23. 4 Core Values of Agile Software Development The Agile Software Development Methodology Manifesto describe four core values of Agile in software development 1.Individuals and Interactions over Processes and Tools 2.Working Software over Comprehensive Documentation 3.Customer Collaboration over Contract Negotiation 4.Responding to Change over Following a Plan
- 24. Characteristics Modularity: Software is designed in independent, reusable units, allowing for easier modification and testing. Iterative: Development happens in cycles (iterations or sprints) where work is completed and reviewed, then used to refine the next iteration. Time-bound: Agile projects have fixed timeframes (sprints) for development, allowing for quick releases and feedback. Less defect: Agile focuses on quality through continuous testing, early feedback, and a culture of improvement, leading to fewer defects. Collaborative: Agile promotes teamwork and collaboration between developers, stakeholders, and customers. Incremental: Features are added in increments, with each increment building upon the previous one, leading to a complete product over time.
- 25. Popular Agile Framework Scrum XP Hybrid Custom Hybrid Kanban Extreme Programing(XP) Scrumban Lean Don't Know Popular Agile Framework 1.Scrum 2.Xp Hybrid 3.Extreme Programing 4.Kanban 5.Lean 6.Don't Know 7.Custom Hybrid 8.Scurmban
- 26. SCRUM
- 32. SCRUM • Scrum is a popular framework that is used whenever we want to develop complex products, Ken Schwaber and Jeff Sutherland are known as the people who developed Scrum. Scrum is a type of Agile framework. • Scrum is a management framework that teams use to self-organize tasks and work towards a common goal. It is a framework within which people can address complex adaptive problems while the productivity and creativity of delivering products are at the highest possible value. Scrum is a management framework that teams use to self-organize and work towards a common goal. • Scrum allows us to develop products of the highest value while making sure that we maintain creativity and productivity. • The iterative and incremental approach used in scrum allows the
- 33. Scrum Characteristics • Simple and scaleable • ▸ Empirical process • ▸ Short-term detailed planning with constant feedback provides simple inspect and adapt cycle • Simple techniques and work artifacts • Requirements are captured as user stories in a list of product backlog • Progress is made in Sprints • › Teams collaborating with the Product Owner • › Optimises working environment • Reduces organisational overhead • ▸ Detects everything that gets in the way of delivery • ▸ Fosters openness and demands visibility
- 34. Product Owner • ▸ Captures Product Vision • Represents the voice of the customer • ▸ Creates initial Product Backlog • Writes customer-centric items • ▸ Helps set the direction of the product • ▸ Accountable for ensuring that the Team delivers value to the business • Responsible for: • Product Backlog
- 35. Product Backlog • Contains all potential features, prioritized as an absolute ordering by business value. • ▸ It is therefore the "What" that will be built, sorted by importance. • ▸ It contains rough estimates of both business value and development effort. • Those estimates help the Product Owner to gauge the timeline and, to a limited extent prioritize.
- 36. Scrum team •These are the people who build products, make estimates •Scrum recommends team sizes of 7 •The teams are cross functional
- 37. Scrum Master • Combination of Coach, Fixer and Gatekeeper. • Make sure the project is progressing smoothly • ▸ Every team member has the tool they need to get the job done • ▸ Sets meetings • Monitors the work done • Facilitates release planning • ▸ to protect the team and keep them focused on the tasks at hand • ▸ servant-leader
- 38. SCRUM Roles • Three core roles and a range of ancillary roles • Core Scrum roles: • Product Owner • Team • Scrum Master • Ancillary roles: • Stakeholders (customers, vendors) • Managers (including Project Managers)
- 39. Sprint • Is an iteration • Can have 1 day of sprint planning, 4 days of work and 1 day of sprint review • ▸ Sprints are short duration milestones • ▸ Sprints range from a couple of days to 30 days • Need atleast 4 to a dozen sprints to get to the release
- 40. Extreme programming (XP) • Extreme programming (XP)is one of the most important software development frameworks of Agile models. It is used to improve software quality and responsiveness to customer requirements. • Extreme Programming (XP) is an Agile software development methodology that focuses on delivering high-quality software through frequent and continuous feedback, collaboration, and adaptation. XP emphasizes a close working relationship between the development team, the customer, and stakeholders, with an emphasis on rapid, iterative development and deployment.
- 42. Kanban • Kanban is a popular Agile Software Development Methodology. It is a signaling device that instructs the moving of parts in a ‘pull’ production system, developed as part of the TPS (Toyota Production System). Kanban is about envisioning the existing workflow in terms of steps. These steps can be created on the whiteboard. • The Kanban method is an approach to evolutionary and incremental systems and process change for organizations. A work-in-progress limited pull system is the central mechanism to uncover system operation (or process) complications and encourage collaboration to continuously improve the system.
- 44. Lean • Lean Software Development (LSD) is an agile framework used to streamline and optimize the software development process. It may also be referred to as the Minimum Viable Product (MVP) strategy as these ways of thinking are very similar since both intend to speed up development by focusing on new deliverables. • Lean Software Development (LSD) is an approach derived from lean manufacturing principles aimed at optimizing efficiency and minimizing waste in the software development process.
- 47. Advantage Of Agile 1. Focus on Customer Value: Agile delivers the most important features first and adapts to customer feedback to ensure maximum value. 2. Enhanced Team Morale and Motivation: Teams feel empowered and motivated through autonomy and shared ownership. 3. Stakeholder Collaboration: Agile fosters close collaboration and continuous feedback from all stakeholders. 4. Early and Continuous Delivery: Frequent releases allow early feedback, faster validation, and reduced risk. 5. Delivering High-Quality Software: Agile ensures quality through continuous testing, integration, and regular reviews. Disadvantage of Agile 1. Lack of Predictability: Agile’s flexible nature can make it hard to predict exact timelines and budgets. 2. Dependency on Customer Availability: Frequent feedback is crucial, so unavailability of customers can slow progress. 3. Scaling Agile: It’s challenging to scale Agile for large teams or complex projects due to coordination issues. 4. Dependency on Team Dynamics: Poor team communication or lack of experience can reduce productivity and quality. 5. Increased Overhead: Agile requires more time for planning, meetings, and coordination, which can add extra workload.
- 48. Most Usages Model of (SDLC) AGILE HYBRID WATER FALL Dev ops Others ( spiral, v- model etc)
- 49. Thank You
- 50. QNA
Editor's Notes
- #8: 单击此处编辑母版文本样式 第二级 第三级 第四级 第五级