The document summarizes an agile project meeting agenda and provides background information on agile methodologies. The agenda covers opening remarks, summaries of agile methods like Scrum and Extreme Programming, discussions on what projects are suitable for agile, the client perspective, and how to procure agile projects. Key topics include how agile focuses on collaboration, adaptability, and rapid delivery of working software over comprehensive documentation and rigid plans.
Agile Scrum Training (+ Kanban), Day 2 (2/2)Jens Wilke
Training materials for Agile Scrum. This presentation goes into more detail how to manage you product backlog, bug inflow and resolution and technical debt. Benefits of test driven development and continuous integration and live deployment are also discussed. Kanban is introduced in more detail, and the benefits of Scrum, Kanban and Scrum-Ban are compared.
This document discusses agile adoption in real world contexts. It emphasizes that agile adoption takes time, typically 3-5 years, and requires executive commitment. Common pitfalls include terminology abuse and an overreliance on user stories without considering other requirements. Automating processes through continuous integration is important for agile development. While agile principles have remained relevant, some argue the manifesto could be updated to reflect a greater focus on learning and customer empathy over just responding to change. The presentation concludes with questions about bringing change to companies, encouraging reluctant employees, and measuring agile maturity.
The document provides an agenda and overview of an introductory training on Agile and Scrum frameworks. It discusses key concepts like the Agile Manifesto, Scrum values and roles, and the differences between Scrum and traditional Waterfall methodologies. It also covers topics like product vision, role engagement, planning, estimation, and Scrum simulations.
Kanban For Software Engineering Apr 242Ross Lawley
The document discusses Kanban, a lean software engineering method focused on continuous flow and limiting work-in-progress. It describes Kanban's principles of limiting WIP, visualizing workflow, and pulling work. Kanban uses boards to visualize queues of work moving through stages, with WIP limits preventing overloading any stage. Pulling work only when downstream capacity allows keeps flow optimized.
Lean and Kanban-based Software DevelopmentTathagat Varma
This document discusses key concepts in Lean and Kanban-based software development. It defines Lean as focusing on maximizing customer value while minimizing waste. Key Lean principles outlined include identifying value, mapping the value stream, establishing flow and pull, and seeking perfection. Kanban is introduced as a scheduling system inspired by Toyota's just-in-time production to visualize workflow and limit work-in-progress. The document also discusses applying Lean concepts like value stream mapping, waste elimination, and 5S to software development processes and teams.
Agile & Lean & Kanban in the Real World - A Case StudyRussell Pannone
The document discusses Lean, Agile, and Kanban principles and methods. It provides an overview of Lean Agile approaches, the Kanban method, and a case study of an infrastructure team at a footwear company applying hybrid Lean Agile and Kanban principles. The team was previously using Scrum but found it did not fit their reactive, event-driven work. They decided to experiment with Kanban to better fit their work style and provide more visibility into tasks. The goal was to see if work-in-progress limits and measuring cycle time would help improve their effectiveness.
Agile Software Development Scrum Vs LeanAbdul Wahid
Scrum and Lean are both software development methodologies that aim to improve processes and productivity. Scrum focuses on self-organizing teams working in short sprints to develop products, while Lean emphasizes eliminating waste and respecting people. Both value continuous improvement, but Lean provides more engineering practices while Scrum is more of a framework. While their approaches differ, Scrum and Lean share fundamental values and can be used together by applying Lean principles within Scrum's flexible process.
The document discusses the principles and practices of extreme programming (XP), an agile software development methodology. It outlines 12 core practices of XP including planning games, small releases, simple design, testing, pair programming, and continuous integration. Benefits include frequent feedback, adapting to change, and delivering working software early. Challenges involve customer availability and determining appropriate levels of documentation and planning.
Agile Scrum Training (+ Kanban), Day 2 (2/2)Jens Wilke
Training materials for Agile Scrum. This presentation goes into more detail how to manage you product backlog, bug inflow and resolution and technical debt. Benefits of test driven development and continuous integration and live deployment are also discussed. Kanban is introduced in more detail, and the benefits of Scrum, Kanban and Scrum-Ban are compared.
This document discusses agile adoption in real world contexts. It emphasizes that agile adoption takes time, typically 3-5 years, and requires executive commitment. Common pitfalls include terminology abuse and an overreliance on user stories without considering other requirements. Automating processes through continuous integration is important for agile development. While agile principles have remained relevant, some argue the manifesto could be updated to reflect a greater focus on learning and customer empathy over just responding to change. The presentation concludes with questions about bringing change to companies, encouraging reluctant employees, and measuring agile maturity.
The document provides an agenda and overview of an introductory training on Agile and Scrum frameworks. It discusses key concepts like the Agile Manifesto, Scrum values and roles, and the differences between Scrum and traditional Waterfall methodologies. It also covers topics like product vision, role engagement, planning, estimation, and Scrum simulations.
Kanban For Software Engineering Apr 242Ross Lawley
The document discusses Kanban, a lean software engineering method focused on continuous flow and limiting work-in-progress. It describes Kanban's principles of limiting WIP, visualizing workflow, and pulling work. Kanban uses boards to visualize queues of work moving through stages, with WIP limits preventing overloading any stage. Pulling work only when downstream capacity allows keeps flow optimized.
Lean and Kanban-based Software DevelopmentTathagat Varma
This document discusses key concepts in Lean and Kanban-based software development. It defines Lean as focusing on maximizing customer value while minimizing waste. Key Lean principles outlined include identifying value, mapping the value stream, establishing flow and pull, and seeking perfection. Kanban is introduced as a scheduling system inspired by Toyota's just-in-time production to visualize workflow and limit work-in-progress. The document also discusses applying Lean concepts like value stream mapping, waste elimination, and 5S to software development processes and teams.
Agile & Lean & Kanban in the Real World - A Case StudyRussell Pannone
The document discusses Lean, Agile, and Kanban principles and methods. It provides an overview of Lean Agile approaches, the Kanban method, and a case study of an infrastructure team at a footwear company applying hybrid Lean Agile and Kanban principles. The team was previously using Scrum but found it did not fit their reactive, event-driven work. They decided to experiment with Kanban to better fit their work style and provide more visibility into tasks. The goal was to see if work-in-progress limits and measuring cycle time would help improve their effectiveness.
Agile Software Development Scrum Vs LeanAbdul Wahid
Scrum and Lean are both software development methodologies that aim to improve processes and productivity. Scrum focuses on self-organizing teams working in short sprints to develop products, while Lean emphasizes eliminating waste and respecting people. Both value continuous improvement, but Lean provides more engineering practices while Scrum is more of a framework. While their approaches differ, Scrum and Lean share fundamental values and can be used together by applying Lean principles within Scrum's flexible process.
The document discusses the principles and practices of extreme programming (XP), an agile software development methodology. It outlines 12 core practices of XP including planning games, small releases, simple design, testing, pair programming, and continuous integration. Benefits include frequent feedback, adapting to change, and delivering working software early. Challenges involve customer availability and determining appropriate levels of documentation and planning.
This document provides an overview of adopting an agile Scrum framework. It begins with introducing the presenter and their experience in agile project delivery. It then summarizes the traditional waterfall approach and poses questions about its effectiveness. The bulk of the document outlines the Scrum framework and provides tips for implementation, including establishing objectives, selecting pilot projects, customizing processes, training teams, and adopting in stages. It emphasizes treating the implementation as a formal project and allowing time for the cultural changes required.
This document provides an overview of Scrum, an agile framework for project management. It describes key Scrum roles like the Product Owner, Scrum Master, and self-organizing team. It outlines common Scrum events like sprint planning, daily stand-ups, sprint reviews, and retrospectives. It also explains main Scrum artifacts like the product backlog, sprint backlog, and burn down charts that are used to track work. The document aims to explain the basic concepts, roles, events, and artifacts that make up the Scrum framework.
The document provides an overview of the Agile Scrum process. It describes traditional waterfall methodologies and how Agile and Scrum differ by being more iterative, collaborative with stakeholders, and able to adapt to changes. The Scrum framework involves three main roles - Product Owner, Scrum Master, and Team. It also describes the four main Scrum ceremonies - Sprint Planning Meeting, Daily Standup, Sprint Review, and Sprint Retrospective - as well as the typical artifacts like Product Backlog and Sprint Backlog.
There are a lot of choices and alternatives for getting started with Agile. It can be confusing. This talk will give you a brief guided tour of Agile methodologies so that you have some understanding of how they are similar and how they differ. We'll cover some of the history of iterative development and waterfall as well as the Agile Manifesto to provide context. At the end of this, you will have an understanding of key principles and the Agile landscape.
Please email me if you would like a download.
Waterfall vs agile approach scrum framework and best practices in software d...Tayfun Bilsel
The document discusses various topics related to software development approaches, including:
1. The differences between waterfall and agile approaches. Agile focuses on iterative development and responding to change over extensive planning.
2. Common problems with traditional project management like late delivery and budget overruns.
3. An overview of the Scrum framework, including roles, artifacts, ceremonies, and best practices. Scrum uses short iterations called sprints to iteratively deliver working software.
4. Recommendations to customize Scrum by incorporating elements of eXtreme Programming (XP) and lean principles to eliminate waste and continually improve processes.
This document provides an introduction to Lean, Agile, Scrum, and XP. It defines Lean as focusing on identifying value and optimizing processes. Agile emphasizes responding quickly to change through principles like valuing individuals, working software, and customer collaboration. Scrum is a framework that uses short cycles, daily stand-ups, and product backlogs to organize complex work. XP includes practices like pair programming, test-driven development, and collective code ownership.
Presentation I gave to the Chicago ACM about Lean Software Development. Full audio can be found here:
https://soundcloud.com/griffinc/intro-to-lean-software
Lean software engineering emphasizes continuous delivery of high quality applications. Ken Pugh explains the principles and practices that form the basis of lean software development―concentrating on developing a continuous flow by eliminating delays and loopbacks; delivering quickly by developing in small batches; emphasizing high quality which decreases delays due to defect repair; making policies, process and progress transparent; optimizing the whole rather than individual steps; and becoming more efficient by decreasing waste. Ken describes lean’s emphasis on cycle time, rather than resource utilization, and demonstrates the value stream map which helps you visualize the development cycle flow to identify bottlenecks. He explores the differences between push and pull flow, describes how lean thinking shows up in agile processes including Scrum and Extreme Programming, and discusses how lean can be applied to the entire workflow—not just the development portion. Ken concludes with a discussion of how you can begin your lean transformation.
Dimitri Ponomareff is an experienced coach, project manager, and facilitator. He has extensive experience coaching and training teams at many large organizations. Dimitri is passionate about sharing his knowledge of Agile methodologies like Scrum, XP, and Kanban to help teams improve. The document provides an overview of these Agile approaches including their origins and key principles.
This document provides an introduction to Agile and Scrum. It discusses the principles of Agile, including the Agile Manifesto. Scrum is presented as an Agile framework consisting of roles, ceremonies, and artifacts. The roles of Product Owner, Scrum Master, and Engineering Team are defined. Ceremonies like Sprint Planning, Daily Scrum, Sprint Review and Retrospective are explained. Artifacts such as Product Backlog, Sprint Backlog and Burn Down Chart are also summarized. User stories, estimation techniques, and definitions of done are covered as part of requirements and planning in Scrum.
When I needed to do presentations of Scrum to executives and students, I started to look for existing ones. Most presentations I found were very good for detailed presentations or training. But what I was looking for was a presentation I could give in less than 15 minutes (or more if I wanted). Most of them also contained out dated content. For example, the latest changes in the Scrum framework were not present and what has been removed was still there.
UPDATE VERSION : https://www.slideshare.net/pmengal/scrum-in-ten-slides-v20-2018
Introduction to Agile and Lean Software DevelopmentThanh Nguyen
The document provides an introduction to agile and lean software development. It discusses traditional vs agile development, defines agile as iterative and incremental using a plan-do-check-act approach with empowered cross-functional teams relying on automation. It covers the agile manifesto, principles and core practices including short iterations, deming's PDCA model, and the agile software development lifecycle. Lean concepts are introduced such as eliminating waste, amplifying learning, deciding late and delivering fast to empower teams and build integrity.
The document discusses several agile software development frameworks including the Agile Manifesto, eXtreme Programming (XP), Scrum, and hybrid methods. The Agile Manifesto values individuals, working software, customer collaboration, and responding to change. XP focuses on communication, simplicity, feedback, and courage. Key practices include planning game, small releases, refactoring, and collective code ownership. Scrum emphasizes empirical process control, self-organizing cross-functional teams, and delivering working software frequently in short iterations. Hybrid methods combine different agile approaches to suit various project needs.
The document provides an introduction to Agile project management. It discusses key concepts like Scrum, an Agile methodology. Scrum uses short "sprints" to incrementally deliver working software. Meetings like daily stand-ups and sprint planning and retrospectives help coordinate work. The roles of product owner, Scrum master, and self-organizing cross-functional teams are also outlined. The document emphasizes delivering value to customers through iterative development and continuous improvement.
Feedback loops - the second way towards the world of DevOpsTapio Rautonen
The three ways define a philosophical journey to an unfinished world of IT development. Amplifying feedback loops, the second way, is about shortening and amplifying any bottlenecks preventing feedback to close a full circuit of continual improvement.
The document provides an overview of the waterfall model and agile methodologies for software development projects. It discusses:
- The linear sequential phases of the waterfall model and when it is suitable.
- Issues with the waterfall model like inability to handle changes and lack of testing throughout.
- Benefits of agile like ability to adapt to changes, early delivery of working software, and improved success rates.
- Key aspects of the Scrum agile framework like sprints, daily stand-ups, and product backlogs.
- Differences in how development costs are treated as capital expenditures or operating expenses between waterfall, agile, and cloud-based models.
This document discusses DevOps feedback loops and the importance of closing the loop between development and operations. It provides examples of where feedback comes from in operations, including from people and machines, and where feedback needs to go in development, such as to developers and development systems. The key message is that closing the feedback loop through continuous feedback is critical for DevOps in order to optimize software development and address issues quickly before they become bigger problems.
This document provides an overview of agile and lean principles for software development. It discusses concepts like the agile manifesto, scrum, extreme programming (XP), kanban, and lean software development. The document aims to introduce audiences to fundamental agile and lean concepts and encourage them to continue learning through references and future events.
This document provides an overview of adopting an agile Scrum framework. It begins with introducing the presenter and their experience in agile project delivery. It then summarizes the traditional waterfall approach and poses questions about its effectiveness. The bulk of the document outlines the Scrum framework and provides tips for implementation, including establishing objectives, selecting pilot projects, customizing processes, training teams, and adopting in stages. It emphasizes treating the implementation as a formal project and allowing time for the cultural changes required.
This document provides an overview of Scrum, an agile framework for project management. It describes key Scrum roles like the Product Owner, Scrum Master, and self-organizing team. It outlines common Scrum events like sprint planning, daily stand-ups, sprint reviews, and retrospectives. It also explains main Scrum artifacts like the product backlog, sprint backlog, and burn down charts that are used to track work. The document aims to explain the basic concepts, roles, events, and artifacts that make up the Scrum framework.
The document provides an overview of the Agile Scrum process. It describes traditional waterfall methodologies and how Agile and Scrum differ by being more iterative, collaborative with stakeholders, and able to adapt to changes. The Scrum framework involves three main roles - Product Owner, Scrum Master, and Team. It also describes the four main Scrum ceremonies - Sprint Planning Meeting, Daily Standup, Sprint Review, and Sprint Retrospective - as well as the typical artifacts like Product Backlog and Sprint Backlog.
There are a lot of choices and alternatives for getting started with Agile. It can be confusing. This talk will give you a brief guided tour of Agile methodologies so that you have some understanding of how they are similar and how they differ. We'll cover some of the history of iterative development and waterfall as well as the Agile Manifesto to provide context. At the end of this, you will have an understanding of key principles and the Agile landscape.
Please email me if you would like a download.
Waterfall vs agile approach scrum framework and best practices in software d...Tayfun Bilsel
The document discusses various topics related to software development approaches, including:
1. The differences between waterfall and agile approaches. Agile focuses on iterative development and responding to change over extensive planning.
2. Common problems with traditional project management like late delivery and budget overruns.
3. An overview of the Scrum framework, including roles, artifacts, ceremonies, and best practices. Scrum uses short iterations called sprints to iteratively deliver working software.
4. Recommendations to customize Scrum by incorporating elements of eXtreme Programming (XP) and lean principles to eliminate waste and continually improve processes.
This document provides an introduction to Lean, Agile, Scrum, and XP. It defines Lean as focusing on identifying value and optimizing processes. Agile emphasizes responding quickly to change through principles like valuing individuals, working software, and customer collaboration. Scrum is a framework that uses short cycles, daily stand-ups, and product backlogs to organize complex work. XP includes practices like pair programming, test-driven development, and collective code ownership.
Presentation I gave to the Chicago ACM about Lean Software Development. Full audio can be found here:
https://soundcloud.com/griffinc/intro-to-lean-software
Lean software engineering emphasizes continuous delivery of high quality applications. Ken Pugh explains the principles and practices that form the basis of lean software development―concentrating on developing a continuous flow by eliminating delays and loopbacks; delivering quickly by developing in small batches; emphasizing high quality which decreases delays due to defect repair; making policies, process and progress transparent; optimizing the whole rather than individual steps; and becoming more efficient by decreasing waste. Ken describes lean’s emphasis on cycle time, rather than resource utilization, and demonstrates the value stream map which helps you visualize the development cycle flow to identify bottlenecks. He explores the differences between push and pull flow, describes how lean thinking shows up in agile processes including Scrum and Extreme Programming, and discusses how lean can be applied to the entire workflow—not just the development portion. Ken concludes with a discussion of how you can begin your lean transformation.
Dimitri Ponomareff is an experienced coach, project manager, and facilitator. He has extensive experience coaching and training teams at many large organizations. Dimitri is passionate about sharing his knowledge of Agile methodologies like Scrum, XP, and Kanban to help teams improve. The document provides an overview of these Agile approaches including their origins and key principles.
This document provides an introduction to Agile and Scrum. It discusses the principles of Agile, including the Agile Manifesto. Scrum is presented as an Agile framework consisting of roles, ceremonies, and artifacts. The roles of Product Owner, Scrum Master, and Engineering Team are defined. Ceremonies like Sprint Planning, Daily Scrum, Sprint Review and Retrospective are explained. Artifacts such as Product Backlog, Sprint Backlog and Burn Down Chart are also summarized. User stories, estimation techniques, and definitions of done are covered as part of requirements and planning in Scrum.
When I needed to do presentations of Scrum to executives and students, I started to look for existing ones. Most presentations I found were very good for detailed presentations or training. But what I was looking for was a presentation I could give in less than 15 minutes (or more if I wanted). Most of them also contained out dated content. For example, the latest changes in the Scrum framework were not present and what has been removed was still there.
UPDATE VERSION : https://www.slideshare.net/pmengal/scrum-in-ten-slides-v20-2018
Introduction to Agile and Lean Software DevelopmentThanh Nguyen
The document provides an introduction to agile and lean software development. It discusses traditional vs agile development, defines agile as iterative and incremental using a plan-do-check-act approach with empowered cross-functional teams relying on automation. It covers the agile manifesto, principles and core practices including short iterations, deming's PDCA model, and the agile software development lifecycle. Lean concepts are introduced such as eliminating waste, amplifying learning, deciding late and delivering fast to empower teams and build integrity.
The document discusses several agile software development frameworks including the Agile Manifesto, eXtreme Programming (XP), Scrum, and hybrid methods. The Agile Manifesto values individuals, working software, customer collaboration, and responding to change. XP focuses on communication, simplicity, feedback, and courage. Key practices include planning game, small releases, refactoring, and collective code ownership. Scrum emphasizes empirical process control, self-organizing cross-functional teams, and delivering working software frequently in short iterations. Hybrid methods combine different agile approaches to suit various project needs.
The document provides an introduction to Agile project management. It discusses key concepts like Scrum, an Agile methodology. Scrum uses short "sprints" to incrementally deliver working software. Meetings like daily stand-ups and sprint planning and retrospectives help coordinate work. The roles of product owner, Scrum master, and self-organizing cross-functional teams are also outlined. The document emphasizes delivering value to customers through iterative development and continuous improvement.
Feedback loops - the second way towards the world of DevOpsTapio Rautonen
The three ways define a philosophical journey to an unfinished world of IT development. Amplifying feedback loops, the second way, is about shortening and amplifying any bottlenecks preventing feedback to close a full circuit of continual improvement.
The document provides an overview of the waterfall model and agile methodologies for software development projects. It discusses:
- The linear sequential phases of the waterfall model and when it is suitable.
- Issues with the waterfall model like inability to handle changes and lack of testing throughout.
- Benefits of agile like ability to adapt to changes, early delivery of working software, and improved success rates.
- Key aspects of the Scrum agile framework like sprints, daily stand-ups, and product backlogs.
- Differences in how development costs are treated as capital expenditures or operating expenses between waterfall, agile, and cloud-based models.
This document discusses DevOps feedback loops and the importance of closing the loop between development and operations. It provides examples of where feedback comes from in operations, including from people and machines, and where feedback needs to go in development, such as to developers and development systems. The key message is that closing the feedback loop through continuous feedback is critical for DevOps in order to optimize software development and address issues quickly before they become bigger problems.
This document provides an overview of agile and lean principles for software development. It discusses concepts like the agile manifesto, scrum, extreme programming (XP), kanban, and lean software development. The document aims to introduce audiences to fundamental agile and lean concepts and encourage them to continue learning through references and future events.
What content strategists need to demand from the CMS guysPerttu Tolvanen
This talk is a brutally honest confession of a CMS expert and information architect about the state of Web CMS market today and how the rise of content and mobile devices is changing what we should expect from our Web CMS. The presentation will review the most important features of CMSs that are important for content strategists and what should content strategists demand from the CMS guys.
Web CMS vs. Custom applications - different approachesPerttu Tolvanen
This presentation offers you examples and tips in choosing whether to build your custom application on top of Web CMS or to do it as a stand-alone custom application (built using some framework).
Turbocharging Drupal Syndication with Node.jsExove
You can get far by caching Drupal's content feeds. There are a lot of caching layers available. But when you need a bit of intelligence to your caching layer, drowning deep into the world of Varnish VCL configurations isn't the only option.
We went from trying to optimize Drupal's ability to deliver JSON-feeds out with MongoDB field storage and SOLR backed Views with a Varnish caching layer to a performance-optimized standalone Node.JS/MongoDB stack.
In this presentation we'll show a real-world case, where Drupal's content is optimized and indexed to MongoDB and then delivered out in JSON with astonishing speeds with a very simple Node.JS layer.
The setup serves most of the video content to Finland's biggest media corporation, Sanoma. It's the sole source of video content to their online TV service, Ruutu.fi.
The same setup could be used for serving as a backend for high-volume Javascript applications, replicating a lot of content around the world or optimizing the UX of a Drupal site by adding super-fast asynchronous APIs.
In the presentation we'll look at the architecture, the development phases, performance optimizations and lessons learnt in storing complicated data structures to Drupal and MongoDB. We'll also look at the current development efforts in getting the system in shape for Drupal 8 upgrade in the near future.
The session video (slides with audio) can be viewed in YouTube: https://www.youtube.com/watch?v=VmTd6hITVVA
This document outlines the agenda for an event hosted by Exove, a Northern European company specializing in open source web services. The agenda includes presentations on mobile trends, eCommerce trends, open source trends, and marketing automation trends. Speakers will cover topics like the growth of eCommerce and mobile commerce, the impact on physical retail stores, emerging mobile and eCommerce technologies, and how open source platforms and tools are evolving. The event aims to provide insights into key digital trends and recommendations for how companies can leverage these trends in their business. Networking breaks involving glögi are also included in the agenda.
Language support in searching Drupal with SOLR - Drupalcamp London 2013Exove
In this presentation we'll go through the needed contrib modules, as well as the resources and special cofigurations needed for SOLR to not only index, but also find multi-language content.
This document outlines an email marketing bootcamp presented by Michael Reynolds. It discusses best practices for email marketing, including using email to increase consumer spending by 138% and 91% of consumers using email daily. It provides tips for understanding buyers, setting goals, growing email lists, creating high-value content, segmenting lists, and writing subject lines. The presentation emphasizes keeping emails short, focused on one call-to-action, and sending valuable content to engage subscribers.
This time AppTalk will focus on the everyday question of web applications vs hybrid applications vs native mobile applications. We'll provide guidance in making the business decision between these approaches. This will be presented through practical real-life cases. The focus will be on mobile applications rather than games.
Agile and its impact to Project Management 022218.pptxPerumalPitchandi
This document provides an introduction to Agile project management. It discusses the history and evolution of Agile, including the Agile Manifesto. It then describes several common Agile methodologies like Scrum, Kanban, and Extreme Programming. The document also introduces key Agile concepts like iterative development, user stories, and velocity. It discusses how project scheduling, cost estimation, and DevOps relate to Agile. Finally, it provides an overview of the Scaled Agile Framework (SAFe) for implementing Agile at an enterprise level.
Software Development Process Models (SCRUM Methodology)Muhammad Ahmed
This document provides an overview of software process models and Scrum methodology. It defines a software process model as a description of the sequence of activities carried out in a software engineering project. The key activities include specification, design & implementation, validation, and evolution. Scrum is introduced as an agile software development framework. It utilizes short development cycles called sprints, daily stand-up meetings, product backlogs to track requirements, and emphasizes self-organizing teams and adaptive planning. The benefits of Scrum are discussed as improved productivity, quality, and ability to manage changing requirements.
This document provides an overview of agile project management. It discusses the history and origins of agile, including the Agile Manifesto. The Scrum methodology is described, including its events, artifacts, and team roles. The document also addresses how project managers fit into agile projects and considerations for determining if agile is appropriate. The presenter is introduced as an experienced project manager seeking to educate others on agile principles and practices.
The document discusses Agile software development methods. It defines Agile as iterative development methods that promote adaptive planning, evolutionary development, rapid response to change, and value interactions and collaboration over processes and tools. It describes common Agile frameworks like Scrum, which uses sprints, daily stand-ups, and artifacts like product backlogs to help teams self-organize and deliver working software frequently. The document contrasts traditional waterfall methods with Agile's emphasis on adaptability, collaboration, and rapid delivery of working software.
A compilation of the absolute basics for those who want to know about Agile Methodology with some insights on Scrum. The idea is to give enough to fuel the curiosity to learn more. It might not interest one of he / she is an Agile guru but may I ask for your review / comments / suggestions. I'd love to hear from you all...
This document provides an overview of Agile and Scrum methodologies. It describes the iterative incremental model and compares it to the waterfall model. The key aspects of Agile include iterative development, early delivery of working software, collaboration between business and developers, self-organizing teams, and face-to-face communication. Scrum is then introduced as a framework for implementing Agile. The core Scrum roles, events, artifacts, user stories, estimation techniques, and burn down charts are defined and explained at a high level.
This document provides an overview of Agile methodology and SCRUM. It discusses the principles of Agile, including its emphasis on collaboration, adaptability, and delivering working software frequently. It then describes SCRUM in more detail, covering the roles of Product Owner, Scrum Master, and Team. The key SCRUM artifacts like Product Backlog, Sprint Backlog, and Burn Down Chart are explained. It also outlines the core SCRUM ceremonies of Sprint Planning, Daily Scrum, Sprint Review, and Retrospective. The document concludes by discussing challenges of adopting SCRUM and provides tips for SCRUM Team members.
How to Manage Marketing Projects and People (Without Going Insane)LeadMD
Marketing departments face the perfect storm of issues: too-small budgets leading to too-few people with huge financial return expectations. To keep shifting priorities in check, marketers need to adopt an agile framework, like Scrum, to bring visibility -- and productivity -- to the forefront.
The document provides an overview of Agile software development using Scrum. It describes Scrum as an Agile framework that focuses on delivering business value through short iterative development cycles called sprints. Key aspects of Scrum include self-organizing cross-functional teams, prioritized product backlogs maintained by a Product Owner, and regular sprint planning, daily standup, review and retrospective meetings facilitated by a Scrum Master.
Working with Agile technologies and SCRUMAndrea Tino
The document provides an overview of Scrum and Agile methodologies for software development. It discusses key Scrum concepts like roles, events, artifacts, and tools used in the Scrum process. The roles in Scrum include the Product Owner, Development Team, and Scrum Master. Events include the Sprint, Sprint Planning meeting, Daily Scrum meeting, and Sprint Review meeting. Artifacts include Product and Sprint Backlogs, as well as Deliverables and Bugs. Tools discussed include Kanban boards, code review tools, changesets, and Microsoft's unit testing framework.
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.
This document provides an overview of different software development processes including the waterfall model, iterative model, Rational Unified Process (RUP), and Agile Development Process (ADP). It describes the key aspects of each process including phases, roles, artifacts, and ceremonies. Specifically, it provides detailed explanations of Scrum, an agile methodology, including Scrum roles like Product Owner and Scrum Master, ceremonies like the Daily Scrum, and artifacts like the Product Backlog and Sprint Backlog. The document concludes with references for further information.
The Agile Process - Taming Your Process To Work For YouNowell Strite
The document discusses the Agile process and how it aims to address problems with traditional waterfall approaches. It summarizes the key aspects of Agile including:
- Focusing on iterative delivery of working software over comprehensive documentation.
- Emphasizing collaboration and responsiveness to change over strict contracts and plans.
- Using sprints, daily stand-ups, and retrospectives to keep projects on track and continuously improve.
It then provides more details on how Scrum, one flavor of Agile, structures teams, roles, and the sprint life cycle to help deliver working software in a transparent and adaptive manner.
This document provides an overview of Scrum and its key concepts. It defines the waterfall and agile models of software development. Scrum is described as an agile method that uses cross-functional teams, product backlogs, sprints, daily stand-ups, and sprint reviews. Key Scrum roles like the Product Owner and Scrum Master are explained. The document also discusses estimating techniques, burndown charts, and how Scrum compares to other agile frameworks.
Agile Project Management in a Waterfall World: Managing Sprints with Predicti...John Carter
This document provides an overview of applying agile project management practices to hardware and systems development. It begins with biographies of the authors and case studies where agile methods improved software development. It then discusses challenges applying agile to hardware with long lead times. Key practices discussed include using short intervals with feedback, translating user stories and burn-downs to hardware, and managing projects with boundary conditions and out of bounds processes. The document provides examples and outlines adapting scrum practices like sprints, planning and retrospectives for hardware development.
Overview of SCRUM development process. I put this together to present to my company/group.
Most slides are "borrowed" from Alan Shalloway's presentation.
Post-agile approaches - agile for the real world and how to avoid agile failureYuval Yeret
The document discusses various Agile and Lean concepts and frameworks. It begins with an overview of Agile principles and the Agile Manifesto. It then discusses some of the challenges with implementing Agile approaches in reality, including in large legacy organizations. It introduces several frameworks for implementing Agile at scale, including Kanban, Scrum, SAFe. It analyzes the strengths, weaknesses, opportunities and threats of each approach. It also discusses ways the different approaches can be combined or evolved to better address real-world challenges. The document advocates for focusing on principles over practices and evolving approaches over time based on learning and experimentation.
Professional Project Manager Should Be Proficient in AgileNitor
This document discusses the benefits of being proficient in Agile project management. It begins with an introduction of the presenter and their experience in IT projects. It then contrasts the Waterfall and Agile approaches. Waterfall involves detailed upfront planning while Agile values adaptability and frequent delivery of working software. The document emphasizes that due to global competition, it is not enough to simply complete a project but to exceed expectations and adapt quickly. It provides examples of how companies like Nitor have seen success through Agile methods and discusses key Agile principles like small batch sizes and effective communication.
Rich Mironov's keynote for one-day agile workshop. Intro to agile development and agile organizations, tools, impact on whole organization, product management and product planning. Co-sponsored by AccuRev, Coverity, Electric Cloud, Enthiosys, Rally and Agile Journal.
Similar to Agile Web Development, Exove seminar August 15th, 2013 (20)
Data security in the age of GDPR – most common data security problemsExove
This document discusses common data security problems that can result in fines under the GDPR and how to address them, including:
1) Accidental disclosure of data, such as unauthenticated access to files or APIs, can be avoided by requiring authentication for all data access and properly configuring access settings.
2) Lacking internal access controls allows users to access too much information; these issues can be fixed by implementing and enforcing internal access controls.
3) Targeted attacks by professional criminals are difficult to prevent, but risks can be reduced by limiting data and system access, employing automated checks, and only allowing verified file changes.
Provisioning infrastructure to AWS using Terraform – ExoveExove
This document provides an overview of using Terraform to provision infrastructure on AWS. It discusses how Terraform allows defining infrastructure as code through configuration files, enabling reliable and repeatable deployments. Key points include:
- Terraform can provision AWS services like Lambda, DynamoDB, API Gateway to build a serverless REST API on AWS.
- Managing infrastructure through graphical interfaces becomes complex and error-prone for non-trivial configurations.
- Terraform addresses this by defining resources and dependencies through configuration files, then deploying the necessary infrastructure.
- This allows defining a standard structure for environments like development, test, and production through variables and modules.
This document discusses custom blocks in the Gutenberg editor in WordPress. It provides basics about WordPress and discusses the old editor versus the new Gutenberg editor. It then explains what Advanced Custom Fields (ACF) is and how it can be used to create custom blocks for Gutenberg. It provides a demo of how to register a custom block, create fields for it in ACF, and build a template to display the block with the custom fields on a page.
Robot Framework is an open source test automation framework that can be used to test web, desktop, and mobile applications. It uses a keyword-driven design and has a modular architecture that makes it easy to extend with custom test libraries. Some benefits include being highly reusable, accessible for beginners, and having powerful logging capabilities. However, it does not support while loops or nested for loops, and working with non-string data types can be complicated. The framework operates independently of the system under test and uses test suites made up of test cases that can each be in their own namespace. Custom keywords, variables, and extensions are usually stored separately.
Jenkins is a tool used for continuous integration and automation that can build, test, and deploy software. Visual regression testing involves comparing screenshots of a website between builds to detect unwanted visual changes. The document describes a case study where a screenshot comparison tool was built to run within Jenkins, automatically collecting screenshots of a site, comparing galleries of screenshots between test runs, and reporting any visual differences found.
This document discusses using Next.js and a headless CMS to build server-side rendered React apps that improve SEO. Next.js allows building server-side rendered React apps using server-side rendering for better SEO than traditional single-page apps. A headless CMS like Contentful manages just the content without the front-end, providing an API for a separate front-end app like one built with Next.js to retrieve and display the content.
WebSockets allow for full-duplex communication between a web browser and server over a single TCP connection. The Bravo Dashboard was mainly developed for Exove's internal use to show employee presence, absences, and other useful daily data. WebSockets were used in the Bravo Dashboard out of curiosity and because they allow for easy and quick sending and receiving of data in real-time, such as when editing results in the dashboard. The Socket.io library enables the use of WebSockets in the Bravo Dashboard and provides useful methods like "On", "Off", and "Emit" for listening and sending data between the frontend and backend.
Exove's CTO Kalle Varisvirta shares his insights on diversity in recruitment. Kalle has many years of experience in recruiting software developers. Exove is a company with a diverse & inclusive workforce – and we are very proud of it! Read more about us: exove.com.
Kalle was one of the speakers in the Agile Search HR meetup on 28 March and he gave this presentation there.
Mitä saavutettavuusdirektiivi pitää sisälläänExove
Mitä saavutettavuusdirektiivi pitää sisällään, Kimmo Sääskilahti, Annanpura
Kimmo Sääskilahden puheenvuoro Exoven seminaarissa "Saavutettavuus ja käytettävyys verkkopalveluissa" 15.2.2019
This document discusses various options for creating landing pages in Drupal 8, including paragraphs, Entity Construction Kit (ECK), Display Suite, Field Layout, Panels, and others. Paragraphs allow for structured content chunks that can be reordered and come in types like accordions and galleries. ECK provides reusable entity types for content. Display Suite extends display options and offers custom layouts. Field Layout adds layout capabilities to the field UI in Drupal core. Panels is a powerful but complex system for custom layouts using blocks or fields. Planning and a focus on customer needs are emphasized when choosing an approach.
The document provides an overview of GDPR requirements for developers working with content management systems (CMS). It discusses key GDPR concepts like data controllers, processors and individual rights. It notes CMS pose specific challenges around structured vs unstructured data, content, analytics, logs and digital marketing. The document emphasizes existing systems may not fully document where personal data is stored and retained, and full deletion may not be technically possible. Thorough auditing of storage is needed to ensure compliance.
Life with digital services after GDPR by Kalle Varisvirta, Exove
Seminar Exove and Bird & Bird 26th April 2018: GDPR tulee - mitä tapahtuu h-hetken jälkeen
Exove Extends keynote on Dec 13th, 2017
Developing truly personalised experiences by Simon Chapman from Acquia
Acquia powers some of the world’s biggest and most well-known websites, delivering personalised content whatever the channel, location or device. We’ll take a deep dive into the technologies and components of the Acquia platform and explore traditional development methods versus headless or decoupled architectures. We’ll outline the benefits of using modern JS frameworks whilst delivering personalised experiences that capture your customers ‘in the moment’, which ultimately can be measured through analytics...and as your customer data grows, we’ll talk about how this ‘big data’ can be used to drive reporting, customer journeys and the ‘next best action’.
The document summarizes a seminar on customer experience and personalization held by Exove and Acquia in 2017. The agenda included a welcome by the CEO of Exove, a presentation on taking customers on a 1-1 journey by a Senior Solutions Architect at Acquia, and a presentation on service design and personalization by the Service Design Lead at Exove Design. The document provides details of the presentations and discussions around understanding customers, their journeys, and driving engagement through personalization.
Adventures In Programmatic Branding – How To Design With Algorithms And How T...Exove
The document discusses metaballs and isosurfaces as a way to programmatically generate organic-looking branding. Metaballs are a type of isosurface defined by mathematical functions that can be iterated over pixels to create shapes. While algorithms can generate results, including the client and designer in the process ensures the output aligns with the goals.
Generating privacy-protected synthetic data using Secludy and MilvusZilliz
During this demo, the founders of Secludy will demonstrate how their system utilizes Milvus to store and manipulate embeddings for generating privacy-protected synthetic data. Their approach not only maintains the confidentiality of the original data but also enhances the utility and scalability of LLMs under privacy constraints. Attendees, including machine learning engineers, data scientists, and data managers, will witness first-hand how Secludy's integration with Milvus empowers organizations to harness the power of LLMs securely and efficiently.
Fueling AI with Great Data with Airbyte WebinarZilliz
This talk will focus on how to collect data from a variety of sources, leveraging this data for RAG and other GenAI use cases, and finally charting your course to productionalization.
Connector Corner: Seamlessly power UiPath Apps, GenAI with prebuilt connectorsDianaGray10
Join us to learn how UiPath Apps can directly and easily interact with prebuilt connectors via Integration Service--including Salesforce, ServiceNow, Open GenAI, and more.
The best part is you can achieve this without building a custom workflow! Say goodbye to the hassle of using separate automations to call APIs. By seamlessly integrating within App Studio, you can now easily streamline your workflow, while gaining direct access to our Connector Catalog of popular applications.
We’ll discuss and demo the benefits of UiPath Apps and connectors including:
Creating a compelling user experience for any software, without the limitations of APIs.
Accelerating the app creation process, saving time and effort
Enjoying high-performance CRUD (create, read, update, delete) operations, for
seamless data management.
Speakers:
Russell Alfeche, Technology Leader, RPA at qBotic and UiPath MVP
Charlie Greenberg, host
Digital Banking in the Cloud: How Citizens Bank Unlocked Their MainframePrecisely
Inconsistent user experience and siloed data, high costs, and changing customer expectations – Citizens Bank was experiencing these challenges while it was attempting to deliver a superior digital banking experience for its clients. Its core banking applications run on the mainframe and Citizens was using legacy utilities to get the critical mainframe data to feed customer-facing channels, like call centers, web, and mobile. Ultimately, this led to higher operating costs (MIPS), delayed response times, and longer time to market.
Ever-changing customer expectations demand more modern digital experiences, and the bank needed to find a solution that could provide real-time data to its customer channels with low latency and operating costs. Join this session to learn how Citizens is leveraging Precisely to replicate mainframe data to its customer channels and deliver on their “modern digital bank” experiences.
In the realm of cybersecurity, offensive security practices act as a critical shield. By simulating real-world attacks in a controlled environment, these techniques expose vulnerabilities before malicious actors can exploit them. This proactive approach allows manufacturers to identify and fix weaknesses, significantly enhancing system security.
This presentation delves into the development of a system designed to mimic Galileo's Open Service signal using software-defined radio (SDR) technology. We'll begin with a foundational overview of both Global Navigation Satellite Systems (GNSS) and the intricacies of digital signal processing.
The presentation culminates in a live demonstration. We'll showcase the manipulation of Galileo's Open Service pilot signal, simulating an attack on various software and hardware systems. This practical demonstration serves to highlight the potential consequences of unaddressed vulnerabilities, emphasizing the importance of offensive security practices in safeguarding critical infrastructure.
Skybuffer SAM4U tool for SAP license adoptionTatiana Kojar
Manage and optimize your license adoption and consumption with SAM4U, an SAP free customer software asset management tool.
SAM4U, an SAP complimentary software asset management tool for customers, delivers a detailed and well-structured overview of license inventory and usage with a user-friendly interface. We offer a hosted, cost-effective, and performance-optimized SAM4U setup in the Skybuffer Cloud environment. You retain ownership of the system and data, while we manage the ABAP 7.58 infrastructure, ensuring fixed Total Cost of Ownership (TCO) and exceptional services through the SAP Fiori interface.
AppSec PNW: Android and iOS Application Security with MobSFAjin Abraham
Mobile Security Framework - MobSF is a free and open source automated mobile application security testing environment designed to help security engineers, researchers, developers, and penetration testers to identify security vulnerabilities, malicious behaviours and privacy concerns in mobile applications using static and dynamic analysis. It supports all the popular mobile application binaries and source code formats built for Android and iOS devices. In addition to automated security assessment, it also offers an interactive testing environment to build and execute scenario based test/fuzz cases against the application.
This talk covers:
Using MobSF for static analysis of mobile applications.
Interactive dynamic security assessment of Android and iOS applications.
Solving Mobile app CTF challenges.
Reverse engineering and runtime analysis of Mobile malware.
How to shift left and integrate MobSF/mobsfscan SAST and DAST in your build pipeline.
HCL Notes and Domino License Cost Reduction in the World of DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-and-domino-license-cost-reduction-in-the-world-of-dlau/
The introduction of DLAU and the CCB & CCX licensing model caused quite a stir in the HCL community. As a Notes and Domino customer, you may have faced challenges with unexpected user counts and license costs. You probably have questions on how this new licensing approach works and how to benefit from it. Most importantly, you likely have budget constraints and want to save money where possible. Don’t worry, we can help with all of this!
We’ll show you how to fix common misconfigurations that cause higher-than-expected user counts, and how to identify accounts which you can deactivate to save money. There are also frequent patterns that can cause unnecessary cost, like using a person document instead of a mail-in for shared mailboxes. We’ll provide examples and solutions for those as well. And naturally we’ll explain the new licensing model.
Join HCL Ambassador Marc Thomas in this webinar with a special guest appearance from Franz Walder. It will give you the tools and know-how to stay on top of what is going on with Domino licensing. You will be able lower your cost through an optimized configuration and keep it low going forward.
These topics will be covered
- Reducing license cost by finding and fixing misconfigurations and superfluous accounts
- How do CCB and CCX licenses really work?
- Understanding the DLAU tool and how to best utilize it
- Tips for common problem areas, like team mailboxes, functional/test users, etc
- Practical examples and best practices to implement right away
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/how-axelera-ai-uses-digital-compute-in-memory-to-deliver-fast-and-energy-efficient-computer-vision-a-presentation-from-axelera-ai/
Bram Verhoef, Head of Machine Learning at Axelera AI, presents the “How Axelera AI Uses Digital Compute-in-memory to Deliver Fast and Energy-efficient Computer Vision” tutorial at the May 2024 Embedded Vision Summit.
As artificial intelligence inference transitions from cloud environments to edge locations, computer vision applications achieve heightened responsiveness, reliability and privacy. This migration, however, introduces the challenge of operating within the stringent confines of resource constraints typical at the edge, including small form factors, low energy budgets and diminished memory and computational capacities. Axelera AI addresses these challenges through an innovative approach of performing digital computations within memory itself. This technique facilitates the realization of high-performance, energy-efficient and cost-effective computer vision capabilities at the thin and thick edge, extending the frontier of what is achievable with current technologies.
In this presentation, Verhoef unveils his company’s pioneering chip technology and demonstrates its capacity to deliver exceptional frames-per-second performance across a range of standard computer vision networks typical of applications in security, surveillance and the industrial sector. This shows that advanced computer vision can be accessible and efficient, even at the very edge of our technological ecosystem.
Have you ever been confused by the myriad of choices offered by AWS for hosting a website or an API?
Lambda, Elastic Beanstalk, Lightsail, Amplify, S3 (and more!) can each host websites + APIs. But which one should we choose?
Which one is cheapest? Which one is fastest? Which one will scale to meet our needs?
Join me in this session as we dive into each AWS hosting service to determine which one is best for your scenario and explain why!
Essentials of Automations: Exploring Attributes & Automation ParametersSafe Software
Building automations in FME Flow can save time, money, and help businesses scale by eliminating data silos and providing data to stakeholders in real-time. One essential component to orchestrating complex automations is the use of attributes & automation parameters (both formerly known as “keys”). In fact, it’s unlikely you’ll ever build an Automation without using these components, but what exactly are they?
Attributes & automation parameters enable the automation author to pass data values from one automation component to the next. During this webinar, our FME Flow Specialists will cover leveraging the three types of these output attributes & parameters in FME Flow: Event, Custom, and Automation. As a bonus, they’ll also be making use of the Split-Merge Block functionality.
You’ll leave this webinar with a better understanding of how to maximize the potential of automations by making use of attributes & automation parameters, with the ultimate goal of setting your enterprise integration workflows up on autopilot.
How to Interpret Trends in the Kalyan Rajdhani Mix Chart.pdfChart Kalyan
A Mix Chart displays historical data of numbers in a graphical or tabular form. The Kalyan Rajdhani Mix Chart specifically shows the results of a sequence of numbers over different periods.
How information systems are built or acquired puts information, which is what they should be about, in a secondary place. Our language adapted accordingly, and we no longer talk about information systems but applications. Applications evolved in a way to break data into diverse fragments, tightly coupled with applications and expensive to integrate. The result is technical debt, which is re-paid by taking even bigger "loans", resulting in an ever-increasing technical debt. Software engineering and procurement practices work in sync with market forces to maintain this trend. This talk demonstrates how natural this situation is. The question is: can something be done to reverse the trend?
Taking AI to the Next Level in Manufacturing.pdfssuserfac0301
Read Taking AI to the Next Level in Manufacturing to gain insights on AI adoption in the manufacturing industry, such as:
1. How quickly AI is being implemented in manufacturing.
2. Which barriers stand in the way of AI adoption.
3. How data quality and governance form the backbone of AI.
4. Organizational processes and structures that may inhibit effective AI adoption.
6. Ideas and approaches to help build your organization's AI strategy.
Agile Web Development, Exove seminar August 15th, 2013
1.
2. Agenda
14.00 Opening words Janne Kalliola
14.10 Summary of agile methodologies Kalle Varisvirta
14.30 What kind of projects does agile
fit in?
Janne Alho
14.50 Break
15.00 What agile project means to the
client?
Laura Halenius, Sitra
15.20 Trust in agile projects Janne Kalliola
15.40 How to buy agile projects? Mikko Hämäläinen
16.00 Discussion
4. Typically, you need to
Achieve more with less resources.
Be among the first ones to launch your
service.
Constantly upgrade your offerings.
Satisfy your business needs and keep your
bottom line in shape.
6. Agile focuses on flow of information
and embraces changes instead of
trying to control them.
Lean focuses on results and strives
to reduce all redundant work.
14. Over 60 people, over 150 customers,
over 3.5 MEUR revenue 2012, profitable,
offices in Helsinki, London & Tallinn
15. Agenda
14.00 Opening words Janne Kalliola
14.10 Summary of agile methodologies Kalle Varisvirta
14.30 What kind of projects does agile
fit in?
Janne Alho
14.50 Break
15.00 What agile project means to the
client?
Laura Halenius, Sitra
15.20 Trust in agile projects Janne Kalliola
15.40 How to buy agile projects? Mikko Hämäläinen
16.00 Discussion
17. History
The history of software development processes
is quite long
Originally the projects were small and thus no
processes were needed
Later on the projects become to grow and
suddenly a need for a process was created
First recognized (non-agile) software
development process was Waterfall
19. Waterfall
Waterfall gets usually credited to Winston Royce
because of his 1970 article
However, the seven-step process created from
the article was a misunderstanding
In the article, Royce was explaining the process
that’s currently in use and how broken and non-
functional it is
He never called it good, nor he named it the waterfall
model – that all came later
20. Royce (in the article):
“Either the requirements
must be modified, or a
substantial change in the
design is required. In
effect the development
process has returned to the
origin and one can expect up
to a 100-percent overrun in
schedule and/or costs.”
21. Waterfall taken into use
After Royce’s article, Waterfall model was taken
into use via the official recommendations by e.g.
the DOD
In 1995, DOD was researching the results of
software projects between 1988 and 1995 and
concluded that 46% of the built systems missed
their real needs that they were never taken into
use
22. Agile Manifesto 2001
Agile methods started appearing into scientific
articles and general knowledge during the
1990’s
In the year 2001, 17 agile method enthusiasts
wrote and published the “Agile Manifesto”
23. Agile manifesto
We are uncovering better ways of developing software by
doing it and helping others do it. Through this work we
have come to value:
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
That is, while there is value in the items on the right,
we value the items on the left more.
25. Scrum
Scrum is the most popular of agile methods
today
The iterations of Scrum are called sprints and
they span usually from 2 to 3 weeks
Scrum is based on the “backlog” which is a
prioritized list of tasks yet to be done
Backlog can and should be updated constantly,
but the tasks in a sprint can’t be changed during
a sprint
26. Scrum
Sprint starts with a two-part sprint planning
Inthe first part the client representatives choose the goals and
tasks for the sprint
Inthe second part the customer /product owner meets the
scrum master or the whole team and chooses the actual tasks
from the backlog for the sprint
Sprint ends with a sprint review
Team or the scrum master shows the goals met and demoes
thetasks done
Also the tasks that didn’t get done are gone through and
prioritized back tothe backlog
Every day the teams holds a status meeting, the daily
scrum
27. Scrum - roles
Customer– Product owner
One person (!), who’s responsible for the creation
and the prioritization of the backlog
Selects the tasks for the next sprint
Together with other representatives of the
customer, reviews the sprint results in the sprint
review
28. Scrum - roles
Development – Scrum team
Development team
Process manager – Scrum master
Usually mostly one of the developers, scrum master
role is only part-time
Handles Scrum’s ceremonies, sprint starting, ending
and daily scrums
29. Scrum
In Scrum, tasks are usually categorized to a
abstraction hierarchy
Epic – too big to be done in one sprint, estimating
very hard, needs to be split into smaller pieces
User story – part of an epic, a single feature or a
business demand
Task –Asingle tasks. One or more is needed to
accomplish a single user story
30. How to fail in Scrum
The number of sprints is set at the project kickoff
or the tasks of sprint are set earlier than in the
sprint planning
New tasks are added to a sprint while the sprint
is running
Product owner isn’t participating, can’t or isn’t
allowed make decisions
32. Extreme programming
(XP)
XP is older than Scrum and less known
Even still, many of it’s practices are used today
XP is the first somewhat popular agile method, it
was around in the 1990’s and thus leading the
way for the popularity of agile
33. Extreme programming
(XP)
XP has 12 core principles
These include the most famous, pair programing
All XP principles are very rarely used, but some
are very popular, for example continuous
integration
34. XP practices
Pair programming
Planning game
Test-driven development
Whole team
Continuous integration
Refactoring
Small releases
35. XP practices (cont)
Coding standards
Collective code ownership
Simple design
System metaphor
Sustainable pace
36. Extreme programming
(XP)
XP has the whole team in the same room and the
customer representative (one or more) always
there, too
All tasks are just written with one, two words or a
sentence to post-it notes or similar
When work starts on a task, the developer goes
through it with the customer
One test engineer is dedicated to producing
acceptance testing with the customer, preferably
automated
37. XP
Because of the customer in the room always –
requirement and the pair programming, XP is
very expensive to take fully into use – usually
impractical, too
XP practices are commonly borrowed into a
process that is mainly based on Scrum
39. Lean
Lean is an old production principle that aims for
removing all waste
Toyota’s production system (TPS) from 1948 –
1975 is considered to be it’s base
To the software industry, lean has arrived only
during after the year 2000
41. Lean - principles
Deliver as fast as possible
Create a feedback loop as soon as possible
Release as frequently as possible to get the feedback into
the development
Empower the team
Self-guided team
Build integrity in
Refactor the architecture frequently
See the whole
Everybody should know the product’s business demands,
purpose and see the whole
42. Lean
As you can see, lean doesn’t dictate rules or
procedures, but bases on principles
Thus lean integrates well with otherAgile or
Lean methodologies
The key is just to remove everything that doesn’t
produce value to the customer
43. Kanban
Kanban is one of the lean software processes
It’s based on a Kanban board, that shows the
state of all tasks
The states move from left to right as they get
done
The key function of the board is to limit the work
that’s in-progress
45. Combinations
Frequently we see multiple of the processes in
use at the same time
As long as you make sure you follow the key
rules, it might work well
Often combinations are used to circumvent the
most important (and hard to implement) rules
Scrumwaterban
47. Agenda
14.00 Opening words Janne Kalliola
14.10 Summary of agile methodologies Kalle Varisvirta
14.30 What kind of projects does agile
fit in?
Janne Alho
14.50 Break
15.00 What agile project means to the
client?
Laura Halenius, Sitra
15.20 Trust in agile projects Janne Kalliola
15.40 How to buy agile projects? Mikko Hämäläinen
16.00 Discussion
48. PROJECT FIT TO AGILE
DEVELOPMENT
JanneAlho
ProjectDirector
50. Project budget
Agile vs. Waterfall
Waterfall
Fixed provider commitment, prior tp project start -> risk included in project offer price
Buyers plans for changes
Change budgeting (typically 10%-20%)
Change Requests handling is a hard “playing field” between parties
What is additional effort to manage/negotiate and get approval to Change Requests
What is buyers knowledge level in handling technical details related to CR’s
Agile
Full project budget visible to both parties
Risk sharing needs to be agreed during contract negotiation
Change needs is part of joined estimates, as part of targets ambiquity and order of
importance evaluation
Managing changes is part of normal Agile project handling – no need for separate CR
handling
Budget control becomes a joined cause
52. Project scope and target
Agile vs. Waterfall
Waterfall
Requires detailed scope definitions beforehand
Project targets can not change much during project
All changes require separate handling
In problematic projects mutual agreement may be very difficult to achieve
Provide can progress project more independently. The end result
is needed to be verified only in the end of the project
Agile
In order to start, project scope is needed only in overall level
Project target is allowed to change according to buyer needs
In order to get good results efficiently, a strong guidance is
needed. Guidance need to be given by person who has full and
detailed understanding of customer needs
Project results are being validated throughout the project
53. Project team
Agile vs. Waterfall
Waterfall
Requirements writer is in key role
PM manages the development to be done according to requirments and
reports to both organizations
Developers are often far from requirements writer
Agile
Product Owner – Owns requirements during project
In key position to make sure that requirements are clear to developers
Works close to both organizations
Developers (Tech Lead and other developers)
Take part in understanding targets and reasons behind requirements
Role and commitment is bigger than in waterfall
Project Manager
Provides material required to follow up project (hour reports, progress reports,
excecutive summaries)
Monitors and plans resources and reacts to exceptions
Normally less involved than in waterfall
54. Experiences
Janne Alho
1989 -2013 Nokia Business Communications, Comverse, First
Hop, Airwide, Mavenir, Exove
Telecom tele, Telecom Web, Web solutions
Personal experiences
Lead time from requirements definition to market launch has been
significantly reduced all the time
Waterfall projects provide results too late for business needs
Solutions are very strongly tuned during development, and further tuned
during production life
Agile model provides clear ground rules to all players
Agile provides ways to take learnings found during project better into
account
Agile provides possibility to give developers more understanding on all
overall goals in order to reach them
Customer PO, and the support that provider can give to him/her is one of
the key success factors in agile projects
56. Agenda
14.00 Opening words Janne Kalliola
14.10 Summary of agile methodologies Kalle Varisvirta
14.30 What kind of projects does agile
fit in?
Janne Alho
14.50 Break
15.00 What agile project means to the
client?
Laura Halenius, Sitra
15.20 Trust in agile projects Janne Kalliola
15.40 How to buy agile projects? Mikko Hämäläinen
16.00 Discussion
66. Agenda
14.00 Opening words Janne Kalliola
14.10 Summary of agile methodologies Kalle Varisvirta
14.30 What kind of projects does agile
fit in?
Janne Alho
14.50 Break
15.00 What agile project means to the
client?
Laura Halenius, Sitra
15.20 Trust in agile projects Janne Kalliola
15.40 How to buy agile projects? Mikko Hämäläinen
16.00 Discussion
67. Trust
Agile practices place great emphasis on the
team
Encourages autonomy
Leadership is shared
Team has substantially more control
Trust is required from managers and clients to
avoid micromanagement or falling back to non-
agile methodologies
68. Definition of Trust
When you trust to someone, you are willing to
be vulnerable to the actions of another party
Based on the expectation that the other party
will perform an important action
Irrespective of the ability to monitor or control the
other party
69. Definition of Trust, cont’d
Trust is not a behaviour or a choice
But a psychological state that cause or result
from aforementioned actions
That is related to both rational and emotional
skills of the people involved
70. And?
This means that trust must be built, not
purchased or ordered
Building is a long and fragile process
Requires participation from each party
Blunders are ok when they are not repetitive or
malicious
71. The Basic Needs
In order to create and grow trust, the basics
need to be in a good shape:
The goals are well-defined and reachable
The client loosens the control – at least somewhat –
to allow vendor to perform on its own
The vendor is able to run with the ball
72. How to Build Trust?
Trust is created with small actions that stay
constant
Everyone respects the others
Communication is open, honest and immediate
Expectations are managed by all parties
People are not punished for making mistakes
73. Threats to Trust
Not enough external visibility to the project
Team need to keep everyone on the same page about
the progress
Demos and shared environments
Tensions between developers and the product
owner / customer
Everyone needs to agree on the shared goals and
means to reach them
Underestimations
Team need to assess its capability to estimate and make
changes as required
74. What You Gain from
Trust?
Trust reduces extra work
Focuses everyone’s attention to things that matter
Less controls and meetings
The project generates more customer value with the
same investment
Trust allows people to talk about difficult or painful
matters openly
No issues are swept under the carpet
Trust makes the project team happier -> improves
productivity and work meaningfulness
75. Onward
Trust helps everyone to get things done in a
pleasant way
It should be one of the primary goals in a successful IT
relationship
Sell the idea of trust to your team
Guide their steps when they try to build and maintain it
If possible, participate actively
If you have trustworthy teams, vendors or project,
remember to praise them from time to time
76. Agenda
14.00 Opening words Janne Kalliola
14.10 Summary of agile methodologies Kalle Varisvirta
14.30 What kind of projects does agile
fit in?
Janne Alho
14.50 Break
15.00 What agile project means to the
client?
Laura Halenius, Sitra
15.20 Trust in agile projects Janne Kalliola
15.40 How to buy agile projects? Mikko Hämäläinen
16.00 Discussion
78. About Speaker
Mikko Hämäläinen, DI
Responsible for Consulting at Exove
Over 15 years of industry experience
Product management, project management, SW development
Web & mobile, identity management
Currently working on…
Online business, best practices, how tocreate value?
Studies, e.g. what direction totake in online development
Product ownership
Marketing automation
@mthamalamikko@exove.fi
79. What’s Agile Buying?
The goal is to do a truly agile project
Focus on skills & experience of the vendor – not
just budget, schedule, and scope
Flexible contract model – 2 out of 3 can be fixed:
Budget
ScopeSchedule
80. Anatomy of an Agile
Online Project
Creativeprocess
Concept Userinterfaces/visuals
Technicalvendorpartofprojectfromthestart
Design&technologydonetight,agilecollaboration
Contentcreation
andinput
Launch!
Initial
definition
and
vendor
selection
Technicalimplementation
Iterative,agileproject
Deploy-
ment
81. Two Models for Buying an
Agile Online Project
1. Buy resources
An agile team or part of it for a specified time
Customer is responsible for driving the team
Very flexible and powerful – when product ownership is
good
Decision factors: skills, references, and daily price
Buyer must define the skills that are needed to get to the
goal
Vendors&consultantscanhelphere
Make use of vendor’s special skills outside core team
82. Two Models for Buying an
Agile Online Project
2. Agile project
Implementation of certain scope defined on high level
Customer is responsible for requirements & priorities,
vendor organizes the implementation work
Often budged & schedule are fixed, scope is flexible
Agile backlog collaboratively refined during the project
The service can be published once key features
creating value have been implemented (MVP)
Decision factors: References, skills, project model
and daily price
83. Budget, Scope, and Schedule
– Contractual Model for Agile
Splitscope in 2-3 categories
Max.50%mandatoryfeatures
Estimateall work and create budgedbasedon the total
Actualtime spenton each feature realizedduringthe project
The goalis to publisha working,valuableservice in budgetand
schedule
ProjectManagement
Design
Implementation:Priority1 Priority2-3
Wk 1 2 3 4 5 6 7 8 9 10 11 12
Production
Scheduleandbudgetlimit
Mandatorywork
grows/shrinksduringthe
project
Restofthebudget&
timespenthere
Maintenance
/furtherdev.
84. Buyer’s Checklist
1. Clearly define big goals – and prepare for changes
during the project
2. Work with known and trusted vendors
3. Emphasis on product ownership – buy help when
you need it
4. Launch as early as possible – let the customer
feedback guide further development
Consulting before and during the project can
save a lot of money during the implementation
phase
85. Agile online project works for everyone
willing to get better results more effectively
86. THANK YOU!
Seminar materials and contact information
on www.exove.com
See you at:
• DrupalCamp Baltics 23.8. Tallinn
• WordPress Café 10.9. 16-18 Exove
• DrupalCon Prague 23.-27.9.
Aseta selkeät isot päämäärät – ja valmistaudu muutoksiin matkallaMitoita budjetti oikein suhteessa toiveisiinVarmista oikea osaaminen projektissaValitse kumppaneiksi tunnettuja ja luotettavia verkkoalan toimijoita Valitse tarpeeksi suuri kumppani, jonka kanssa jatkoyhteistyö on turvattua. Suunnittelun ja toteutuksen yhteispeli toimivaksiOikeat teknologiat tarpeisiin nähdenPanosta tuoteomistajuuteen – tarvittaessa kouluttaudu ennen projektiaTuoteomistajalle (ja toimittajalle) valta päättää yksityiskohdistaRiittävästi aikaa tuoteomistajalleYksityiskohtien loputon hiominen harvoin parantaa tulostaPyri julkaisemaan mahdollisimman aikaisin – ja anna asiakaspalautteen ohjata (osaltaan) jatkokehitystä