Similar Group - Development Team Management Principals
•
0 likes•676 views
This is the pitch I gave my new team at Similar Group. It describes the things that matters in a modern development team.
Report
Share
Report
Share
Download to read offline
Recommended
Agile brazil2013poised
The document discusses business agility and how to achieve it through continuous experimentation, rapid feedback, and keeping systems poised for change. It outlines factors like agile software development principles, internal software quality measures, evolutionary architecture principles, and continuous delivery practices. These help lower the cost and risk of experimentation while maximizing visibility and feedback. The goal is for the business to be agile through experimenting often, being prepared to change quickly yet safely, and relying on evidence over guesses to balance predictability and opportunities.
Effective Agile Metrics, Cuneyt Gul
The document discusses effective agile metrics. It begins by explaining why metrics are important for continuous improvement, and provides examples of good and bad metrics to track. The document then discusses different types of metrics like key performance indicators and how to measure teams and processes, not individuals. It provides examples of metrics that can be collected from project tracking systems, source control, continuous integration/delivery, and application monitoring. Finally, it shares SBM's approach to agile performance measurement including metrics at the team and individual level.
Scrum and Kanban guide
Scrum & Kanban in nutshell, template is useful for small team with any collaboration tools. Scrum masters products owners & agile teams can use this tool/template for better collaboration. intention are to spread agile awareness. please maintain the santity. this should be used as commercial gains. This template are results of empiricism culture initiated by experts in the agile sector.
The DevOps Challenge - Red Hat DevOps & Microservices Conference 2017
The document discusses the challenges of traditional software development organizations versus a DevOps approach. It outlines how typical organizations separate development, testing, release and operations into silos, which can lead to delays, rework and failures. DevOps aims to break down these silos through practices like continuous integration, delivery and deployment, automation, shared code/configuration, and improved collaboration between development and operations teams. The goal is to increase efficiency, productivity, quality and speed of delivering software through an organizational transformation focused on people, processes and technology. It provides an overview of DevOps principles and emphasizes that successful adoption is an incremental journey that requires building skills, momentum and a collaborative culture over time.
Enterprise feature streams
From Value Stream Management to Feature Stream Enablement
- The tech and tools don't matter (Use the in-place toolchain...Jira, Jenkins & Github...)
- The process and methodology that work best for you (Agile, Scrum, Kanban, Lean, XP, Waterfall...)
- Teams can finally see work with full transparency (full-stream, full-stack, full-flow...all tied to KPIs and OKRs)
Enabling Continuous Delivery
The document discusses continuous application delivery (CAD) and how DevOps principles enable it. It describes breaking down silos, automating processes, and collaborating as a unified team. The CAD maturity model scores organizations on agile delivery practices like continuous integration, automated testing, and self-service tools. Highly mature organizations implement patterns like trunk-based development, automated testing and deployment, and decoupling database changes.
Devops
DevOps aims to solve challenges faced by traditional waterfall and agile development models. It promotes collaboration between development and operations teams through shared tools and workflows. Benefits of DevOps include increased speed and frequency of releases, improved collaboration across teams, and continuous quality assurance through monitoring of deployed software. Many large companies have adopted DevOps practices.
DEV ops for sap
In today’s competitive business landscape, leaders are constantly striving to innovate to deliver value and increase effectiveness. This calls for the need for agile enterprise software solutions that can help businesses to support these goals by adapting and responding safely to rapid and frequent change. So, if you wish to deliver value to your customers while being a part of a revved-up organization that prospers in a fast-paced digital economy then embracing DevOps for SAP makes sense.
Recommended
Agile brazil2013poised
The document discusses business agility and how to achieve it through continuous experimentation, rapid feedback, and keeping systems poised for change. It outlines factors like agile software development principles, internal software quality measures, evolutionary architecture principles, and continuous delivery practices. These help lower the cost and risk of experimentation while maximizing visibility and feedback. The goal is for the business to be agile through experimenting often, being prepared to change quickly yet safely, and relying on evidence over guesses to balance predictability and opportunities.
Effective Agile Metrics, Cuneyt Gul
The document discusses effective agile metrics. It begins by explaining why metrics are important for continuous improvement, and provides examples of good and bad metrics to track. The document then discusses different types of metrics like key performance indicators and how to measure teams and processes, not individuals. It provides examples of metrics that can be collected from project tracking systems, source control, continuous integration/delivery, and application monitoring. Finally, it shares SBM's approach to agile performance measurement including metrics at the team and individual level.
Scrum and Kanban guide
Scrum & Kanban in nutshell, template is useful for small team with any collaboration tools. Scrum masters products owners & agile teams can use this tool/template for better collaboration. intention are to spread agile awareness. please maintain the santity. this should be used as commercial gains. This template are results of empiricism culture initiated by experts in the agile sector.
The DevOps Challenge - Red Hat DevOps & Microservices Conference 2017
The document discusses the challenges of traditional software development organizations versus a DevOps approach. It outlines how typical organizations separate development, testing, release and operations into silos, which can lead to delays, rework and failures. DevOps aims to break down these silos through practices like continuous integration, delivery and deployment, automation, shared code/configuration, and improved collaboration between development and operations teams. The goal is to increase efficiency, productivity, quality and speed of delivering software through an organizational transformation focused on people, processes and technology. It provides an overview of DevOps principles and emphasizes that successful adoption is an incremental journey that requires building skills, momentum and a collaborative culture over time.
Enterprise feature streams
From Value Stream Management to Feature Stream Enablement
- The tech and tools don't matter (Use the in-place toolchain...Jira, Jenkins & Github...)
- The process and methodology that work best for you (Agile, Scrum, Kanban, Lean, XP, Waterfall...)
- Teams can finally see work with full transparency (full-stream, full-stack, full-flow...all tied to KPIs and OKRs)
Enabling Continuous Delivery
The document discusses continuous application delivery (CAD) and how DevOps principles enable it. It describes breaking down silos, automating processes, and collaborating as a unified team. The CAD maturity model scores organizations on agile delivery practices like continuous integration, automated testing, and self-service tools. Highly mature organizations implement patterns like trunk-based development, automated testing and deployment, and decoupling database changes.
Devops
DevOps aims to solve challenges faced by traditional waterfall and agile development models. It promotes collaboration between development and operations teams through shared tools and workflows. Benefits of DevOps include increased speed and frequency of releases, improved collaboration across teams, and continuous quality assurance through monitoring of deployed software. Many large companies have adopted DevOps practices.
DEV ops for sap
In today’s competitive business landscape, leaders are constantly striving to innovate to deliver value and increase effectiveness. This calls for the need for agile enterprise software solutions that can help businesses to support these goals by adapting and responding safely to rapid and frequent change. So, if you wish to deliver value to your customers while being a part of a revved-up organization that prospers in a fast-paced digital economy then embracing DevOps for SAP makes sense.
Realize the opportunity - with DevOps
This document discusses realizing opportunities through adopting DevOps practices. It poses the question "What if projects realized business objectives regarding objectives, time, quality and cost?" It also questions what if transitions from concept to reality were collaborative, if projects were truly agile and requirements changes easily integrated, and if development and testing happened seamlessly. Adopting DevOps could help ensure projects are on budget and time, quality is consistently high, projects can be quickly deployed, and applications continuously meet customer expectations.
Shift Left Quality Assurance: How to do it. Why it matters.
Shift Left Quality Assurance was originally presented by Mark Summers in a Webinar hosted by Worksoft in September 2015.
Continuous Delivery at DEK Technologies
The document discusses how DEK Technologies helps clients establish a continuous delivery pipeline to rapidly develop and deploy software. This involves applying agile and lean principles to streamline processes, automate tasks, integrate steps, and create feedback loops. Services include value stream mapping, improving culture, configuration management, infrastructure management, automated testing, and zero-downtime releases. The goal is to allow software to be developed to high standards, easily packaged and deployed to test environments, enabling frequent, reliable releases to customers.
Agile at Salesforce From theory to practice, how to be agile at scale
Talk given by Pitch Chevalier, Director of SW Engineering, Search, at Salesforce, at Agile Grenoble 2015.
The story of Agile at Salesforce started in 2006 when the engineering teams were facing several blockers, delays and quality issues. The adoption of an agile methodology inspired by scrum, common to all teams, backed by senior management, lead to having shorter and predictable development cycles with three releases per year, deployed to all customers. The approach had a big focus on initiative and autonomy giving teams all latitude. It was key to the adoption and the agile transformation.
In order to support this new organization based on a large number of small teams, working independently, distributed across sites and different locations, a set of common agile tools was being deployed allowing teams to manage their projects, their delivery artifacts and more important to collaborate seamlessly.
This talk starts with a high-level description of the ADM (Agile Development Methodology), lessons learned and issues to overcome. It might even point to new issues that remain to be addressed. The second part of the presentation showcases the Salesforce Agile Accelerator, that can also be used by our customers.
Simple Lean Agile KPIs
This document discusses key performance indicators (KPIs) for measuring productivity, effectiveness, predictability, reliability, and business agility in network, application, server, and development groups. It maps traditional KPI areas like throughput, effectiveness, response time, and quality to Agile metrics like velocity, cycle time, lead time, variability, and defects. Specific Agile KPIs discussed include throughput/velocity, lead time/cycle time, predictability through meeting commitments and reducing variability, effectiveness through cost/operating expense, and release overhead. The document recommends starting KPI measurement without fully adopting Agile and provides examples of using Kanban to track metrics.
The philosophy of continuous deployment
Presentation given to Sydney Tech Leaders Meetup 11-June-2015.
Focuses on behaviours and culture change that is required within the delivery team and throughout the enterprise to assist and complement the technical capability of the organisation.
A paradigm shift for testing - how to increase productivity 10x!
European IT industry need to deal with a huge salary gap with developing countries.
How can we increase our productivity and quality to compensate for the salary differences? This is a systems-thinking / Lean based approach to that problem
Salesforce1 ELEVATE Workshop - Dublin
Hands-on experience building a complete app in a day without the need to learn a programming language
Agile Process Audit
This document discusses conducting an agile process audit. It outlines common problems with software projects like cost overruns and quality issues. Agile methodologies are presented as a solution. The benefits of a process audit are described as providing insight and identifying areas for improvement. The document details what aspects are audited, such as team distractions and bugs. Sample findings around these issues are presented along with recommendations and benefits of addressing the findings. Guiding principles of eliminating waste, being people-centric, and optimizing across the organization are also shared.
Scrum at Scale
Salesforce.com is an enterprise Cloud Computing Leader that specializes in Software as a Service. With several hundred teams working on our diverse product suite, releasing three times a year is not an easy endeavor. Our Agile processes are the key to our success. In this deck, learn the 5 fundamental elements of our successful enterprise implementation of Agile software development methodologies.
DevOps Swim Lanes - Silo Org Change Challenges
The document compares the traditional waterfall model and siloed approach to development (IT) with the DevOps approach. With waterfall and silos, components were developed and managed in isolation by specialist teams, which led to quality issues, delays, and lack of collaboration between teams. DevOps embraces a collaborative culture with shared goals and optimized system flows between development, operations, and other functions. This approach leverages practices like automation, cloud technologies, and continuous integration/delivery to allow for faster innovation and higher quality through greater transparency, accountability, and opportunities for feedback and improvement.
Adaptive Development Methodology
The document provides an overview of the Adaptive Development Methodology (ADM), which is a modified Scrum/XP approach used specifically for product development at Salesforce. It describes key aspects of ADM including principles like iterative development, transparency, and eliminating waste. It also outlines roles, ceremonies, and artifacts of the Scrum framework that ADM is based on such as sprints, daily stand-ups, product backlogs, and sprint planning.
8 tips for successful change management
Change management can be one of the most challenging parts of implementing a new system. Employees are resistant to adopt, but getting them on board is crucial. We give you 8 tips that will help to make the transition a little easier.
Pooja shift left 1.0
Agile testing challenges
Shift Left: What, Why and How
Benefits of Shift Left testing
Case Study
DevOps feedback loops
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.
DevOps Maturity Curve v5
What does a Maturity Curve for Enterprise Adoption of Agile and DevOps look like? Where would an organization like yours rank on the curve? Are there specific areas of improvement you might want to consider?
sitHH16 - The Implications of Becoming Agile
Slides from my talk about the not so obvious changes that occur when change from waterfall to agile software development with Scrum. A review on the past three years in an agile transition.
Dev ops.enterprise.2014 (1)
The document discusses quality engineering (QE) and its role in a DevOps transformation at Salesforce. QE is involved at all stages of development to prevent issues. They work closely with developers, operations, security and other teams. The goal is to build quality into the product from the start and make quality everyone's responsibility, not just testing. A DevOps culture with strong QE collaboration can deliver high quality services to customers.
Tomas Butkus: Agile Practices in Enterprise Environment
The document discusses introducing and using agile practices in a large enterprise environment. It describes the presenter's organization, which has 145,000 employees worldwide and distributed project teams across locations. While the traditional waterfall process provides discipline, requirements often change and integration is complicated. The presentation explores how agile could benefit the organization through iterative deliveries, continuous feedback, and flexibility. A case study is presented of a distributed team that used practices like limiting work in progress, Kanban boards, test-driven development, and daily standups, which resulted in on-time and on-budget delivery with higher quality and functionality. Future challenges discussed include tailoring agile for offshore teams and aligning with constraints of mission critical systems.
DevOps
The document describes an Enterprise DevOps Open Scale Framework (EDOSF) that helps integrate various technology and process frameworks like Agile, DevOps, ITIL, and Kanban. The framework acts as a facilitator for tools and business processes, establishes open communication across teams, and allows real-time views of business and IT services through customizable dashboards for problem monitoring and resolution.
Shift Left - Approach and practices with IBM
"Shift Left" is a DevOps practice that provides an effective means to perform testing with or in parallel to development activities.
When shifting left, development, test and operations work together to plan, manage and execute automated and continuous testing to accelerate feedback to developers and improve the quality of changes early in the life-cycle. The rate of the accelerated feedback is determined by an organization’s desired outcomes for velocity of changes and capacity for feedback.
Software Quality Assurance
The document provides an overview of an SQA workshop on quality and process concepts. It discusses quality models, the SQA role, and audit systems. Key topics covered include quality definitions, quality gurus, total quality management, process management, industry quality models like ISO 9001 and CMMI, quality system elements, and the purpose and types of audits.
More Related Content
What's hot
Realize the opportunity - with DevOps
This document discusses realizing opportunities through adopting DevOps practices. It poses the question "What if projects realized business objectives regarding objectives, time, quality and cost?" It also questions what if transitions from concept to reality were collaborative, if projects were truly agile and requirements changes easily integrated, and if development and testing happened seamlessly. Adopting DevOps could help ensure projects are on budget and time, quality is consistently high, projects can be quickly deployed, and applications continuously meet customer expectations.
Shift Left Quality Assurance: How to do it. Why it matters.
Shift Left Quality Assurance was originally presented by Mark Summers in a Webinar hosted by Worksoft in September 2015.
Continuous Delivery at DEK Technologies
The document discusses how DEK Technologies helps clients establish a continuous delivery pipeline to rapidly develop and deploy software. This involves applying agile and lean principles to streamline processes, automate tasks, integrate steps, and create feedback loops. Services include value stream mapping, improving culture, configuration management, infrastructure management, automated testing, and zero-downtime releases. The goal is to allow software to be developed to high standards, easily packaged and deployed to test environments, enabling frequent, reliable releases to customers.
Agile at Salesforce From theory to practice, how to be agile at scale
Talk given by Pitch Chevalier, Director of SW Engineering, Search, at Salesforce, at Agile Grenoble 2015.
The story of Agile at Salesforce started in 2006 when the engineering teams were facing several blockers, delays and quality issues. The adoption of an agile methodology inspired by scrum, common to all teams, backed by senior management, lead to having shorter and predictable development cycles with three releases per year, deployed to all customers. The approach had a big focus on initiative and autonomy giving teams all latitude. It was key to the adoption and the agile transformation.
In order to support this new organization based on a large number of small teams, working independently, distributed across sites and different locations, a set of common agile tools was being deployed allowing teams to manage their projects, their delivery artifacts and more important to collaborate seamlessly.
This talk starts with a high-level description of the ADM (Agile Development Methodology), lessons learned and issues to overcome. It might even point to new issues that remain to be addressed. The second part of the presentation showcases the Salesforce Agile Accelerator, that can also be used by our customers.
Simple Lean Agile KPIs
This document discusses key performance indicators (KPIs) for measuring productivity, effectiveness, predictability, reliability, and business agility in network, application, server, and development groups. It maps traditional KPI areas like throughput, effectiveness, response time, and quality to Agile metrics like velocity, cycle time, lead time, variability, and defects. Specific Agile KPIs discussed include throughput/velocity, lead time/cycle time, predictability through meeting commitments and reducing variability, effectiveness through cost/operating expense, and release overhead. The document recommends starting KPI measurement without fully adopting Agile and provides examples of using Kanban to track metrics.
The philosophy of continuous deployment
Presentation given to Sydney Tech Leaders Meetup 11-June-2015.
Focuses on behaviours and culture change that is required within the delivery team and throughout the enterprise to assist and complement the technical capability of the organisation.
A paradigm shift for testing - how to increase productivity 10x!
European IT industry need to deal with a huge salary gap with developing countries.
How can we increase our productivity and quality to compensate for the salary differences? This is a systems-thinking / Lean based approach to that problem
Salesforce1 ELEVATE Workshop - Dublin
Hands-on experience building a complete app in a day without the need to learn a programming language
Agile Process Audit
This document discusses conducting an agile process audit. It outlines common problems with software projects like cost overruns and quality issues. Agile methodologies are presented as a solution. The benefits of a process audit are described as providing insight and identifying areas for improvement. The document details what aspects are audited, such as team distractions and bugs. Sample findings around these issues are presented along with recommendations and benefits of addressing the findings. Guiding principles of eliminating waste, being people-centric, and optimizing across the organization are also shared.
Scrum at Scale
Salesforce.com is an enterprise Cloud Computing Leader that specializes in Software as a Service. With several hundred teams working on our diverse product suite, releasing three times a year is not an easy endeavor. Our Agile processes are the key to our success. In this deck, learn the 5 fundamental elements of our successful enterprise implementation of Agile software development methodologies.
DevOps Swim Lanes - Silo Org Change Challenges
The document compares the traditional waterfall model and siloed approach to development (IT) with the DevOps approach. With waterfall and silos, components were developed and managed in isolation by specialist teams, which led to quality issues, delays, and lack of collaboration between teams. DevOps embraces a collaborative culture with shared goals and optimized system flows between development, operations, and other functions. This approach leverages practices like automation, cloud technologies, and continuous integration/delivery to allow for faster innovation and higher quality through greater transparency, accountability, and opportunities for feedback and improvement.
Adaptive Development Methodology
The document provides an overview of the Adaptive Development Methodology (ADM), which is a modified Scrum/XP approach used specifically for product development at Salesforce. It describes key aspects of ADM including principles like iterative development, transparency, and eliminating waste. It also outlines roles, ceremonies, and artifacts of the Scrum framework that ADM is based on such as sprints, daily stand-ups, product backlogs, and sprint planning.
8 tips for successful change management
Change management can be one of the most challenging parts of implementing a new system. Employees are resistant to adopt, but getting them on board is crucial. We give you 8 tips that will help to make the transition a little easier.
Pooja shift left 1.0
Agile testing challenges
Shift Left: What, Why and How
Benefits of Shift Left testing
Case Study
DevOps feedback loops
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.
DevOps Maturity Curve v5
What does a Maturity Curve for Enterprise Adoption of Agile and DevOps look like? Where would an organization like yours rank on the curve? Are there specific areas of improvement you might want to consider?
sitHH16 - The Implications of Becoming Agile
Slides from my talk about the not so obvious changes that occur when change from waterfall to agile software development with Scrum. A review on the past three years in an agile transition.
Dev ops.enterprise.2014 (1)
The document discusses quality engineering (QE) and its role in a DevOps transformation at Salesforce. QE is involved at all stages of development to prevent issues. They work closely with developers, operations, security and other teams. The goal is to build quality into the product from the start and make quality everyone's responsibility, not just testing. A DevOps culture with strong QE collaboration can deliver high quality services to customers.
Tomas Butkus: Agile Practices in Enterprise Environment
The document discusses introducing and using agile practices in a large enterprise environment. It describes the presenter's organization, which has 145,000 employees worldwide and distributed project teams across locations. While the traditional waterfall process provides discipline, requirements often change and integration is complicated. The presentation explores how agile could benefit the organization through iterative deliveries, continuous feedback, and flexibility. A case study is presented of a distributed team that used practices like limiting work in progress, Kanban boards, test-driven development, and daily standups, which resulted in on-time and on-budget delivery with higher quality and functionality. Future challenges discussed include tailoring agile for offshore teams and aligning with constraints of mission critical systems.
DevOps
The document describes an Enterprise DevOps Open Scale Framework (EDOSF) that helps integrate various technology and process frameworks like Agile, DevOps, ITIL, and Kanban. The framework acts as a facilitator for tools and business processes, establishes open communication across teams, and allows real-time views of business and IT services through customizable dashboards for problem monitoring and resolution.
What's hot (20)
Shift Left Quality Assurance: How to do it. Why it matters.
Shift Left Quality Assurance: How to do it. Why it matters.
Agile at Salesforce From theory to practice, how to be agile at scale
Agile at Salesforce From theory to practice, how to be agile at scale
A paradigm shift for testing - how to increase productivity 10x!
A paradigm shift for testing - how to increase productivity 10x!
Tomas Butkus: Agile Practices in Enterprise Environment
Tomas Butkus: Agile Practices in Enterprise Environment
Similar to Similar Group - Development Team Management Principals
Shift Left - Approach and practices with IBM
"Shift Left" is a DevOps practice that provides an effective means to perform testing with or in parallel to development activities.
When shifting left, development, test and operations work together to plan, manage and execute automated and continuous testing to accelerate feedback to developers and improve the quality of changes early in the life-cycle. The rate of the accelerated feedback is determined by an organization’s desired outcomes for velocity of changes and capacity for feedback.
Software Quality Assurance
The document provides an overview of an SQA workshop on quality and process concepts. It discusses quality models, the SQA role, and audit systems. Key topics covered include quality definitions, quality gurus, total quality management, process management, industry quality models like ISO 9001 and CMMI, quality system elements, and the purpose and types of audits.
Quality Assurance Comparison in Traditional and Agile Methodologies
This document compares quality assurance techniques between traditional and agile software development methodologies. It discusses the limitations of traditional waterfall models and agile methods. Traditional methods emphasize well-defined requirements and documentation, while agile prioritizes working software through short iterations with frequent customer feedback. Both approaches aim to ensure quality, but agile relies more on practices like refactoring, test-driven development, and continuous integration throughout the development cycle. In conclusion, agile may better facilitate quality by starting testing earlier and more frequently integrating customer input.
DevOps
This document discusses DevOps frameworks and principles. It outlines that as customer needs have become more complex, development teams have evolved their practices to be more flexible and agile. This has blurred the lines between traditional development and operations teams. DevOps aims to make organizations more efficient by integrating tools, processes, and guidelines. It provides a flexible environment that facilitates success. To implement DevOps successfully, organizations should perform due diligence, define processes tailored to their needs, select appropriate tools, establish KPIs, and provide best practices and examples.
Lean Agile Metrics And KPIs
Summary of some Lean/Agile metrics and KPIs, as well as some elaboration of key metrics and case studies on this subject
Agile principles and mindset agile wednesday series
Jamey is a project catalyst for motivation and believes project success starts with team confidence. He has directed / managed project portfolios up to $200 million and portfolios as low as 1/2 million dollars in funding. Being a lifelong learning, it was the smaller projects where he learned he has an innate ability to find the right balance between people and process to obtain the team’s innovation hidden talents. Leveraging his unwavering determination, he has successfully implemented projects with company-wide impacts involving ~700 stakeholders.
Jamey is an Iowa native, graduated from Iowa State University, and certified in Agile Certified Practitioner (PMI-ACP), Certified Scrum Master (CSM), Project Management Professional (PMP) and, IT Infrastructure Library (ITIL). He is an active PMI member of the PMI Washington DC chapter.
How to build Rome in a day
The document describes an organization's transformation to becoming more agile. It discusses the moments of ignorance, truth, action, learning, and attainment. It outlines changes made such as adopting agile practices, implementing CI/CD pipelines, automating testing, using a single backlog tool, and focusing on customer experience. It also discusses lessons learned around change management and the need to consider the full customer journey. The organization continued improving by building feature teams, investing in automation, and focusing on employee experience. The transformation resulted in higher velocity, quality, and employee satisfaction.
Agile webinar pack (2)
This document discusses the differences between waterfall and agile development approaches for SAP projects. It notes that it is not an "either/or" debate, as both approaches have advantages and neither is suitable for all situations. The document outlines some of the benefits of each approach, such as shorter time to market with agile but more extensive testing and change management with waterfall. It then discusses five fundamentals for becoming more agile with SAP: creating an enabling environment, building an agile development model, using smart bundling strategies, automating processes and shifting testing left, and focusing on culture change.
Dev ops as a service
This document provides an overview of DevOps consulting services, including:
- DevOps improves innovation, reduces risks, and speeds up time to market by making it safer to experiment and releasing features faster.
- The consulting services include DevOps assessments, workshops to align stakeholders, value stream mapping, training, and implementing a DevOps pipeline with continuous integration, testing, and deployment.
- The process begins with workshops to define a vision, assess maturity, identify value streams, and map the current process. Then DevOps is piloted on selected value streams through implementing improvements from a transformation backlog.
Notes on agile
Agile testing is a software testing practice that follows the principles of agile software development. In agile testing, testing is continuous and occurs throughout the development process rather than as a separate phase. All team members, including developers and business analysts, are involved in testing. Feedback is provided frequently in short iterations to quickly adapt to changing requirements. This allows issues to be identified and addressed earlier compared to traditional waterfall development models.
Webinar - Design Thinking for Platform Engineering
This document discusses approaching platform engineering with a design thinking mindset. It begins by outlining challenges with existing approaches, such as tools being difficult to use and responsibilities being blurred. It then defines platform engineering and describes design thinking, which integrates user needs, technology possibilities, and business requirements. The design thinking process involves empathizing with users to gain insights, defining opportunities, ideating solutions, prototyping ideas, and testing assumptions. The document argues that applying a human-centered design thinking approach helps focus on outcomes rather than just technology, surfaces conflicts, identifies new opportunities, and involves frequent testing with users. It concludes by recommending getting started with design thinking for platform engineering by identifying and prioritizing problems, engaging stakeholders
Innovative Engineering Workshop Npi 30march10
AESSiS is an engineering consultancy that specializes in product lifecycle management (PLM) implementation and process improvement to help manufacturing businesses achieve better performance. PLM is a strategic approach to managing product information throughout the lifecycle from concept to end of life. It aims to provide a single source of truth, configuration management, reduced waste, and increased innovation. PLM tools help manage parts, relationships between parts, documents, changes to parts, and the lifecycle of a part from new to obsolete. Aras is an open source PLM platform that provides an enterprise solution with no upfront costs and uses existing IT infrastructure and skills.
Using Lean Thinking to identify and address Delivery Pipeline bottlenecks
Using Lean Thinking to identify and address Delivery Pipeline bottlenecks discusses applying Lean principles to accelerate feedback and improve time to value across the development, testing, and production stages. It identifies common bottlenecks like deploying infrastructure and provides examples of how adopting DevOps practices like continuous delivery can help optimize pipelines and flow of work. The document advocates mapping bottlenecks and implementing solutions like capturing infrastructure as code to enable faster, more reliable application deployments.
Agile methodology v 4.5 s
This document provides an overview of agile methodology compared to traditional waterfall methodology. It discusses that agile is more suitable for new product development where requirements are evolving, while waterfall is better for maintaining mature systems. Agile focuses on quick iterations, customer involvement, and frequent releases to adapt to changes. Though agile has less formal processes than waterfall, it still includes change control and quality assurance. The roles and responsibilities in agile include business analysts to define requirements, architects to design solutions, developers to build code, testers to validate quality, and project managers to deliver projects on schedule and budget.
Kanban : optimising for predictability
How to turn small tasks into a predictable flow of deliverables and use lean principles to experiment, measure and learn in the process.
Lean Thinking Inside and Outside a Software Engineering Company (Dave Jackson)
In this series of talks, our panel of experts present real world examples that illustrate how Lean Production concepts are being successfully applied to software development. In particular to applications that have to meet the highest levels of safety and security.
Lessons from DevOps: Taking DevOps practices into your AppSec Life
Bruce Lee once said “Don’t get set into one form, adapt it and build your own, and let it grow, be like water“.
AppSec needs to look beyond itself for answers to solving problems since we live in a world of every increasing numbers of apps. Technology and apps have invaded our lives, so how to you lead a security counter-insurgency? One way is to look at the key tenants of DevOps and apply those that make sense to your approach to AppSec. Something has to change as the application landscape is already changing around us.
Software Project Health Check: Best Practices and Techniques for Your Product...
While you’re working on your software project, there’s, unfortunately, no guarantee that it won’t go over your budget limits, ruin the deadlines, or fail to meet expectations. Even if you can’t have a magic pill to avoid these, you can conduct health checks to ensure the development goes as planned.
To help you with that, we held a webinar that sheds light on how to take care of a software product and align it with initial goals. Our expert, who has years of background in the relevant field, shares lots of practical knowledge for effective tech product delivery.
What do we talk about in particular?
- Industry practices to track project progress
- Dynamical adjustments of functionality
- Aligning customizations with the roadmap
- Automated testing as part of a health check
- Dashboards for effective communication
- Technical debt and its role in your project
You can find all this in our on-demand webinar: https://www.velvetech.com/events/software-project-health-check/
Doors Change
The document discusses Telelogic DOORS and Telelogic Change software for requirements management and change management. Key points:
1. Telelogic DOORS allows visual definition of requirements, management of changes, and traceability between requirements and tests/design/metrics. Telelogic Change provides a workflow for managing changes to requirements.
2. Telelogic Change allows users to implement their own change management process or use out-of-the-box best practices. It provides traceability between requirements and development activities.
3. The software provides customizable workflows for lifecycle change management, reporting and metrics, and managing distributed teams. It integrates with other Telelogic products for requirements-driven development.
Testing Framework
The document provides an overview of building a quality testing framework. It discusses setting goals, defining a vision and timeline, establishing processes and roadmaps, gaining acceptance, and making improvements. Key aspects include test planning, case design, defect management, metrics, involvement of QA early, and continuous improvement. The overall message is that quality assurance principles applied throughout the development and testing process can help prevent bugs and ensure high quality work.
Similar to Similar Group - Development Team Management Principals (20)
Quality Assurance Comparison in Traditional and Agile Methodologies
Quality Assurance Comparison in Traditional and Agile Methodologies
Agile principles and mindset agile wednesday series
Agile principles and mindset agile wednesday series
Webinar - Design Thinking for Platform Engineering
Webinar - Design Thinking for Platform Engineering
Using Lean Thinking to identify and address Delivery Pipeline bottlenecks
Using Lean Thinking to identify and address Delivery Pipeline bottlenecks
Lean Thinking Inside and Outside a Software Engineering Company (Dave Jackson)
Lean Thinking Inside and Outside a Software Engineering Company (Dave Jackson)
Lessons from DevOps: Taking DevOps practices into your AppSec Life
Lessons from DevOps: Taking DevOps practices into your AppSec Life
Software Project Health Check: Best Practices and Techniques for Your Product...
Software Project Health Check: Best Practices and Techniques for Your Product...
Recently uploaded
Enchancing adoption of Open Source Libraries. A case study on Albumentations.AI
Enchancing adoption of Open Source Libraries. A case study on Albumentations.AIVladimir Iglovikov, Ph.D.
Presented by Vladimir Iglovikov:
- https://www.linkedin.com/in/iglovikov/
- https://x.com/viglovikov
- https://www.instagram.com/ternaus/
This presentation delves into the journey of Albumentations.ai, a highly successful open-source library for data augmentation.
Created out of a necessity for superior performance in Kaggle competitions, Albumentations has grown to become a widely used tool among data scientists and machine learning practitioners.
This case study covers various aspects, including:
People: The contributors and community that have supported Albumentations.
Metrics: The success indicators such as downloads, daily active users, GitHub stars, and financial contributions.
Challenges: The hurdles in monetizing open-source projects and measuring user engagement.
Development Practices: Best practices for creating, maintaining, and scaling open-source libraries, including code hygiene, CI/CD, and fast iteration.
Community Building: Strategies for making adoption easy, iterating quickly, and fostering a vibrant, engaged community.
Marketing: Both online and offline marketing tactics, focusing on real, impactful interactions and collaborations.
Mental Health: Maintaining balance and not feeling pressured by user demands.
Key insights include the importance of automation, making the adoption process seamless, and leveraging offline interactions for marketing. The presentation also emphasizes the need for continuous small improvements and building a friendly, inclusive community that contributes to the project's growth.
Vladimir Iglovikov brings his extensive experience as a Kaggle Grandmaster, ex-Staff ML Engineer at Lyft, sharing valuable lessons and practical advice for anyone looking to enhance the adoption of their open-source projects.
Explore more about Albumentations and join the community at:
GitHub: https://github.com/albumentations-team/albumentations
Website: https://albumentations.ai/
LinkedIn: https://www.linkedin.com/company/100504475
Twitter: https://x.com/albumentationsIntroducing Milvus Lite: Easy-to-Install, Easy-to-Use vector database for you...
Join us to introduce Milvus Lite, a vector database that can run on notebooks and laptops, share the same API with Milvus, and integrate with every popular GenAI framework. This webinar is perfect for developers seeking easy-to-use, well-integrated vector databases for their GenAI apps.
みなさんこんにちはこれ何文字まで入るの？40文字以下不可とか本当に意味わからないけどこれ限界文字数書いてないからマジでやばい文字数いけるんじゃないの？えこ...
ここ3000字までしか入らないけどタイトルの方がたくさん文字入ると思います。
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdf
Monitoring and observability aren’t traditionally found in software curriculums and many of us cobble this knowledge together from whatever vendor or ecosystem we were first introduced to and whatever is a part of your current company’s observability stack.
While the dev and ops silo continues to crumble….many organizations still relegate monitoring & observability as the purview of ops, infra and SRE teams. This is a mistake - achieving a highly observable system requires collaboration up and down the stack.
I, a former op, would like to extend an invitation to all application developers to join the observability party will share these foundational concepts to build on:
20240607 QFM018 Elixir Reading List May 2024
Everything I found interesting about the Elixir programming ecosystem in May 2024
Removing Uninteresting Bytes in Software Fuzzing
Imagine a world where software fuzzing, the process of mutating bytes in test seeds to uncover hidden and erroneous program behaviors, becomes faster and more effective. A lot depends on the initial seeds, which can significantly dictate the trajectory of a fuzzing campaign, particularly in terms of how long it takes to uncover interesting behaviour in your code. We introduce DIAR, a technique designed to speedup fuzzing campaigns by pinpointing and eliminating those uninteresting bytes in the seeds. Picture this: instead of wasting valuable resources on meaningless mutations in large, bloated seeds, DIAR removes the unnecessary bytes, streamlining the entire process.
In this work, we equipped AFL, a popular fuzzer, with DIAR and examined two critical Linux libraries -- Libxml's xmllint, a tool for parsing xml documents, and Binutil's readelf, an essential debugging and security analysis command-line tool used to display detailed information about ELF (Executable and Linkable Format). Our preliminary results show that AFL+DIAR does not only discover new paths more quickly but also achieves higher coverage overall. This work thus showcases how starting with lean and optimized seeds can lead to faster, more comprehensive fuzzing campaigns -- and DIAR helps you find such seeds.
- These are slides of the talk given at IEEE International Conference on Software Testing Verification and Validation Workshop, ICSTW 2022.
Goodbye Windows 11: Make Way for Nitrux Linux 3.5.0!
As the digital landscape continually evolves, operating systems play a critical role in shaping user experiences and productivity. The launch of Nitrux Linux 3.5.0 marks a significant milestone, offering a robust alternative to traditional systems such as Windows 11. This article delves into the essence of Nitrux Linux 3.5.0, exploring its unique features, advantages, and how it stands as a compelling choice for both casual users and tech enthusiasts.
Alt. GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using ...
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
Why You Should Replace Windows 11 with Nitrux Linux 3.5.0 for enhanced perfor...
The choice of an operating system plays a pivotal role in shaping our computing experience. For decades, Microsoft's Windows has dominated the market, offering a familiar and widely adopted platform for personal and professional use. However, as technological advancements continue to push the boundaries of innovation, alternative operating systems have emerged, challenging the status quo and offering users a fresh perspective on computing.
One such alternative that has garnered significant attention and acclaim is Nitrux Linux 3.5.0, a sleek, powerful, and user-friendly Linux distribution that promises to redefine the way we interact with our devices. With its focus on performance, security, and customization, Nitrux Linux presents a compelling case for those seeking to break free from the constraints of proprietary software and embrace the freedom and flexibility of open-source computing.
20 Comprehensive Checklist of Designing and Developing a Website
Dive into the world of Website Designing and Developing with Pixlogix! Looking to create a stunning online presence? Look no further! Our comprehensive checklist covers everything you need to know to craft a website that stands out. From user-friendly design to seamless functionality, we've got you covered. Don't miss out on this invaluable resource! Check out our checklist now at Pixlogix and start your journey towards a captivating online presence today.
20240605 QFM017 Machine Intelligence Reading List May 2024
Everything I found interesting about machines behaving intelligently during May 2024
Pushing the limits of ePRTC: 100ns holdover for 100 days
At WSTS 2024, Alon Stern explored the topic of parametric holdover and explained how recent research findings can be implemented in real-world PNT networks to achieve 100 nanoseconds of accuracy for up to 100 days.
Cosa hanno in comune un mattoncino Lego e la backdoor XZ?
ABSTRACT: A prima vista, un mattoncino Lego e la backdoor XZ potrebbero avere in comune il fatto di essere entrambi blocchi di costruzione, o dipendenze di progetti creativi e software. La realtà è che un mattoncino Lego e il caso della backdoor XZ hanno molto di più di tutto ciò in comune.
Partecipate alla presentazione per immergervi in una storia di interoperabilità, standard e formati aperti, per poi discutere del ruolo importante che i contributori hanno in una comunità open source sostenibile.
BIO: Sostenitrice del software libero e dei formati standard e aperti. È stata un membro attivo dei progetti Fedora e openSUSE e ha co-fondato l'Associazione LibreItalia dove è stata coinvolta in diversi eventi, migrazioni e formazione relativi a LibreOffice. In precedenza ha lavorato a migrazioni e corsi di formazione su LibreOffice per diverse amministrazioni pubbliche e privati. Da gennaio 2020 lavora in SUSE come Software Release Engineer per Uyuni e SUSE Manager e quando non segue la sua passione per i computer e per Geeko coltiva la sua curiosità per l'astronomia (da cui deriva il suo nickname deneb_alpha).
A tale of scale & speed: How the US Navy is enabling software delivery from l...
Rapid and secure feature delivery is a goal across every application team and every branch of the DoD. The Navy’s DevSecOps platform, Party Barge, has achieved:
- Reduction in onboarding time from 5 weeks to 1 day
- Improved developer experience and productivity through actionable findings and reduction of false positives
- Maintenance of superior security standards and inherent policy enforcement with Authorization to Operate (ATO)
Development teams can ship efficiently and ensure applications are cyber ready for Navy Authorizing Officials (AOs). In this webinar, Sigma Defense and Anchore will give attendees a look behind the scenes and demo secure pipeline automation and security artifacts that speed up application ATO and time to production.
We will cover:
- How to remove silos in DevSecOps
- How to build efficient development pipeline roles and component templates
- How to deliver security artifacts that matter for ATO’s (SBOMs, vulnerability reports, and policy evidence)
- How to streamline operations with automated policy checks on container images
Microsoft - Power Platform_G.Aspiotis.pdf
Revolutionizing Application Development
with AI-powered low-code, presentation by George Aspiotis, Sr. Partner Development Manager, Microsoft
Presentation of the OECD Artificial Intelligence Review of Germany
Consult the full report at https://www.oecd.org/digital/oecd-artificial-intelligence-review-of-germany-609808d6-en.htm
How to Get CNIC Information System with Paksim Ga.pptx
Pakdata Cf is a groundbreaking system designed to streamline and facilitate access to CNIC information. This innovative platform leverages advanced technology to provide users with efficient and secure access to their CNIC details.
Recently uploaded (20)
Enchancing adoption of Open Source Libraries. A case study on Albumentations.AI
Enchancing adoption of Open Source Libraries. A case study on Albumentations.AI
Introducing Milvus Lite: Easy-to-Install, Easy-to-Use vector database for you...
Introducing Milvus Lite: Easy-to-Install, Easy-to-Use vector database for you...
みなさんこんにちはこれ何文字まで入るの？40文字以下不可とか本当に意味わからないけどこれ限界文字数書いてないからマジでやばい文字数いけるんじゃないの？えこ...
みなさんこんにちはこれ何文字まで入るの？40文字以下不可とか本当に意味わからないけどこれ限界文字数書いてないからマジでやばい文字数いけるんじゃないの？えこ...
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdf
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdf
Goodbye Windows 11: Make Way for Nitrux Linux 3.5.0!
Goodbye Windows 11: Make Way for Nitrux Linux 3.5.0!
Alt. GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using ...
Alt. GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using ...
Why You Should Replace Windows 11 with Nitrux Linux 3.5.0 for enhanced perfor...
Why You Should Replace Windows 11 with Nitrux Linux 3.5.0 for enhanced perfor...
20 Comprehensive Checklist of Designing and Developing a Website
20 Comprehensive Checklist of Designing and Developing a Website
20240605 QFM017 Machine Intelligence Reading List May 2024
20240605 QFM017 Machine Intelligence Reading List May 2024
Pushing the limits of ePRTC: 100ns holdover for 100 days
Pushing the limits of ePRTC: 100ns holdover for 100 days
Cosa hanno in comune un mattoncino Lego e la backdoor XZ?
Cosa hanno in comune un mattoncino Lego e la backdoor XZ?
A tale of scale & speed: How the US Navy is enabling software delivery from l...
A tale of scale & speed: How the US Navy is enabling software delivery from l...
Presentation of the OECD Artificial Intelligence Review of Germany
Presentation of the OECD Artificial Intelligence Review of Germany
How to Get CNIC Information System with Paksim Ga.pptx
How to Get CNIC Information System with Paksim Ga.pptx
Similar Group - Development Team Management Principals
- 2. WHY We believe we can change web traffic analytics HOW We collect data from millions of users and analyse it WHAT We created several websites and services that shows the analysed data from various angles
- 3. OUR CHALLENGES move fast - we need to develop new features quickly get quick feedback - we need to know if our customers like our product and apply changes fast focus on value - we need to create a company-wide focus on the things that matters
- 4. OUR PROBLEMS our business is constantly evolving we are in a competitive market we are growing our architecture is evolving development can take a lot of time our load is increasing we have more quality issues
- 5. WHAT CAN WE DO improve communication and tasks management standardization scalable architecture (human-wise and production-wise) faster and better quality assurance automate repeating processes
- 6. OUR GOALS WE SHOULD AIM FOR staying focused being flexible shortening feedback loops being quality oriented
- 7. AGILE METHODOLOGY ADOPT CHANGE Focus small features iteration start / stand-up meetings / retrospectives definition of ready less paper, more talk transparent Flexible - quickly adopt to change Short Feedback Loop - release when done Quality Oriented QA built in definition of done
- 8. CVS - GIT BRANCH FAST, MERGE FAST Focus - isolate your environment Flexible - working together without interruptions Short Feedback Loop - commit often, rebase often Quality Oriented - test locally before commits
- 9. DOMAIN DRIVEN DESIGN EVOLVE TOGETHER Focus ubiquitous language structured code and logic APIs as domains Flexible - evolving model Short Feedback Loop - allows testing domain logic first in isolation Quality Oriented test locally before commits No SPOF
- 10. CODE STANDARDIZATION UNITE AND GAIN Focus use common practices when possible enjoy the open source community Flexible - developers mobility Short Feedback Loop - tooling that guide the developer Quality Oriented - part of the build process
- 11. TDD/BDD QUALITY FIRST Focus focus on the task stakeholder and developer work together Flexible - allows safe changes Short Feedback Loop - tooling that guide the developer Quality Oriented - quality before implementation (queuing theory)
- 12. TEAMS BASED ON PROFESSION GROW TOGETHER Focus do one thing good advantage of size Flexible - assign developers to tasks based on workload Short Feedback Loop - change, test, spread across products Quality Oriented - use tools to guide and enforce standards
- 13. OWNERSHIP BASED ON PRODUCT OWN YOUR WORK Focus - distributed responsibility Flexible - define responsibilities based on actual product Short Feedback Loop - alert the right person Quality Oriented - production is part of the process
- 14. A/B TESTING AND FEATURE FLAGS STOP GUESSING Focus - focus on results Flexible - experimenting several options at once Short Feedback Loop - metrics tells what works Quality Oriented - reduce risk in production
- 15. CONTINUOUS INTEGRATION / DEPLOYMENT SHIP FAST AND SAFE Focus - release is not a ceremony Flexible - develop mvp, ship, monitor, repeat Short Feedback Loop - (almost) instant feedback Quality Oriented - safer, less human error prone
- 16. MONITORING CONTROL PRODUCTION Focus - results, not guesses Flexible - monitor everything with minimal impact on production servers Short Feedback Loop - real time data Quality Oriented - detect errors before customers do
- 17. GOOD LUCK!