Learn about the Scrum implementation of Agile Software Development. We’ll discuss the importance of this ubiquitous framework, the composition of a Scrum team, the importance of the ceremonies, and much more.
The document discusses different approaches to software development such as waterfall, scrum, and agile. It notes problems with waterfall such as no working software until late and inability to adapt to changing requirements. It summarizes key aspects of agile such as valuing individuals, working software, and responding to change over documentation and strict plans. The document advocates for estimating but not relying on precise predictions, prioritizing based on value, thin feature slicing, and building quality in daily.
The realities of working in an enterprise (distributed teams, multiple stakeholders, etc) present a series of challenges when trying to plan and scale agile development. Learn how Rosetta Stone knit together a dozen existing JIRA Agile boards into a coherent program-level view of their Scaled Agile Framework (SAFe) release train using JIRA Portfolio – without sacrificing team autonomy.
Project Managers often face an identity crisis when companies transition to agile: either become a scrum master, move to another role entirely, or another company! This discussion will demonstrate how project management can not only co-exist with your agile process, but thrive. Plus, you'll learn how Gilt blends agile principles with traditional project management techniques to bring their strategic initiatives to life.
Techniques for Keeping Retrospectives Effective and FunFadi Stephan
This document discusses retrospectives in Agile software development. It outlines the basic structure of retrospectives, including setting the stage, gathering data, generating insights, deciding what to do, and closing. It emphasizes the "prime directive" of understanding that everyone did their best given the circumstances. The document also presents various tools that can be used in retrospectives, such as timelines, silent retrospectives, and team radars. It concludes by advertising an upcoming Agile engineering conference and recommending a book on Agile retrospectives.
Modernizing Development - The Road to Agility and DevOps at CompuwareAtlassian
Transforming a development organization from waterfall to agile is a big undertaking. Even larger when it’s a 40-year-old mainframe development organization. Having the vision for the future and the proper tools to enable that vision is essential. Join David Rizzo, an IT veteran, who led the transformation of Compuware from waterfall to agile and implementation of DevOps. You’ll see how Confluence was used to promote collaboration, in the office and in the field. How JIRA Software was used to track agile tasks and projects and how Bitbucket was utilized for handling source code. A modern DevOps toolchain is key to successful implementation. Using the Atlassian tools, Agile and DevOps were fully implemented across the entire organization.
Connect strategic goals with development realities with JIRA PortfolioAnna Ioceva
JIRA Portfolio is a relatively new Atlassian product, which provides a single, accurate view for planning and managing initiatives across multiple teams and projects in JIRA.
We will cover its key features:
- managing pre-project stages
- planning large initiatives across multiple JIRA projects
- teams and people - skills, vacations, work hours
- automatic schedule calculation .
- reporting over high level strategic themes
- team's utilization report.
Celebrating Portfolio for JIRA's First Year with Five LearningsAtlassian
Portfolio for JIRA's 1st year, in short, has been one hell of a ride. Join product manager Martin Suntinger as he talks about data-driven planning no-one will secretly shake their heads at, how to maintain your innovation mojo at scale, and how to report beyond just facts and figures. Plus, see what's in store for the next generation of Portfolio for JIRA. No "terrible twos" here!
The document discusses different approaches to software development such as waterfall, scrum, and agile. It notes problems with waterfall such as no working software until late and inability to adapt to changing requirements. It summarizes key aspects of agile such as valuing individuals, working software, and responding to change over documentation and strict plans. The document advocates for estimating but not relying on precise predictions, prioritizing based on value, thin feature slicing, and building quality in daily.
The realities of working in an enterprise (distributed teams, multiple stakeholders, etc) present a series of challenges when trying to plan and scale agile development. Learn how Rosetta Stone knit together a dozen existing JIRA Agile boards into a coherent program-level view of their Scaled Agile Framework (SAFe) release train using JIRA Portfolio – without sacrificing team autonomy.
Project Managers often face an identity crisis when companies transition to agile: either become a scrum master, move to another role entirely, or another company! This discussion will demonstrate how project management can not only co-exist with your agile process, but thrive. Plus, you'll learn how Gilt blends agile principles with traditional project management techniques to bring their strategic initiatives to life.
Techniques for Keeping Retrospectives Effective and FunFadi Stephan
This document discusses retrospectives in Agile software development. It outlines the basic structure of retrospectives, including setting the stage, gathering data, generating insights, deciding what to do, and closing. It emphasizes the "prime directive" of understanding that everyone did their best given the circumstances. The document also presents various tools that can be used in retrospectives, such as timelines, silent retrospectives, and team radars. It concludes by advertising an upcoming Agile engineering conference and recommending a book on Agile retrospectives.
Modernizing Development - The Road to Agility and DevOps at CompuwareAtlassian
Transforming a development organization from waterfall to agile is a big undertaking. Even larger when it’s a 40-year-old mainframe development organization. Having the vision for the future and the proper tools to enable that vision is essential. Join David Rizzo, an IT veteran, who led the transformation of Compuware from waterfall to agile and implementation of DevOps. You’ll see how Confluence was used to promote collaboration, in the office and in the field. How JIRA Software was used to track agile tasks and projects and how Bitbucket was utilized for handling source code. A modern DevOps toolchain is key to successful implementation. Using the Atlassian tools, Agile and DevOps were fully implemented across the entire organization.
Connect strategic goals with development realities with JIRA PortfolioAnna Ioceva
JIRA Portfolio is a relatively new Atlassian product, which provides a single, accurate view for planning and managing initiatives across multiple teams and projects in JIRA.
We will cover its key features:
- managing pre-project stages
- planning large initiatives across multiple JIRA projects
- teams and people - skills, vacations, work hours
- automatic schedule calculation .
- reporting over high level strategic themes
- team's utilization report.
Celebrating Portfolio for JIRA's First Year with Five LearningsAtlassian
Portfolio for JIRA's 1st year, in short, has been one hell of a ride. Join product manager Martin Suntinger as he talks about data-driven planning no-one will secretly shake their heads at, how to maintain your innovation mojo at scale, and how to report beyond just facts and figures. Plus, see what's in store for the next generation of Portfolio for JIRA. No "terrible twos" here!
Realizing a solution is no longer enough
Imagine yourself a clever software developer, sitting in his room, working deep at night. For weeks, months, he's breeding on that one perfect solution. He codes like crazy, refactors, rebuilds. He wants it to be perfect. May be he showed it to some of his friends and they told him they like the idea. After a lot of hard work the solution is finally ready. Excited and full of expectations he introduces it to the market. Soon, all his effort will pay off, money will start flowing. Unfortunately, nobody seems to be interested in using the product and for sure they don't want to pay for it. What went wrong? How to prevent? During the lecture we will discuss how to cut this big salami into small pieces by using a lean development approach based on Scrum.
The process of defining a roadmap is arguably one of the most difficult but important things a product manager has to do. Far too often roadmaps are built without the complete picture in mind, without the right timing, in silos, or are misdirected. How then can we ensure we’re doing it right? Is there really such a thing as an agile roadmap?
This talk will draw from lessons learnt building product to provide practical tips and techniques enabling you to understand roadmap inputs, plan with different perspectives in mind, optimise for learning, communicate and set roadmap goals as well as find agility when the landscape around you changes.
Products covered:
Confluence
This document outlines a presentation on fundamentals of agile software development given by Ikenna Nwaiwu. The presentation introduces the Lagos Agile & Craftsmanship Meetup group, its mission to spread knowledge of agile principles and practices in Nigeria. It then covers the values and principles of the Agile Manifesto, including emphasizing individuals and interactions, working software, customer collaboration, and responding to change. The contents of the presentation are listed as the Agile Manifesto, principles of agile, and agile methods.
Large companies often struggle to align development with sales and marketing - how do you ensure the delivery of features and fixes lines up with the efforts to promote them? Luisa will talk about how a big organization implemented a lightweight version of SAFe, but adapted the methodology to fit their needs. Learn how you can tailor agile principles to address the unique challenges your teams face and why configuring your agile tools properly is critical to increasing agility throughout the company.
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.
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.
Agile processes emphasize collaboration between customers, developers, and designers to develop software through short iterative cycles. Teams work to eliminate waste and adaptively plan in two-week sprints, where they focus on delivering working functionality, get feedback, and improve. Common agile frameworks like Scrum involve cross-functional teams that regularly meet to discuss progress, issues, and plan the next increments.
Key Takeaways from Managing an Integrated JIRA ExperienceAtlassian
This document discusses how Kiva, a nonprofit organization, uses various Atlassian products like JIRA, HipChat, Confluence, and Geckoboard to manage projects and collaborate across teams. It provides examples of how JIRA is integrated with HipChat for real-time communication, with Confluence for documentation, and with Salesforce to close the loop from user feedback to development. Geckoboard is used to create customizable dashboards for tracking key metrics. The document emphasizes how these tools help Kiva collaborate anywhere, track everything, and bridge gaps between teams.
Salesforce.com underwent a major enterprise-wide transformation to an Agile development methodology over the course of just 3 months. The transformation was done in a "Big Bang" approach where everyone transitioned together. The results were significant increases in features delivered per team, decreased time between major releases, and improved customer and employee satisfaction. The transformation approach involved executive commitment, a dedicated cross-functional rollout team, training employees in Agile concepts, and radical transparency.
Managing the Chaos of Client Collaboration and Physical DeploymentAtlassian
The document discusses managing the chaos of experiential events using Atlassian tools. It describes how Helios used JIRA for project management from the sales pipeline through development. During the prototyping phase, concerns arose about hardware integration and whether the experience aligned with the brand story. At SXSW, issues with motion sickness, environment changes, and internet access occurred. Setup challenges included electricity, construction, and unexpected full footprint. Risks like these were mitigated through preparation and quick on-site problem solving, allowing innovative experiences to be created despite changing requirements and risks.
Agile projects do involve planning contrary to a common myth. There are five levels of planning - product vision, roadmap, release plan, iteration plan, and daily plan. While detailed upfront planning is not done, planning occurs continuously. Another myth is that there is no feedback on progress without a plan, but product and sprint backlogs provide burn down visibility. Finally, while the scope may be adjusted, Agile projects have timeboxes and budgets, and documentation is still created when prioritized and not a roadblock to delivery.
At Atlassian, we strive to improve how our engineering, marketing, service and IT teams work together. We believe great teamwork is the result of shared goals, effective communication, and clear and transparent processes.
Learn how Atlassian helps teams work better together. This presentation shares our newest product features and illustrate how they help us get more done.
(Re)Discover JIRA Core: Tricks that Make a BIG DifferenceAtlassian
What do nontechnical teams, such as marketing, operations, HR, finance and legal have in common? Even though their processes might be different they can all use JIRA Core to track contracts, candidates, campaigns, approvals, and much more. But there are so many things you can tweak when setting up your team process: workflows, permissions, projects, issue types, etc.
Whether you’re new to JIRA Core, or a power user, we’ll share the best practices for business teams, and give examples of how teams use JIRA Core effectively. You'll learn how to:
Set up JIRA Core to match your business team's process
Set up user permissions for approval processes
Manage issues across different projects
Handle multiple milestone due dates
Expect tons of examples and aha moments when diving deep into the core of JIRA.
Products covered:
JIRA Core
The document discusses different approaches to agile software development including Scrum, Kanban, Extreme Programming (XP), Lean Startups, and Design Driven Development (D3). It explains that agile is a philosophy focused on individuals, collaboration, adaptability to change, and delivering working software frequently. Specific agile methods then apply this philosophy through practices like test-driven development, daily standups, limiting work in progress, and continuous delivery.
Slides talking about Scrum, Dr. Sami Taha (Instructor at Palestine Polytechnic University) was explained about Scrum and he used these slides into event by Hebron Tech Meetup.
Eng. Meqdad Darweesh
CSE Engineer
This document discusses Agile and Scrum methodologies for web development projects. It defines Agile as an iterative development process built around self-organizing teams. Scrum is described as one of the most commonly used Agile frameworks, with an emphasis on delivering working software in short iterations called sprints. The document contrasts the Waterfall and Agile approaches, and explains how Scrum's daily stand-up meetings help track progress, plan work, and identify impediments.
The document discusses agile software development and methodologies like Scrum and XP. It notes that agile practices work best for small organizations that value individuals, interactions, working software, and responding to change over processes, documentation, contracts, and plans. For large organizations, some processes are needed to manage agile development. Real-world examples of agile in practice are provided, including using Scrum for an island project and the iterative development process used at Eclipse.
How to Measure Agility Project Success in Business TermsEthan Ram
The document discusses various ways to measure the success of agile projects in business terms. It suggests measuring key performance indicators related to support issues like open escalations and fault rates. Other metrics include waste reduction by decreasing builds versus deliveries and shortening bug resolution times. Employee satisfaction, revenues, and release cycle times can also indicate how agile methods have helped the business.
The document discusses the differences between traditional project management and agile project management. An agile project manager manages the unknown rather than following a detailed plan and focuses on facilitating decision making rather than making decisions. Key traits of an agile project manager include being cross-functional, building relationships, encouraging innovation, and facilitating collaboration rather than controlling the project. Agile project management values respecting individuals over processes.
Reducing Tickets and Crushing SLAs with StatusPageAtlassian
Downtime is a fact of life, and can be a great competitive advantage for your company and your customers if you handle it well. By keeping customers and employees informed during downtime, you can build trust and cut support costs.
Join Scott, co-founder of StatusPage, for a history of the company and its recent acquisition by Atlassian. We'll cover StatusPage best practices we've learned along the way, and tips for implementing a great StatusPage experience for you and your customers.
Products covered:
StatusPage
This document provides an overview of Agile project management and Scrum methodology. It defines Waterfall project management as a sequential process and explains that Agile is an iterative approach. Scrum is described as one version of Agile that uses roles like Product Owner, ScrumMaster, and Team. It also outlines the artifacts (Product and Sprint Backlogs, burndowns), ceremonies (Sprint Planning, Daily Scrum, Demo), and case studies where CivicActions used Scrum successfully on projects for clients.
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.
Realizing a solution is no longer enough
Imagine yourself a clever software developer, sitting in his room, working deep at night. For weeks, months, he's breeding on that one perfect solution. He codes like crazy, refactors, rebuilds. He wants it to be perfect. May be he showed it to some of his friends and they told him they like the idea. After a lot of hard work the solution is finally ready. Excited and full of expectations he introduces it to the market. Soon, all his effort will pay off, money will start flowing. Unfortunately, nobody seems to be interested in using the product and for sure they don't want to pay for it. What went wrong? How to prevent? During the lecture we will discuss how to cut this big salami into small pieces by using a lean development approach based on Scrum.
The process of defining a roadmap is arguably one of the most difficult but important things a product manager has to do. Far too often roadmaps are built without the complete picture in mind, without the right timing, in silos, or are misdirected. How then can we ensure we’re doing it right? Is there really such a thing as an agile roadmap?
This talk will draw from lessons learnt building product to provide practical tips and techniques enabling you to understand roadmap inputs, plan with different perspectives in mind, optimise for learning, communicate and set roadmap goals as well as find agility when the landscape around you changes.
Products covered:
Confluence
This document outlines a presentation on fundamentals of agile software development given by Ikenna Nwaiwu. The presentation introduces the Lagos Agile & Craftsmanship Meetup group, its mission to spread knowledge of agile principles and practices in Nigeria. It then covers the values and principles of the Agile Manifesto, including emphasizing individuals and interactions, working software, customer collaboration, and responding to change. The contents of the presentation are listed as the Agile Manifesto, principles of agile, and agile methods.
Large companies often struggle to align development with sales and marketing - how do you ensure the delivery of features and fixes lines up with the efforts to promote them? Luisa will talk about how a big organization implemented a lightweight version of SAFe, but adapted the methodology to fit their needs. Learn how you can tailor agile principles to address the unique challenges your teams face and why configuring your agile tools properly is critical to increasing agility throughout the company.
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.
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.
Agile processes emphasize collaboration between customers, developers, and designers to develop software through short iterative cycles. Teams work to eliminate waste and adaptively plan in two-week sprints, where they focus on delivering working functionality, get feedback, and improve. Common agile frameworks like Scrum involve cross-functional teams that regularly meet to discuss progress, issues, and plan the next increments.
Key Takeaways from Managing an Integrated JIRA ExperienceAtlassian
This document discusses how Kiva, a nonprofit organization, uses various Atlassian products like JIRA, HipChat, Confluence, and Geckoboard to manage projects and collaborate across teams. It provides examples of how JIRA is integrated with HipChat for real-time communication, with Confluence for documentation, and with Salesforce to close the loop from user feedback to development. Geckoboard is used to create customizable dashboards for tracking key metrics. The document emphasizes how these tools help Kiva collaborate anywhere, track everything, and bridge gaps between teams.
Salesforce.com underwent a major enterprise-wide transformation to an Agile development methodology over the course of just 3 months. The transformation was done in a "Big Bang" approach where everyone transitioned together. The results were significant increases in features delivered per team, decreased time between major releases, and improved customer and employee satisfaction. The transformation approach involved executive commitment, a dedicated cross-functional rollout team, training employees in Agile concepts, and radical transparency.
Managing the Chaos of Client Collaboration and Physical DeploymentAtlassian
The document discusses managing the chaos of experiential events using Atlassian tools. It describes how Helios used JIRA for project management from the sales pipeline through development. During the prototyping phase, concerns arose about hardware integration and whether the experience aligned with the brand story. At SXSW, issues with motion sickness, environment changes, and internet access occurred. Setup challenges included electricity, construction, and unexpected full footprint. Risks like these were mitigated through preparation and quick on-site problem solving, allowing innovative experiences to be created despite changing requirements and risks.
Agile projects do involve planning contrary to a common myth. There are five levels of planning - product vision, roadmap, release plan, iteration plan, and daily plan. While detailed upfront planning is not done, planning occurs continuously. Another myth is that there is no feedback on progress without a plan, but product and sprint backlogs provide burn down visibility. Finally, while the scope may be adjusted, Agile projects have timeboxes and budgets, and documentation is still created when prioritized and not a roadblock to delivery.
At Atlassian, we strive to improve how our engineering, marketing, service and IT teams work together. We believe great teamwork is the result of shared goals, effective communication, and clear and transparent processes.
Learn how Atlassian helps teams work better together. This presentation shares our newest product features and illustrate how they help us get more done.
(Re)Discover JIRA Core: Tricks that Make a BIG DifferenceAtlassian
What do nontechnical teams, such as marketing, operations, HR, finance and legal have in common? Even though their processes might be different they can all use JIRA Core to track contracts, candidates, campaigns, approvals, and much more. But there are so many things you can tweak when setting up your team process: workflows, permissions, projects, issue types, etc.
Whether you’re new to JIRA Core, or a power user, we’ll share the best practices for business teams, and give examples of how teams use JIRA Core effectively. You'll learn how to:
Set up JIRA Core to match your business team's process
Set up user permissions for approval processes
Manage issues across different projects
Handle multiple milestone due dates
Expect tons of examples and aha moments when diving deep into the core of JIRA.
Products covered:
JIRA Core
The document discusses different approaches to agile software development including Scrum, Kanban, Extreme Programming (XP), Lean Startups, and Design Driven Development (D3). It explains that agile is a philosophy focused on individuals, collaboration, adaptability to change, and delivering working software frequently. Specific agile methods then apply this philosophy through practices like test-driven development, daily standups, limiting work in progress, and continuous delivery.
Slides talking about Scrum, Dr. Sami Taha (Instructor at Palestine Polytechnic University) was explained about Scrum and he used these slides into event by Hebron Tech Meetup.
Eng. Meqdad Darweesh
CSE Engineer
This document discusses Agile and Scrum methodologies for web development projects. It defines Agile as an iterative development process built around self-organizing teams. Scrum is described as one of the most commonly used Agile frameworks, with an emphasis on delivering working software in short iterations called sprints. The document contrasts the Waterfall and Agile approaches, and explains how Scrum's daily stand-up meetings help track progress, plan work, and identify impediments.
The document discusses agile software development and methodologies like Scrum and XP. It notes that agile practices work best for small organizations that value individuals, interactions, working software, and responding to change over processes, documentation, contracts, and plans. For large organizations, some processes are needed to manage agile development. Real-world examples of agile in practice are provided, including using Scrum for an island project and the iterative development process used at Eclipse.
How to Measure Agility Project Success in Business TermsEthan Ram
The document discusses various ways to measure the success of agile projects in business terms. It suggests measuring key performance indicators related to support issues like open escalations and fault rates. Other metrics include waste reduction by decreasing builds versus deliveries and shortening bug resolution times. Employee satisfaction, revenues, and release cycle times can also indicate how agile methods have helped the business.
The document discusses the differences between traditional project management and agile project management. An agile project manager manages the unknown rather than following a detailed plan and focuses on facilitating decision making rather than making decisions. Key traits of an agile project manager include being cross-functional, building relationships, encouraging innovation, and facilitating collaboration rather than controlling the project. Agile project management values respecting individuals over processes.
Reducing Tickets and Crushing SLAs with StatusPageAtlassian
Downtime is a fact of life, and can be a great competitive advantage for your company and your customers if you handle it well. By keeping customers and employees informed during downtime, you can build trust and cut support costs.
Join Scott, co-founder of StatusPage, for a history of the company and its recent acquisition by Atlassian. We'll cover StatusPage best practices we've learned along the way, and tips for implementing a great StatusPage experience for you and your customers.
Products covered:
StatusPage
This document provides an overview of Agile project management and Scrum methodology. It defines Waterfall project management as a sequential process and explains that Agile is an iterative approach. Scrum is described as one version of Agile that uses roles like Product Owner, ScrumMaster, and Team. It also outlines the artifacts (Product and Sprint Backlogs, burndowns), ceremonies (Sprint Planning, Daily Scrum, Demo), and case studies where CivicActions used Scrum successfully on projects for clients.
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.
Agile development methodology focuses on iterative development where requirements and solutions evolve through collaboration between cross-functional teams. Some key aspects of agile include short development cycles, working software over documentation, customer collaboration, and responding to change. Scrum is a popular agile framework used at W3i that utilizes user stories, estimating, planning meetings, daily stand-ups, burndown charts, sprints, reviews and retrospectives to deliver working software frequently.
Agile is a software development methodology in which the development is carried out iteratively and the requirements evolve through continuous inspection and adaptation. Some of the most commonly used agile software development methods/frameworks are: Adaptive Software Development (ASD), Extreme Programming (XP), Scrum and Kanban.
This presentation has been compiled using material available in public domain. Copyrights of the owners and sources of the material used has been duly acknowledged.
The document introduces Agile software development, which originated from a need for more flexible approaches compared to traditional waterfall models. It describes how in 2001, 17 software developers published the Agile Manifesto which values individuals, collaboration, working software, and responding to change over rigid processes and documentation. The manifesto led to principles like frequent delivery, collaboration between business and technical roles, self-organizing teams, and valuing working software over documentation.
For projects like building a power plant or a train tunnel, tough project managers are needed. But when it comes to developing digital or physical products, the role of a project manager has an increasingly difficult standing. During agile or digital transformations, new roles emerge to take over project management tasks. So, are project managers needed in these areas in the future?
The document provides an introduction to Agile project management. It defines Agile as an iterative approach to project management that is commonly used for software development. The key characteristics of Agile methods include being people-driven, facilitating frequent delivery of working software increments, measuring success through working software, and embracing change. The document discusses why Agile approaches are useful compared to traditional "industrial" methods, and how Scrum is one of the most commonly used Agile frameworks, allowing for predictable delivery through short sprints. It also outlines benefits of Agile for convincing executives like reducing risk and ensuring continuous alignment with changing needs.
Why Agile?
What is Agile?
Agile is a mindset
5 key characteristics
Agility can not be planned
Modern Agile
Agile with Scrum
Incremental development
Convincing Senior Executives
Final word
The document provides an overview of Agile development and Scrum methodology. It discusses key Agile concepts like the Agile Manifesto, Scrum roles and artifacts, timeboxing, and metrics like velocity and burndowns. It also addresses adopting Agile, working with requirements and QA, and challenges of offshore development in an Agile model.
This document describes a process called Single Point Continuous Flow that combines elements of Scrum and Kanban for executing small, self-contained projects quickly. Key aspects include: limiting work-in-progress to one story per developer; having developers work on stories from start to finish with minimal interruptions; maintaining a prioritized backlog of ready stories; and applying lean principles like continuous flow and minimizing waste. The process evolved over six months for a team that saw their throughput increase by 60% when adjusted for hours, demonstrating the effectiveness of this Scrumban-inspired approach for small, focused development efforts.
This document provides an overview of agile fundamentals and concepts. It discusses the roots of agile in scientific management and plan-driven approaches. It describes the agile manifesto values and principles. It outlines several agile approaches like Scrum, XP, FDD, and Kanban. It defines the roles of delivery teams, product owners, and product owner teams. It maps out the typical agile ceremonies of visioning, release planning, specification, sprint planning, daily standups, reviews, and retrospectives. Finally, it lists some key agile fundamental concepts around value delivery, stakeholder engagement, team performance, adaptive planning, problem resolution, and continuous improvement.
The document provides an overview of agile software development methods. It discusses the history and principles of agile development, including the Agile Manifesto. Specific agile methods like Scrum, XP, RAD, TDD, Crystal and Kanban are covered. For Scrum, it describes the roles of Product Owner, Scrum Master and Development Team. It also explains Scrum events like Sprint Planning, Daily Scrums, Sprint Review and Retrospective. The document aims to give the reader a brief introduction to common agile concepts and practices.
Return on Investment (ROI) of Lean & Agile MethodsDavid Rico
Quick overview of the Return on Investment of (ROI) of using Lean & Agile Methods for managing the development of high-technology products and services. Begins with the impetus for using lean and agile vs. traditional methods and techniques, an overview of why traditional projects fail, a definition of lean and agile methods, and a quick overview of its value system, principles, and organizational context. Then, provides a quick survey of major competing lean and agile methods, techniques, paradigms, their evolution, and history. Then, it provides a broad survey of the costs, benefits, return on investment, and business performance of using lean and agile methods at the project, program, portfolio, organization, industry, and national levels. Wraps up with a few high-profile case studies, and a summary of lean and agile project management principles.
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.
Agile methodology is a project management approach that breaks work into short phases with frequent reassessment. It values individuals, working software, customer collaboration, and response to change over processes, documentation, contracts, and plans. The Agile Manifesto outlines these values. Traditional approaches use waterfall development with sequential phases and no revisiting. Agile is useful when requirements change, development is long-term, and collaboration is needed. Popular aspects of Agile include sprints, Scrum meetings, backlogs, user stories, and frequent deliveries.
This document discusses Agile product development using the SCRUM model. It describes SCRUM as a framework for project management that develops software in incremental steps by having teams complete features in short time periods called sprints. The key aspects of SCRUM covered are the roles of the product owner, development team, and SCRUM master, as well as the core processes of sprint planning, daily stand-ups, sprint reviews, and retrospectives. The document emphasizes that SCRUM aims to facilitate adaptive planning, self-organizing teams, and rapid delivery of working software.
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.
Agile Project Management - An introduction to Agile and the new PMI-ACPDimitri Ponomareff
The PMI-ACP recognizes knowledge of agile principles, practices and tools and techniques across agile methodologies. If you use agile practices in your projects, or your organization is adopting agile approaches to project management, then this PDM will provide a full overview about this new PMI certification while exploring key agile principles, practices and techniques. If you always wanted to learn more about agile, this presenter is a certified Agile practitioner, trainer and coach so you will receive up to date information about the state of Agile and how it can most help you in your organization or your career.
The document discusses Agile software development methods and provides evidence that Agile approaches are effective. It defines Agile development as iterative and incremental with close collaboration. Case studies show organizations achieving better results with Agile, including increased productivity, quality, and customer satisfaction. Adopting Agile practices like Scrum and test-driven development enables organizations to adapt to changing priorities and deliver working software more frequently.
AWS offers everything you need to deploy a secure and flexible data lake in the cloud. Discover how services like Amazon Simple Storage Service (Amazon S3) and Amazon Redshift can be used together to build and manage your own data lake, and how AWS Lake Formation makes it possible to set up a data lake in days. We walk through an example architecture together, covering everything from data storage to data analytics.
Demystifying Data Science & Analytics - 757ColorCoded 2019Guillermo A. Fisher
This document provides definitions and explanations related to data science and analytics. It begins by defining key terms like big data, data analytics, data science, machine learning, and artificial intelligence. It then discusses the challenges posed by large and complex data sets. Next, it outlines a hierarchy of needs for organizations adopting data science and analytics. Finally, it reviews common roles in data science teams including data engineers, data analysts, and data scientists.
This document discusses cultural identity and what culture encompasses. It explores the author's cultural heritage as someone who is Afro-Latino and Afro-Caribbean and was surrounded by the African, Caribbean, West Indian, and Latino diasporas growing up. The author discusses leaving home to attend college and having to figure out how to relate to others from different cultural backgrounds. The author identifies some of the key pillars of their culture that include movies/TV, music, and food from various genres and regions.
The document discusses release management and continuous delivery. It defines release management as planning, designing, building, configuring and testing hardware and software releases. It notes that high performing IT organizations deploy code 30x more frequently with 50% fewer failures and much faster deployment times and recovery times. It emphasizes the importance of version control, automated testing, proactive monitoring, and continuous delivery in achieving these benefits. Continuous delivery is defined as proving every change can be deployed at any time. The presentation encourages automating processes to ensure all systems are always ready to go.
The document discusses building valuable RESTful APIs. It covers defining value through business models like freemium and subscription. It also discusses design best practices, including using HTTP verbs and status codes, resources, hypermedia controls, authentication, pagination, versioning, and error handling. The goal is to build APIs that are easy to use and provide value to both businesses and developers.
You're Probably Brilliant - Norfolk.js 2017 Lightning TalkGuillermo A. Fisher
This document encourages the reader that they are probably brilliant and that communication is critical to their job and career advancement. It advises the reader to practice communication skills as their job requires communication, communication will further their career, and with practice of communication skills, they can be successful. The document is signed by Guillermo A. Fisher who can be found on social media at @guillermoandrae and thanks the reader for their time.
The document discusses implementing continuous delivery for PHP applications deployed to AWS. It covers topics like using the latest stable version of PHP, solid object-oriented design principles, automated testing tools for PHP, build automation with Jenkins and Phing, application monitoring, and infrastructure automation with AWS services like EC2, RDS, and Elastic Beanstalk. Continuous delivery is presented as a solution to dysfunctional code deployments and lack of sleep by establishing automated, reliable deployment processes.
Introduction of Cybersecurity with OSS at Code Europe 2024Hiroshi SHIBATA
I develop the Ruby programming language, RubyGems, and Bundler, which are package managers for Ruby. Today, I will introduce how to enhance the security of your application using open-source software (OSS) examples from Ruby and RubyGems.
The first topic is CVE (Common Vulnerabilities and Exposures). I have published CVEs many times. But what exactly is a CVE? I'll provide a basic understanding of CVEs and explain how to detect and handle vulnerabilities in OSS.
Next, let's discuss package managers. Package managers play a critical role in the OSS ecosystem. I'll explain how to manage library dependencies in your application.
I'll share insights into how the Ruby and RubyGems core team works to keep our ecosystem safe. By the end of this talk, you'll have a better understanding of how to safeguard your code.
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.
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.
Driving Business Innovation: Latest Generative AI Advancements & Success StorySafe Software
Are you ready to revolutionize how you handle data? Join us for a webinar where we’ll bring you up to speed with the latest advancements in Generative AI technology and discover how leveraging FME with tools from giants like Google Gemini, Amazon, and Microsoft OpenAI can supercharge your workflow efficiency.
During the hour, we’ll take you through:
Guest Speaker Segment with Hannah Barrington: Dive into the world of dynamic real estate marketing with Hannah, the Marketing Manager at Workspace Group. Hear firsthand how their team generates engaging descriptions for thousands of office units by integrating diverse data sources—from PDF floorplans to web pages—using FME transformers, like OpenAIVisionConnector and AnthropicVisionConnector. This use case will show you how GenAI can streamline content creation for marketing across the board.
Ollama Use Case: Learn how Scenario Specialist Dmitri Bagh has utilized Ollama within FME to input data, create custom models, and enhance security protocols. This segment will include demos to illustrate the full capabilities of FME in AI-driven processes.
Custom AI Models: Discover how to leverage FME to build personalized AI models using your data. Whether it’s populating a model with local data for added security or integrating public AI tools, find out how FME facilitates a versatile and secure approach to AI.
We’ll wrap up with a live Q&A session where you can engage with our experts on your specific use cases, and learn more about optimizing your data workflows with AI.
This webinar is ideal for professionals seeking to harness the power of AI within their data management systems while ensuring high levels of customization and security. Whether you're a novice or an expert, gain actionable insights and strategies to elevate your data processes. Join us to see how FME and AI can revolutionize how you work with data!
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-und-domino-lizenzkostenreduzierung-in-der-welt-von-dlau/
DLAU und die Lizenzen nach dem CCB- und CCX-Modell sind für viele in der HCL-Community seit letztem Jahr ein heißes Thema. Als Notes- oder Domino-Kunde haben Sie vielleicht mit unerwartet hohen Benutzerzahlen und Lizenzgebühren zu kämpfen. Sie fragen sich vielleicht, wie diese neue Art der Lizenzierung funktioniert und welchen Nutzen sie Ihnen bringt. Vor allem wollen Sie sicherlich Ihr Budget einhalten und Kosten sparen, wo immer möglich. Das verstehen wir und wir möchten Ihnen dabei helfen!
Wir erklären Ihnen, wie Sie häufige Konfigurationsprobleme lösen können, die dazu führen können, dass mehr Benutzer gezählt werden als nötig, und wie Sie überflüssige oder ungenutzte Konten identifizieren und entfernen können, um Geld zu sparen. Es gibt auch einige Ansätze, die zu unnötigen Ausgaben führen können, z. B. wenn ein Personendokument anstelle eines Mail-Ins für geteilte Mailboxen verwendet wird. Wir zeigen Ihnen solche Fälle und deren Lösungen. Und natürlich erklären wir Ihnen das neue Lizenzmodell.
Nehmen Sie an diesem Webinar teil, bei dem HCL-Ambassador Marc Thomas und Gastredner Franz Walder Ihnen diese neue Welt näherbringen. Es vermittelt Ihnen die Tools und das Know-how, um den Überblick zu bewahren. Sie werden in der Lage sein, Ihre Kosten durch eine optimierte Domino-Konfiguration zu reduzieren und auch in Zukunft gering zu halten.
Diese Themen werden behandelt
- Reduzierung der Lizenzkosten durch Auffinden und Beheben von Fehlkonfigurationen und überflüssigen Konten
- Wie funktionieren CCB- und CCX-Lizenzen wirklich?
- Verstehen des DLAU-Tools und wie man es am besten nutzt
- Tipps für häufige Problembereiche, wie z. B. Team-Postfächer, Funktions-/Testbenutzer usw.
- Praxisbeispiele und Best Practices zum sofortigen Umsetzen
Dandelion Hashtable: beyond billion requests per second on a commodity serverAntonios Katsarakis
This slide deck presents DLHT, a concurrent in-memory hashtable. Despite efforts to optimize hashtables, that go as far as sacrificing core functionality, state-of-the-art designs still incur multiple memory accesses per request and block request processing in three cases. First, most hashtables block while waiting for data to be retrieved from memory. Second, open-addressing designs, which represent the current state-of-the-art, either cannot free index slots on deletes or must block all requests to do so. Third, index resizes block every request until all objects are copied to the new index. Defying folklore wisdom, DLHT forgoes open-addressing and adopts a fully-featured and memory-aware closed-addressing design based on bounded cache-line-chaining. This design offers lock-free index operations and deletes that free slots instantly, (2) completes most requests with a single memory access, (3) utilizes software prefetching to hide memory latencies, and (4) employs a novel non-blocking and parallel resizing. In a commodity server and a memory-resident workload, DLHT surpasses 1.6B requests per second and provides 3.5x (12x) the throughput of the state-of-the-art closed-addressing (open-addressing) resizable hashtable on Gets (Deletes).
Main news related to the CCS TSI 2023 (2023/1695)Jakub Marek
An English 🇬🇧 translation of a presentation to the speech I gave about the main changes brought by CCS TSI 2023 at the biggest Czech conference on Communications and signalling systems on Railways, which was held in Clarion Hotel Olomouc from 7th to 9th November 2023 (konferenceszt.cz). Attended by around 500 participants and 200 on-line followers.
The original Czech 🇨🇿 version of the presentation can be found here: https://www.slideshare.net/slideshow/hlavni-novinky-souvisejici-s-ccs-tsi-2023-2023-1695/269688092 .
The videorecording (in Czech) from the presentation is available here: https://youtu.be/WzjJWm4IyPk?si=SImb06tuXGb30BEH .
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.
zkStudyClub - LatticeFold: A Lattice-based Folding Scheme and its Application...Alex Pruden
Folding is a recent technique for building efficient recursive SNARKs. Several elegant folding protocols have been proposed, such as Nova, Supernova, Hypernova, Protostar, and others. However, all of them rely on an additively homomorphic commitment scheme based on discrete log, and are therefore not post-quantum secure. In this work we present LatticeFold, the first lattice-based folding protocol based on the Module SIS problem. This folding protocol naturally leads to an efficient recursive lattice-based SNARK and an efficient PCD scheme. LatticeFold supports folding low-degree relations, such as R1CS, as well as high-degree relations, such as CCS. The key challenge is to construct a secure folding protocol that works with the Ajtai commitment scheme. The difficulty, is ensuring that extracted witnesses are low norm through many rounds of folding. We present a novel technique using the sumcheck protocol to ensure that extracted witnesses are always low norm no matter how many rounds of folding are used. Our evaluation of the final proof system suggests that it is as performant as Hypernova, while providing post-quantum security.
Paper Link: https://eprint.iacr.org/2024/257
What is an RPA CoE? Session 1 – CoE VisionDianaGray10
In the first session, we will review the organization's vision and how this has an impact on the COE Structure.
Topics covered:
• The role of a steering committee
• How do the organization’s priorities determine CoE Structure?
Speaker:
Chris Bolin, Senior Intelligent Automation Architect Anika Systems
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.
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.
Your One-Stop Shop for Python Success: Top 10 US Python Development Providersakankshawande
Simplify your search for a reliable Python development partner! This list presents the top 10 trusted US providers offering comprehensive Python development services, ensuring your project's success from conception to completion.
Freshworks Rethinks NoSQL for Rapid Scaling & Cost-EfficiencyScyllaDB
Freshworks creates AI-boosted business software that helps employees work more efficiently and effectively. Managing data across multiple RDBMS and NoSQL databases was already a challenge at their current scale. To prepare for 10X growth, they knew it was time to rethink their database strategy. Learn how they architected a solution that would simplify scaling while keeping costs under control.
2. Guillermo A. Fisher
Husband, father, software engineer,
people leader, solutions architect,
continuous delivery enthusiast, writer,
AWS Data Hero.
https://bklyn.dev
@guillermoandrae
@joinHandshake
3. 757ColorCoded
We exist to educate and empower local
people of color to achieve careers in
technology and improve their lives.
https://757ColorCoded.org
https://slack.757ColorCoded.org
@757ColorCoded
6. Waterfall is a project management
approach where a project is
completed in distinct stages and
moved step by step toward
ultimate release to consumers.
“
7.
8. Major Disadvantages of Waterfall
All requirements must be known prior to development
There is little to no room for change
The customer only sees the finished product
12. Agile software development is an
approach to software development
under which requirements and
solutions evolve through the
collaborative effort of self-organizing
and cross-functional teams and
their customer(s)/end user(s).
“
13. Major Benefits of Agile Development
Ability to manage changing priorities
Project visibility
Business/IT alignment
Team morale
Delivery time
18. Scrum is a framework within which
people can address complex
adaptive problems, while
productively and creatively
delivering products of the highest
possible value.
“
23. Artifact: Sprint Backlog
Work from the Product Backlog selected for Sprint
Represents the work associated with the Increment
Managed by the Scrum Team
28. Events: The Sprint
Time-boxed event during which the Increment is created
Scrum Team commits to a Sprint Goal
Managed by the Product Owner and Scrum Team
29. Events: Sprint Planning
Time-boxed event wherein the plan for the Sprint is created
What can be delivered in the Increment resulting from the
upcoming Sprint?
How will the work needed to deliver the Increment be
achieved?
30. Events: Daily Scrum (Standup)
Time-boxed (15 minute) meeting held daily
What did I do yesterday?
What will I do today?
Do I see any impediment?
31. Events: Sprint Review
Time-boxed event wherein the Increment is inspected
Product Owner explains what has been completed
Review of timeline, budget, marketplace
Scrum Team demonstrates work
32. Events: Sprint Retrospective
Time-boxed event wherein the Scrum Team inspects itself
How did the Sprint go with regards to people,
relationships, processes, tools?
What went well? What didn’t go well?
Create a plan to make improvements
33. Events: Backlog Grooming/Refinement
The act of adding detail, estimates, and order to items in
the Product Backlog
Ongoing process
Consumes no more than 10% of the Scrum Team’s
capacity
37. The Wild Rydes App
In today’s fast paced world, you’ve got places you need to
be but not enough time in your jam packed schedule.
Wouldn’t it be nice if there were a transportation service
that changed the way you get around daily? Introducing
Wild Rydes, an innovative transportation service that helps
people get to their destination faster and hassle-free.
Getting started is as easy as tapping a button in our app.