Agile for developers
0 likes280 views
Scrum and agile frameworks provide several benefits for developers: 1) Success - Studies show agile projects have higher success rates than traditional waterfall methods. 2) Improved skills - Working across disciplines through practices like pair programming and code reviews helps developers gain new skills and become more well-rounded. 3) Autonomy - Self-organizing teams are accountable for delivering working software and make their own technical decisions, giving developers more autonomy over their work.
1 of 40
Download to read offline
![Yet another quote
The amateur is learning about his problem [...], the professional [...] is learning
about her profession - programming - and the problem being programmed is only
one incidental step in her process of development.
- The Psychology of Computer Programming, Gerald Weinberg, 1971.](https://image.slidesharecdn.com/aa6dc96c-80bb-483e-bfc5-3e2ecdf4e01b-170106172311/85/Agile-for-developers-37-320.jpg)
Ad
Recommended
Scrum master's role - top 20 challenges
Scrum master's role - top 20 challenges Viresh Doshi
油
The document outlines 21 challenges faced by Scrum Masters, including failing to meet commitments, poor estimations, lack of focus on sprint work, disorganized sprint reviews, low collaboration, insufficient ticket information, frequent scope changes, delivering nothing at the end of sprints, low motivation, reprioritizing features mid-sprint, lack of communication of company strategy and roadmap, inadequate backlog grooming, unclear quality ownership, poor timekeeping, lack of development improvements, teams that do not care about quality, lack of code transparency, insufficient test automation, deficient triage processes, limited DevOps practices, and code not being checked in daily.Technical Excellence Doesn't Just Happen - AgileIndy 2016
Technical Excellence Doesn't Just Happen - AgileIndy 2016Allison Pollard
油
This document summarizes a presentation about igniting a craftsmanship culture through technical excellence. It introduces the presenters and defines technical excellence as both delivering value today and building an adaptable product. It discusses how technical debt occurs and how continuous attention to quality enhances agility. Several practices are discussed that were tried to improve quality, such as test-driven development training, code clinics, and code reviews. It emphasizes that technical excellence requires ongoing learning and discipline to achieve long-term viability.Technical Excellence Doesn't Just Happen--Igniting a Craftsmanship Culture
Technical Excellence Doesn't Just Happen--Igniting a Craftsmanship CultureAllison Pollard
油
This document discusses igniting a culture of craftsmanship in software development. It argues that technical excellence is necessary for agility, as ignoring technical debt and quality will eventually slow a project. The document outlines some common causes of technical debt, such as cutting corners and overengineering. It also discusses how paying down technical debt through refactoring can improve both internal code quality and external customer outcomes. Overall, the document advocates for continuous attention to technical practices, automated testing, refactoring and simple designs in order to sustain agility in software development.Is management dead?
Is management dead?Flavius Stef
油
The document discusses the relevance of management in an agile environment, emphasizing the principles of the Agile Manifesto that prioritize self-organizing teams, customer satisfaction, and sustainable development. It contrasts traditional management practices with agile management, highlighting motivation, self-organization, and the importance of empowering teams. Key concepts include the role of a manager in setting goals and constraints while fostering an environment that promotes autonomy and collaboration among team members.Scrum And The Enterprise
Scrum And The EnterpriseJames Peckham
油
This document discusses strategies for scaling Scrum practices within large organizations. It addresses organizing teams, integrating work across teams, managing people and skills, prioritizing work in an enterprise backlog, and delivering value through iterative development focused on the highest priority items. Key challenges include integrating work across multiple teams and layers, managing specialized skills, and ensuring continuous delivery of value at the enterprise level.Big rewrites without big risks
Big rewrites without big risksFlavius Stef
油
The document discusses strategies for incremental refactoring in software development, emphasizing the importance of validation and continuous integration. It outlines a series of steps for transitioning applications and dealing with dependencies while keeping the software buildable and running at all times. It also highlights the challenges and best practices involved in architectural changes and refactoring processes.How to Ace Your Scrum Master Interview
How to Ace Your Scrum Master InterviewPavel Dabrytski
油
The document provides guidance on preparing for a scrum master interview, including traits to look for in candidates and tips for refining resumes. It outlines the importance of quantifiable experience and specific communication skills while also listing common interview questions and outcomes from previous hiring processes. Additional resources for preparation, including recommended books and contact information, are provided.The Tester Role & Scrum
The Tester Role & ScrumJohan Hoberg
油
Testers fit into the Scrum framework based on their competence rather than their role. Someone with testing competence can help with code and architecture design, writing acceptance criteria, testability, and test automation. They can also coach other members of the scrum team and provide a tester's perspective during retrospectives. While everyone on the scrum team is responsible for testing, someone with strong testing competence can help handle more complex testing problems. Their unique skills and perspective help support the overall scrum team.Stop throwing money out the window
Stop throwing money out the windowFlavius Stef
油
The document discusses techniques for minimizing waste when developing products. It recommends using lean startup principles like building minimum viable products and getting early customer feedback through techniques like interviews and A/B testing. This allows businesses to learn quickly what customers want rather than wasting money on unnecessary features. Examples are given of how these principles were applied to develop an email digest product and plan a leadership workshop. The key is to start with the customer's problem, make assumptions explicit, and continually refine the product based on what is learned from real users.Kens Scrum Presentation
Kens Scrum PresentationJames Peckham
油
The document discusses several key aspects of Scrum:
1. Scrum is a framework based on empirical process control that was developed from lessons learned by companies like Toyota. It focuses on transparency, inspection, and adaptation.
2. Scrum provides a framework for self-organizing cross-functional teams to deliver working software frequently in short iterations with a "Done" definition.
3. Common reasons cited for Scrum failures include underlying problems in the organization already existing prior to adopting Scrum, as well as unwillingness to change engineering practices or deliver working code each iteration.What does a Scrum Master do, or should do, all day?
What does a Scrum Master do, or should do, all day? Stefania Marinelli
油
A Scrum Master facilitates the Scrum process, creates rhythm and sets expectations for projects and team members. They facilitate daily stand-ups and meetings, enhance communication, and act as an approachable coach through 1:1 meetings and active listening. Scrum Masters also train teams, products, and the organization on Agile practices.Mindset: the biggest barrier to agility
Mindset: the biggest barrier to agilityFlavius Stef
油
The document discusses the challenges organizations face during agile transformations, attributing a significant portion of failures to traditional mindsets that hinder adaptability. It highlights the importance of shifting to an agile mindset that empowers individuals and prioritizes customer value, while also suggesting strategies for change such as using the 5 Whys and fostering self-organization. The content emphasizes understanding beliefs about people, optimizing system design, and recognizing true customer needs to improve transformation outcomes.Scrum plus why scrum is not enough for successful delivery
Scrum plus why scrum is not enough for successful deliveryNaveen Kumar Singh
油
The document discusses the limitations of the Scrum framework and advocates for integrating additional engineering practices like TDD, BDD, and DevOps to enhance delivery success. It emphasizes collaboration, addressing common issues like ambiguous requirements and ineffective metrics, and suggests evolving Scrum into a more comprehensive agile approach. It also promotes continuous learning through workshops and practical experiences in Agile methodologies.The Impact of Culture on Distributed Agile - DiscussAgile - May 07 2016
The Impact of Culture on Distributed Agile - DiscussAgile - May 07 2016gmaran23
油
The document discusses the impact of cultural factors on distributed agile software development and offers solutions to improve communication and team effectiveness. It emphasizes the significance of hiring practices, onboarding processes, continuous improvement, and fostering an environment of trust and collaboration. The document highlights the necessity for investments in tools and infrastructure to facilitate better communication and self-organization among teams.What Can I Learn From You?
What Can I Learn From You?gmaran23
油
1. The document discusses improving team presentations at Big Sprint Days by focusing on showcasing lessons learned and work, rather than just presenting status updates. It suggests sharing specific tactics or ideas that others can apply, like how a team improved cross-functionality or crafted good sprint goals.
2. The document also addresses challenges with current Big Sprint Day presentations like them being unstructured with no feedback. It notes presentations should be timeboxed and focus on 2-3 key takeaways that are useful for others.
3. The document emphasizes that presenters should consider what others can learn from their presentation and experiences, not just provide status updates, in order to make the presentations more valuable.Titas Lapinskas - Technical Team Leader in Agile
Titas Lapinskas - Technical Team Leader in AgileAgile Lietuva
油
This document discusses the role of a technical team leader in agile projects. It describes when Scrum works well for projects, such as those with stable teams developing codebases over many years. It also discusses when Scrum may not be suitable, like for short-term projects with fixed costs, schedules, and scopes. The technical team leader acts as a group player, specialist, and manager, providing technical leadership. Their responsibilities include infrastructure setup, prototyping, documentation, and code reviews when needed. The goal is to help the team grow their skills over time and avoid failures by preventing issues before they occur.How to Kick Start a New Scrum Team - Agility and HR at Delft Netherlands 21 J...
How to Kick Start a New Scrum Team - Agility and HR at Delft Netherlands 21 J...gmaran23
油
The document outlines strategies for effectively onboarding new scrum team members, emphasizing the importance of agile principles, team dynamics, and frequent feedback. It highlights the need for establishing clear expectations, creating a collaborative team environment, and providing appropriate tools and challenges for new employees. Additionally, it discusses the role of values and culture in shaping the onboarding experience and promoting successful integration into the scrum framework.Scrum Master Lessons from my 4 Year Old Son
Scrum Master Lessons from my 4 Year Old SonRyan Ripley
油
The document outlines key lessons for Scrum Masters derived from personal experience, emphasizing the need for continuous improvement, effective communication, and the importance of a sustainable pace in Agile practices. It highlights the significance of learning from failures and adapting to team dynamics while fostering an inclusive environment. Additionally, it underscores the role of Scrum Masters in supporting team autonomy and addressing impediments for better productivity.Agile and scrum masterclass
Agile and scrum masterclassDanish Khan
油
Agile and Scrum Masterclass provides a comprehensive video course on Agile and Scrum frameworks. The course covers topics from introductory concepts to advanced practices. Students will gain skills and understanding to implement Scrum successfully, pass certification exams, and deliver projects more efficiently. The benefits outlined include strong Scrum knowledge, preparedness for roles as Product Owner or Scrum Master, and tools to anticipate and address issues. The course developer has over 10 years of Agile experience and aims to fill gaps in students' professional development through the extensive curriculum.Automation is hard and we are doing it wrong
Automation is hard and we are doing it wrongJohan Abildskov
油
The document discusses the challenges and misconceptions surrounding automation in DevOps, arguing that it is not a luxury but a necessity for effective business operations. It emphasizes the need for cultural change, strategic planning, and measurable goals in automation initiatives to overcome current limitations. Additionally, the author highlights the importance of testability and the risks associated with manual processes, advocating for a shift towards automation to improve performance.Agile development makes elephants dance
Agile development makes elephants danceEthan Huang
油
This document discusses agile development and how it can help address issues with traditional waterfall development approaches. It provides an overview of agile principles from the Agile Manifesto, popular agile methodologies like Scrum and XP, and how agile practices emphasize iterative development, emergent requirements, frequent inspection/adaptation, and valuing individuals/interaction over processes. A real example is given of how adopting scrum helped turn around a failing project that was over budget and delivering poor quality.Why Does Agile Work?
Why Does Agile Work?Matthew Caine
油
The document provides an overview of a presentation given by Matthew Caine on why Agile works. Some key points:
- Agile focuses on people and results above all else
- Traditional management kills motivation in the workplace
- Steve Denning discovered motivated "geeks" using Agile and wanted to understand why it worked
- Humans need autonomy, mastery, and purpose to be motivated according to Daniel Pink
- Agile provides these things by allowing autonomy over work, mastery through continuous learning, and a sense of purpose in adaptive planning
- Agile ceremonies like planning, stand-ups, reviews, and retrospectives create a structure that embraces emergent details and continuous improvementKaizen in Action
Kaizen in ActionKiro Harada
油
This document outlines Kiro Harada's presentations on Kaizen (continuous improvement) at the Agile Conference Vietnam 2016 and Agile Tour Bangkok 2016. It discusses why Kaizen is important, provides examples of how Toyota implemented early Kaizen practices, and gives suggestions for how individuals and teams can incorporate Kaizen into their work. The key messages are that Kaizen should be continuous, addressing both individual and team improvement, and that creating slack/downtime is necessary before beginning any Kaizen activities to avoid overwork and burnout.Feedback - The Secret ingredient of success
Feedback - The Secret ingredient of successElad Sofer
油
The document discusses the differences between home cooks and professional chefs, as well as differences in feedback loops between agile software development processes and traditional processes. It notes that chefs receive constant feedback while cooking that allows them to adjust their dish, unlike home cooks who just follow recipes without tasting. For software development, it describes how agile processes have much shorter and more frequent feedback loops at various levels compared to traditional processes, such as having code reviews that take minutes instead of days and unit testing that provides feedback in minutes rather than weeks. Keeping feedback loops short, frequent, and at multiple levels is key to success with agile methods. Coaching Anti-Pattens and common smells
Coaching Anti-Pattens and common smellsSekhar Burra, CEC, P-CST
油
Sekhar Burra is an agile transformation coach who has led two large-scale agile transformations. He has experience as an executive agile coach, scrum master, product owner, and engineering manager. The document discusses a scenario where a coach provides feedback to a client about improving their daily stand-ups by addressing the three standard questions. It then defines what patterns and anti-patterns are in the context of agile development before giving examples of common anti-patterns and smells like having no retrospectives or one team member dominating planning meetings. Coaching techniques for addressing anti-patterns at the team and organizational level are discussed, including learning design patterns and using mocks, Jutta Eckstein's perspectives, and retrospectiveContinuous Deployment
Continuous DeploymentKane Mar
油
The document discusses continuous deployment as an advanced form of continuous integration, emphasizing its benefits such as reduced integration problems and faster software development. It outlines the importance of feedback, value, and reducing waste to stay competitive, while also highlighting challenges like the need for extensive automated testing. Suggestions for adopting continuous deployment include starting with continuous integration and establishing real-time monitoring, along with a caution against allowing broken tests and setting unrealistic expectations.Scrum Bangalore 13th meet up 13 june 2015 - behaviour driven development - vi...
Scrum Bangalore 13th meet up 13 june 2015 - behaviour driven development - vi...Scrum Bangalore
油
The document discusses Behavior Driven Development (BDD), emphasizing its role in improving communication among stakeholders (the 'three amigos': business, developers, and testers) to clarify requirements and minimize misunderstandings. It introduces core BDD concepts such as writing specifications in user-friendly language using Gherkin, the importance of real-world examples for clarity, and best practices to avoid shallow implementations. Ultimately, it promotes collaborative efforts to define and validate system behaviors, ensuring all parties have a shared understanding of the project goals.Agile Roles & responsibilities
Agile Roles & responsibilitiesRavi Tadwalkar
油
This document discusses how roles and responsibilities change in Agile/Scrum frameworks compared to traditional organizations. It outlines several key Agile roles including Product Owner, Scrum Master, and Scrum Team Members. It also discusses how requirements, design, testing, and tracking emerge incrementally rather than being fully planned upfront. Cultural shifts involve moving from big requirements/design upfront to emergent approaches. The roles of Architect, User Experience Lead, Internal Coach/Mentor, Agile Program Manager, and Functional Manager are also described.Agile Pmi 102108 Final
Agile Pmi 102108 Finalbmcglin
油
The document outlines the principles and practices of lean agile scrum methodologies aimed at maximizing ROI and minimizing errors in software development. It discusses the shortcomings of traditional waterfall approaches and emphasizes the importance of customer involvement, emergent design, and built-in quality through iterative processes. Additionally, it explains the roles within scrum teams and the significance of delivering business value through agile methods.亠仄 亳从仂于亠 "Why Scrum is so often "Failed" and criticised" Lviv Project M...
亠仄 亳从仂于亠 "Why Scrum is so often "Failed" and criticised" Lviv Project M...Lviv Startup Club
油
Scrum is often criticized as "failed" due to typical barriers such as a project mindset instead of a product mindset, isolated teams instead of interconnected networks, and rushing into agile practices without establishing software craftsmanship. The document outlines seven common barriers to successful scrum implementation and provides solutions such as adopting a product mindset, establishing self-managing cross-functional teams, emphasizing software craftsmanship principles, replacing heroism with collaborative problem solving, taking an empirical view instead of a certainty mindset, practicing professional scrum over mechanical scrum processes, and scaling the product rather than scrum practices.More Related Content
What's hot (20)
Stop throwing money out the window
Stop throwing money out the windowFlavius Stef
油
The document discusses techniques for minimizing waste when developing products. It recommends using lean startup principles like building minimum viable products and getting early customer feedback through techniques like interviews and A/B testing. This allows businesses to learn quickly what customers want rather than wasting money on unnecessary features. Examples are given of how these principles were applied to develop an email digest product and plan a leadership workshop. The key is to start with the customer's problem, make assumptions explicit, and continually refine the product based on what is learned from real users.Kens Scrum Presentation
Kens Scrum PresentationJames Peckham
油
The document discusses several key aspects of Scrum:
1. Scrum is a framework based on empirical process control that was developed from lessons learned by companies like Toyota. It focuses on transparency, inspection, and adaptation.
2. Scrum provides a framework for self-organizing cross-functional teams to deliver working software frequently in short iterations with a "Done" definition.
3. Common reasons cited for Scrum failures include underlying problems in the organization already existing prior to adopting Scrum, as well as unwillingness to change engineering practices or deliver working code each iteration.What does a Scrum Master do, or should do, all day?
What does a Scrum Master do, or should do, all day? Stefania Marinelli
油
A Scrum Master facilitates the Scrum process, creates rhythm and sets expectations for projects and team members. They facilitate daily stand-ups and meetings, enhance communication, and act as an approachable coach through 1:1 meetings and active listening. Scrum Masters also train teams, products, and the organization on Agile practices.Mindset: the biggest barrier to agility
Mindset: the biggest barrier to agilityFlavius Stef
油
The document discusses the challenges organizations face during agile transformations, attributing a significant portion of failures to traditional mindsets that hinder adaptability. It highlights the importance of shifting to an agile mindset that empowers individuals and prioritizes customer value, while also suggesting strategies for change such as using the 5 Whys and fostering self-organization. The content emphasizes understanding beliefs about people, optimizing system design, and recognizing true customer needs to improve transformation outcomes.Scrum plus why scrum is not enough for successful delivery
Scrum plus why scrum is not enough for successful deliveryNaveen Kumar Singh
油
The document discusses the limitations of the Scrum framework and advocates for integrating additional engineering practices like TDD, BDD, and DevOps to enhance delivery success. It emphasizes collaboration, addressing common issues like ambiguous requirements and ineffective metrics, and suggests evolving Scrum into a more comprehensive agile approach. It also promotes continuous learning through workshops and practical experiences in Agile methodologies.The Impact of Culture on Distributed Agile - DiscussAgile - May 07 2016
The Impact of Culture on Distributed Agile - DiscussAgile - May 07 2016gmaran23
油
The document discusses the impact of cultural factors on distributed agile software development and offers solutions to improve communication and team effectiveness. It emphasizes the significance of hiring practices, onboarding processes, continuous improvement, and fostering an environment of trust and collaboration. The document highlights the necessity for investments in tools and infrastructure to facilitate better communication and self-organization among teams.What Can I Learn From You?
What Can I Learn From You?gmaran23
油
1. The document discusses improving team presentations at Big Sprint Days by focusing on showcasing lessons learned and work, rather than just presenting status updates. It suggests sharing specific tactics or ideas that others can apply, like how a team improved cross-functionality or crafted good sprint goals.
2. The document also addresses challenges with current Big Sprint Day presentations like them being unstructured with no feedback. It notes presentations should be timeboxed and focus on 2-3 key takeaways that are useful for others.
3. The document emphasizes that presenters should consider what others can learn from their presentation and experiences, not just provide status updates, in order to make the presentations more valuable.Titas Lapinskas - Technical Team Leader in Agile
Titas Lapinskas - Technical Team Leader in AgileAgile Lietuva
油
This document discusses the role of a technical team leader in agile projects. It describes when Scrum works well for projects, such as those with stable teams developing codebases over many years. It also discusses when Scrum may not be suitable, like for short-term projects with fixed costs, schedules, and scopes. The technical team leader acts as a group player, specialist, and manager, providing technical leadership. Their responsibilities include infrastructure setup, prototyping, documentation, and code reviews when needed. The goal is to help the team grow their skills over time and avoid failures by preventing issues before they occur.How to Kick Start a New Scrum Team - Agility and HR at Delft Netherlands 21 J...
How to Kick Start a New Scrum Team - Agility and HR at Delft Netherlands 21 J...gmaran23
油
The document outlines strategies for effectively onboarding new scrum team members, emphasizing the importance of agile principles, team dynamics, and frequent feedback. It highlights the need for establishing clear expectations, creating a collaborative team environment, and providing appropriate tools and challenges for new employees. Additionally, it discusses the role of values and culture in shaping the onboarding experience and promoting successful integration into the scrum framework.Scrum Master Lessons from my 4 Year Old Son
Scrum Master Lessons from my 4 Year Old SonRyan Ripley
油
The document outlines key lessons for Scrum Masters derived from personal experience, emphasizing the need for continuous improvement, effective communication, and the importance of a sustainable pace in Agile practices. It highlights the significance of learning from failures and adapting to team dynamics while fostering an inclusive environment. Additionally, it underscores the role of Scrum Masters in supporting team autonomy and addressing impediments for better productivity.Agile and scrum masterclass
Agile and scrum masterclassDanish Khan
油
Agile and Scrum Masterclass provides a comprehensive video course on Agile and Scrum frameworks. The course covers topics from introductory concepts to advanced practices. Students will gain skills and understanding to implement Scrum successfully, pass certification exams, and deliver projects more efficiently. The benefits outlined include strong Scrum knowledge, preparedness for roles as Product Owner or Scrum Master, and tools to anticipate and address issues. The course developer has over 10 years of Agile experience and aims to fill gaps in students' professional development through the extensive curriculum.Automation is hard and we are doing it wrong
Automation is hard and we are doing it wrongJohan Abildskov
油
The document discusses the challenges and misconceptions surrounding automation in DevOps, arguing that it is not a luxury but a necessity for effective business operations. It emphasizes the need for cultural change, strategic planning, and measurable goals in automation initiatives to overcome current limitations. Additionally, the author highlights the importance of testability and the risks associated with manual processes, advocating for a shift towards automation to improve performance.Agile development makes elephants dance
Agile development makes elephants danceEthan Huang
油
This document discusses agile development and how it can help address issues with traditional waterfall development approaches. It provides an overview of agile principles from the Agile Manifesto, popular agile methodologies like Scrum and XP, and how agile practices emphasize iterative development, emergent requirements, frequent inspection/adaptation, and valuing individuals/interaction over processes. A real example is given of how adopting scrum helped turn around a failing project that was over budget and delivering poor quality.Why Does Agile Work?
Why Does Agile Work?Matthew Caine
油
The document provides an overview of a presentation given by Matthew Caine on why Agile works. Some key points:
- Agile focuses on people and results above all else
- Traditional management kills motivation in the workplace
- Steve Denning discovered motivated "geeks" using Agile and wanted to understand why it worked
- Humans need autonomy, mastery, and purpose to be motivated according to Daniel Pink
- Agile provides these things by allowing autonomy over work, mastery through continuous learning, and a sense of purpose in adaptive planning
- Agile ceremonies like planning, stand-ups, reviews, and retrospectives create a structure that embraces emergent details and continuous improvementKaizen in Action
Kaizen in ActionKiro Harada
油
This document outlines Kiro Harada's presentations on Kaizen (continuous improvement) at the Agile Conference Vietnam 2016 and Agile Tour Bangkok 2016. It discusses why Kaizen is important, provides examples of how Toyota implemented early Kaizen practices, and gives suggestions for how individuals and teams can incorporate Kaizen into their work. The key messages are that Kaizen should be continuous, addressing both individual and team improvement, and that creating slack/downtime is necessary before beginning any Kaizen activities to avoid overwork and burnout.Feedback - The Secret ingredient of success
Feedback - The Secret ingredient of successElad Sofer
油
The document discusses the differences between home cooks and professional chefs, as well as differences in feedback loops between agile software development processes and traditional processes. It notes that chefs receive constant feedback while cooking that allows them to adjust their dish, unlike home cooks who just follow recipes without tasting. For software development, it describes how agile processes have much shorter and more frequent feedback loops at various levels compared to traditional processes, such as having code reviews that take minutes instead of days and unit testing that provides feedback in minutes rather than weeks. Keeping feedback loops short, frequent, and at multiple levels is key to success with agile methods. Coaching Anti-Pattens and common smells
Coaching Anti-Pattens and common smellsSekhar Burra, CEC, P-CST
油
Sekhar Burra is an agile transformation coach who has led two large-scale agile transformations. He has experience as an executive agile coach, scrum master, product owner, and engineering manager. The document discusses a scenario where a coach provides feedback to a client about improving their daily stand-ups by addressing the three standard questions. It then defines what patterns and anti-patterns are in the context of agile development before giving examples of common anti-patterns and smells like having no retrospectives or one team member dominating planning meetings. Coaching techniques for addressing anti-patterns at the team and organizational level are discussed, including learning design patterns and using mocks, Jutta Eckstein's perspectives, and retrospectiveContinuous Deployment
Continuous DeploymentKane Mar
油
The document discusses continuous deployment as an advanced form of continuous integration, emphasizing its benefits such as reduced integration problems and faster software development. It outlines the importance of feedback, value, and reducing waste to stay competitive, while also highlighting challenges like the need for extensive automated testing. Suggestions for adopting continuous deployment include starting with continuous integration and establishing real-time monitoring, along with a caution against allowing broken tests and setting unrealistic expectations.Scrum Bangalore 13th meet up 13 june 2015 - behaviour driven development - vi...
Scrum Bangalore 13th meet up 13 june 2015 - behaviour driven development - vi...Scrum Bangalore
油
The document discusses Behavior Driven Development (BDD), emphasizing its role in improving communication among stakeholders (the 'three amigos': business, developers, and testers) to clarify requirements and minimize misunderstandings. It introduces core BDD concepts such as writing specifications in user-friendly language using Gherkin, the importance of real-world examples for clarity, and best practices to avoid shallow implementations. Ultimately, it promotes collaborative efforts to define and validate system behaviors, ensuring all parties have a shared understanding of the project goals.Agile Roles & responsibilities
Agile Roles & responsibilitiesRavi Tadwalkar
油
This document discusses how roles and responsibilities change in Agile/Scrum frameworks compared to traditional organizations. It outlines several key Agile roles including Product Owner, Scrum Master, and Scrum Team Members. It also discusses how requirements, design, testing, and tracking emerge incrementally rather than being fully planned upfront. Cultural shifts involve moving from big requirements/design upfront to emergent approaches. The roles of Architect, User Experience Lead, Internal Coach/Mentor, Agile Program Manager, and Functional Manager are also described.Similar to Agile for developers (20)
Agile Pmi 102108 Final
Agile Pmi 102108 Finalbmcglin
油
The document outlines the principles and practices of lean agile scrum methodologies aimed at maximizing ROI and minimizing errors in software development. It discusses the shortcomings of traditional waterfall approaches and emphasizes the importance of customer involvement, emergent design, and built-in quality through iterative processes. Additionally, it explains the roles within scrum teams and the significance of delivering business value through agile methods.亠仄 亳从仂于亠 "Why Scrum is so often "Failed" and criticised" Lviv Project M...
亠仄 亳从仂于亠 "Why Scrum is so often "Failed" and criticised" Lviv Project M...Lviv Startup Club
油
Scrum is often criticized as "failed" due to typical barriers such as a project mindset instead of a product mindset, isolated teams instead of interconnected networks, and rushing into agile practices without establishing software craftsmanship. The document outlines seven common barriers to successful scrum implementation and provides solutions such as adopting a product mindset, establishing self-managing cross-functional teams, emphasizing software craftsmanship principles, replacing heroism with collaborative problem solving, taking an empirical view instead of a certainty mindset, practicing professional scrum over mechanical scrum processes, and scaling the product rather than scrum practices.亠仄 亳从仂于亠 - Agile at scale: 弌hallenges & Fails
亠仄 亳从仂于亠 - Agile at scale: 弌hallenges & FailsTimetogrowup
油
Artem Bykovets discusses typical barriers to agile at scale and potential solutions. Common barriers include having a project mindset rather than a product mindset, isolated "Scrum of Scrums" teams rather than an interconnected network, and focusing on rushing to adopt agile practices rather than developing software craftsmanship. Potential solutions are adopting a product mindset, creating a network of self-managing teams, emphasizing software craftsmanship practices, shifting from heroism to collaborative management, taking an empirical rather than certainty mindset, implementing professional Scrum rather than mechanical Scrum processes, and scaling products rather than Scrum practices.Introduction to Agile & scrum
Introduction to Agile & scrumElad Sofer
油
The document discusses key concepts in Agile and Scrum project management frameworks. It outlines some common misconceptions about Agile, describes Scrum roles and ceremonies like sprint planning and review meetings, and emphasizes that adopting Scrum requires changes to team dynamics, skills, and work habits.The Agile Readiness Assessment Tool Essay
The Agile Readiness Assessment Tool EssayHeidi Owens
油
This report discusses Scrum, an agile software development methodology. It describes the key roles in Scrum - Product Owner, Scrum Master, and Development Team. It also outlines the core Scrum events - Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective. The report examines the Scrum process and how it aims to deliver working software frequently through short development cycles called sprints. It emphasizes that Scrum provides structure through its roles, events, and artifacts while allowing flexibility through its iterative approach.Ultimate Guide on How to Run Performance Review
Ultimate Guide on How to Run Performance ReviewValentine201794
油
This guide outlines how to conduct effective software developer performance reviews, emphasizing the importance of regular evaluations to enhance team productivity and address issues like burnout and lack of clear career paths. It advocates for 360-degree feedback to provide comprehensive insights into employee performance and skill gaps, facilitating targeted development plans. By scheduling reviews in alignment with the software development life cycle and individual employee needs, managers can create a culture of continuous improvement and engagement within their teams.iSQI Certification Days DASA DevOps & ISTQB Frank Frambach
iSQI Certification Days DASA DevOps & ISTQB Frank FrambachIevgenii Katsan
油
Frank Frambach presented on DevOps and testing. Some key points:
1. DevOps is driven by digital business models that require faster development and delivery of new features.
2. The DevOps Agile Skills Association (DASA) provides a competence model and certification program to develop high-performing IT professionals in DevOps.
3. Testing is an important part of DevOps and is integrated into several areas of the DASA competence model, including test specification, programming, and infrastructure engineering.
4. Bob, a tester, is shown undertaking a journey through the DASA model, first learning about DevOps and then developing his skills in related areas to transition into a DevOpsAgile Cafe Boulder - Panelist and keynote slides
Agile Cafe Boulder - Panelist and keynote slidesCloud Elements
油
The document compares the Waterfall and Agile methodologies in the context of Colorado Springs Utilities' energy distribution design projects, highlighting challenges faced during Agile adoption and successes that followed. Key results include delivering software under budget, reducing complexity, and achieving higher user satisfaction due to Agile practices. It emphasizes the importance of organizational change, commitment to Agile principles, and continuous improvement in software development processes.Seven Keys to Navigating Your Agile Testing Transition
Seven Keys to Navigating Your Agile Testing TransitionTechWell
油
The document presents a tutorial by Bob Galen on navigating agile testing transitions, outlining various myths and realities related to agile testing methodologies. It emphasizes the importance of mixed skill sets within teams, the necessity of planning and automation, the roles of testers and developers, and the significance of continuous improvement and collaboration. The final sections advocate for adopting a comprehensive strategy involving risk-based testing and cross-functional practices to enhance quality in agile environments.Agile Transformation 101
Agile Transformation 101Beverley Sutherland
油
This document provides an overview of Agile methodology and Scrum framework. It defines key Agile and Scrum terms like sprints, self-organizing teams, product owner, and scrum master roles. The document outlines an Agile transformation presentation agenda, explaining concepts like why Agile is used, common misconceptions, and how good communication is critical to Agile success. Scrum roles and ceremonies are defined, with an emphasis on delivering working software frequently through short iterations.E-Commerce Project Management
E-Commerce Project ManagementJanette Toral
油
Janette Toral's e-commerce project management emphasizes the multifaceted role of an e-commerce project manager, highlighting the importance of beginning with a clear end goal. The document covers the Scrum framework, detailing roles such as the product owner and scrummaster, as well as the iterative nature of project development through sprints. It also discusses various digital marketing strategies and the significance of customer relationship management in achieving business success.Agile Truths and Misconceptions
Agile Truths and MisconceptionsRichard Cheng
油
This document discusses truths and misconceptions about agile software development. It begins by establishing that agile is more than a high-level concept, and discusses differences between traditional project management and agile principles. Key differences between agile methodologies like Scrum and XP are outlined. The document then addresses common misconceptions about agile and Scrum, establishing truths around topics like planning, fixed-date projects, risk management, rework, and the role of metrics and documentation in Scrum.Scqaa sf scrum presentation - final
Scqaa sf scrum presentation - finalSujit Ghosh
油
The document introduces Scrum and Agile methodologies. It provides an overview of key Scrum concepts such as self-organizing cross-functional teams, Product Owners, User Stories, and Sprints. It also discusses Scrum roles, ceremonies, and artifacts. Challenges of Scrum include requirements of education, buy-in, and strong team members. Benefits include happier employees, less risk of failure, and more flexible adaptation to change.Agile Intro - Saint Louis Day of Dot Net
Agile Intro - Saint Louis Day of Dot NetBrian Blanchard
油
This document provides a comprehensive overview of Agile methodologies, tracing its historical development from the Waterfall model to Agile practices that emphasize iterative processes and customer collaboration. It highlights the advantages of Agile, such as increased productivity, faster time to market, and improved quality, while also addressing common misconceptions and challenges to implementation. The document concludes with discussions on Agile practices, such as estimation strategies, testing approaches, and the importance of feedback loops.Ultimate Guide on Software Engineer Career Progression
Ultimate Guide on Software Engineer Career Progression Valentine201794
油
The document outlines the importance of establishing a software engineer career progression framework for tech companies to enhance employee motivation, development, and retention. It discusses various career ladder structures based on company size, provides tools for managers to effectively plan career progression, and highlights benefits for both employees and organizations. Additionally, it includes templates and examples from successful tech companies to assist in building a tailored career path framework.Agile for Business
Agile for BusinessDigitalCatapultDevelopmentPractices
油
The document outlines the principles and practices of Agile methodology, focusing on its application within software development and beyond. It covers topics like Agile values, Scrum rules, user stories, and the concept of business agility. Key competencies to be gained include understanding Agile's value proposition and differentiating it from Scrum, as well as exploring its wider applications in various business contexts.2010 03 09 the lean startup - gdc
2010 03 09 the lean startup - gdcEric Ries
油
The document discusses techniques for building startups using a lean startup methodology. It advocates for building minimum viable products and rapidly iterating based on customer feedback. Key principles include continuous deployment of code, conducting split tests to validate hypotheses, and using metrics to measure progress and make decisions. The goal is to minimize the time to learn what customers want through short development cycles and frequent releases.Scrum-Agile : An Introduction
Scrum-Agile : An IntroductionGlobal SQA
油
The document provides an introduction to Agile and Scrum methodologies, outlining the twelve principles of Agile and the structure of Scrum processes, roles, and responsibilities. It emphasizes the benefits of Agile, including faster time to market, improved communication, and greater adaptability to changing priorities, while also discussing challenges such as the need for business commitment and effective communication in distributed teams. Scrum is presented as a framework for iterative product development, where cross-functional teams work collaboratively to deliver potentially shippable increments of functionality in fixed-length sprints.Kevin Graves SCQAA-SF Scrum Presentation
Kevin Graves SCQAA-SF Scrum PresentationKevin Graves
油
The document provides an overview of Agile and Scrum methodologies, highlighting their principles, benefits, and challenges. It emphasizes the importance of frequent inspection and adaptation, empowered teams, and customer collaboration over traditional waterfall approaches. Key concepts include Scrum roles, artifacts, and the structure of sprints, aimed at improving project management and delivering value more efficiently.Agile Experience In Complex Projects
Agile Experience In Complex ProjectsBorys Lebeda
油
The document discusses several challenges for implementing agile practices in complex projects. It emphasizes the importance of having the right product owner and manager who understand agile principles and can help organize cross-functional teams. Establishing a knowledge base and continuous integration are also highlighted as important for facilitating collaboration across distributed teams working on evolving products.Ad
Agile for developers
- 1. Agile(scrum) for developers Whats in it for us? @jeteve - Broadbean - 2016
- 3. (In agile)
- 4. Why believe?
- 5. Facts
- 6. Back in the days
- 7. Back in the days Failure (Grumpy stakeholders, Boss fired, Company closing down)
- 8. Then..
- 9. Then.. Product did start making lot of money just fine. Still does, though less and less over time. Product grinds to a halt. Code rots sets in.
- 10. Regaining hope
- 11. Regaining hope Result: Success! Steady increase of revenue over time. Everyones happy. (Scrum)
- 12. First thing in it for us: http://clearcode.cc/2014/12/agile-vs-waterfall-method/ Dr. Dobbs Journal 2013 IT Project Success Survey posted at www.ambysoft.com/surveys/
- 13. First thing in it for us: Success
- 14. Agile Team Roles
- 15. Roles QA Tester Architect Product Manager Graphic designer Devops Tech lead DB Admin Developer Release manager Scrum Master Junior Developer Front end developer BI Analyst SysAdmin UX designer Backend Developer Business Analyst Project Manager
- 16. From the Scrum Alliance Scrum Guide: Scrum recognizes no titles for Development Team members other than Developer, regardless of the work being performed by the person; there are no exceptions to this rule;
- 17. Roles QA Tester Architect Product Manager Graphic designer Devops Tech lead DB Admin Developer Release manager Scrum Master Junior Developer Front end developer BI Analyst SysAdmin UX designer Backend Developer Business Analyst Project Manager
- 18. From the Scrum Alliance scrum Guide: - Development Teams are cross-functional, with all of the skills as a team necessary to create a product Increment; - Individual Development Team members may have specialized skills and areas of focus, but accountability belongs to the Development Team as a whole.
- 19. All of that? Developers:
- 20. Goal: +1 in all < 4
- 21. Second thing in it for us: Through sharing of knowledge, Pair programming, Clear and documented code, Constant learning, Looking for help, Cross reviewing, Your skill set will improve and widen. You will become a more competent and balanced professional. Capable of building larger and more complex software without the constant help of experts.
- 22. The bad: Maybe youll lose very specialized knowledge.
- 27. From Rabelaiss book about the Abbey of Theleme: Do What Thou Wilt; because men that are free, well-born, well-bred, and conversant in honest companies, have naturally an instinct and spur that prompteth them unto virtuous actions, and withdraws them from vice, which is called honour. (1534) https://en.wikipedia.org/wiki/Fran%C3%A7ois_Rabelais
- 28. From the holy scrum guide: Development team members are self-organizing. No one (not even the Scrum Master) tells the Development Team how to turn Product Backlog into Increments of potentially releasable functionality; Scrum recognizes no sub-teams in the Development Team, regardless of particular domains that need to be addressed like testing or business analysis; there are no exceptions to this rule;
- 29. Third thing in it for us: The team takes technical decisions independently, is accountable for releasing working software. Autonomy. Agile recognize that you are a fully functional adult being, with their own will (Thelema), accountable for their actions. You will make mistakes..
- 30. Creating the conditions of change
- 31. Agile - Change
- 32. Change at product level Market changes Requirements change Expectations change Scope change -> PM constantly re-order and enrich the product backlog.
- 33. Change at Process/Team Level Things work Other dont New issues appear People skills change Quality/Stability should always be improving -> SM scrum retrospectives and enforces actions
- 34. Change at technical level Chosen technologies become limited or obsolete. Design mistakes were made. Features must be added or change. Quality improvement are necessary.
- 35. Going from: :To
- 36. Focus shifting from craft to industry From Writing code To testing code From Fixing bugs To avoiding bugs From Implement features To enabling features From individual talent To process driven quality From Gold Plating To customer driven MVP
- 37. Yet another quote The amateur is learning about his problem [...], the professional [...] is learning about her profession - programming - and the problem being programmed is only one incidental step in her process of development. - The Psychology of Computer Programming, Gerald Weinberg, 1971.
- 38. The (somewhat) bad news: Change is faster than waterfall. BUT slower change than cowboy. Price to pay for quality and development scalability.
- 39. Conclusion Agile/Scrum != management practice Developers outnumber the rest. Developers have the power to make it work or to derail it. With great power comes ..
- 40. Great satisfaction And the rest too