This document discusses release cycles and delivery roadmaps. It provides guidance on designing well-balanced release cycles that consider constraints. Key points include defining a catalog of release cycles for different user story families, qualifying development steps as value-added or non-value added, assessing current cycles based on workload and lead time, and leveraging techniques like parallelization, continuous integration, and continuous improvement to reduce lead times. The goal is to balance steps for an acceptable ROI and define SLAs for each user story family's release cycle.
Release Management: Successful Software Releases Start with a Planconnielharper
This presentation was given at devLink 2010 in Nashville, TN and will weigh the pros and cons of each type of release cycle and identify what else is needed for a successful software release.
Understand how command & control release plans create false hopes and low quality products because there is no team buy-in.
Learn how to develop vision and use your your vision to drive the release plan workshop. Use patterns to validate your release.
Lastly you must learn from your release plan and improve the next release (inspect & adapt).
Release Management: Successful Software Releases Start with a Planconnielharper
This presentation was given at devLink 2010 in Nashville, TN and will weigh the pros and cons of each type of release cycle and identify what else is needed for a successful software release.
Understand how command & control release plans create false hopes and low quality products because there is no team buy-in.
Learn how to develop vision and use your your vision to drive the release plan workshop. Use patterns to validate your release.
Lastly you must learn from your release plan and improve the next release (inspect & adapt).
In this session you will learn:
SDLC and Quality Standard
What is SDLC and Stages
Phases of SDLC
SDLC Models
For more information: https://www.mindsmapped.com/courses/quality-assurance/qa-software-testing-training-for-beginners/
Phases of the Software Development Process - MeerakicsMeeraki
Each phase of software development has its unique set of goals and milestones. It is critical that the software development company Florida you choose has a proven SDLC process in place to ensure the delivery of predictable results.
Want to learn about Product Management or just look smart at your interview for a new job in tech?
Learn about the terms and acronyms used in technical product management.
Ever want to understand the difference between Agile and Lean? User Testing and UAT? This deck covers that and soooo much more!
In this document we will explain software development life cycle (SDLC), various steps/stages in SDLC and software development methodologies in detail. Original blog posted here on: http://www.satejinfotech.in/what-is-software-development-lifecycle/
Software Development Process and Methodology followed @ Top Guru Assistants.
We propose Agile Methodology with various documents that we would prepare during the project.
Please review it and share your thoughts.
How to Become a Thought Leader in Your NicheLeslie Samuel
Are bloggers thought leaders? Here are some tips on how you can become one. Provide great value, put awesome content out there on a regular basis, and help others.
In this session you will learn:
SDLC and Quality Standard
What is SDLC and Stages
Phases of SDLC
SDLC Models
For more information: https://www.mindsmapped.com/courses/quality-assurance/qa-software-testing-training-for-beginners/
Phases of the Software Development Process - MeerakicsMeeraki
Each phase of software development has its unique set of goals and milestones. It is critical that the software development company Florida you choose has a proven SDLC process in place to ensure the delivery of predictable results.
Want to learn about Product Management or just look smart at your interview for a new job in tech?
Learn about the terms and acronyms used in technical product management.
Ever want to understand the difference between Agile and Lean? User Testing and UAT? This deck covers that and soooo much more!
In this document we will explain software development life cycle (SDLC), various steps/stages in SDLC and software development methodologies in detail. Original blog posted here on: http://www.satejinfotech.in/what-is-software-development-lifecycle/
Software Development Process and Methodology followed @ Top Guru Assistants.
We propose Agile Methodology with various documents that we would prepare during the project.
Please review it and share your thoughts.
How to Become a Thought Leader in Your NicheLeslie Samuel
Are bloggers thought leaders? Here are some tips on how you can become one. Provide great value, put awesome content out there on a regular basis, and help others.
Avea utilized waterfall and agile methodologies concurrently for increased efficiency. IBM rational products helped applying robust release management process for both waterfall and agile.
Release Manager (RM) from AnalytiX Data Services offers a clean, intuitive 100% web interface to track the release process approvals, audits, and verifications through the approval process when migrating release objects from one environment to another.
These are the slides from the webinar organized by InSync Solutions (APPSeCONNECT) in partnership with Zoho.
Here we covered the topic: why CRM used in an organization should be connected with the back office ERP system.
ERP and CRM are used widely across all industry verticals and became inevitable tool in todays business. Each organization is having a large number of Sales and Support resources to provide Pre Sales, Sales, Customer Service and Support.
CRM is the application to automate these business processes. On the other hand ERP is used mainly by Backoffice users for a wide variety of business process management, such as Purchase, Sales, Production, Accounting, Payroll, Sales Forecasting, Production Planning, Inventory Management, Order Processing & Shipment, etc.
Go through the slides to learn more
Compares the project management lifecycle with the IT service management lifecycle and the interactions between the two
Identifies considerations for project managers to successfully lead IT development or infrastructure projects
Consultant and author Jerry Manas shares his slide deck on Service-Oriented Project Management (SOPM), his framework for managing projects with a client-focused mindset. Visit Jerry's website at www.marengogroup.com.
Measuring The Service Provided By Project Management - WhitepaperColin Ellis
In 2015, the highly respected Standish Group stated that whilst some projects met time and cost constraints many customers were unhappy about the service they received. We think that has to change and have developed a tool to help you.
Abstract: Digital technologies have made customers powerful, giving them the option to choose and the means to instantaneously spread their opinions widely. They have become demanding, and they change brands without a blink if their experience with the product or service isn’t what they expect. Brand loyalty, therefore, has taken a backseat and customer experience has emerged supreme. In an IBM survey, 95% of CEOs said enhancing customer experience was top priority for them. Security forms a core foundation for enhancing customer experience!
Typically security has been inward looking focusing more on technology vulnerabilities and less on securing business objectives. Securing the digital enterprise entails looking outside-in, to protect customer experience its strategic objective. Also, internally the digital enterprise needs assurance against vulnerabilities introduced by
digital technologies like cloud, IoT etc.
Bio: Mohan is an acknowledged expert and thought leader in information security. He was the Snr VP and Global CISO at Bharti Airtel, where he had also held charge as the company’s Chief Architect and CIO for its Bangladesh and Sri Lankan operations. Prior to his stint in Bharti, he was an advisor at a Big-4 consultancy, CEO of a security company he helped start, and the Director of the Indian Navy’s Information Technology, where he was awarded the Vishist Seva Medal by the President of India for innovative work in information security. He has also been a member of several national and international committees on security, including the National Task Force on information security, DOT Joint Working Group on Telecom Security, Indo-US Cyber Security Forum, IBM Security Board of Advisors, RSA Security for Business Innovation Council, and has been chairperson of the CII National Committee on data security among others. For his contribution to the information security practice he has also been awarded the DSCI Security Leader Award, CSO Forum Security Visionary Award, and the RSA Security Strategist Award.
Keene Systems latest whitepaper release simplifies the process of planning a software project by comparing it with the phases of building a house. To simplify it even further, Keene also developed a clever infographic that visually walks the viewer through the 10 step process with a conversation between a construction worker and a programmer.
An executive level view of Product Life Cycle Management as an Enterprise Platform. Simplified description of Platform roots and PLM maturity levels. What to do next and how Zero Wait State can help
What is Agile Software Development example?
Image result for agile software development
Examples of Agile Methodology. The most popular and common examples are Scrum, eXtreme Programming (XP), Feature Driven Development (FDD), Dynamic Systems Development Method (DSDM), Adaptive Software Development (ASD), Crystal, and Lean Software Development (LSD).
Test Planning and Test Estimation TechniquesMurageppa-QA
In this Quality Assurance Training session, you will learn about Types of Testing , Test Strategy and Planning, and Test Estimation Techniques. Topic covered in this session are:
• Test Planning,
• Test Estimation Techniques
For more information, about this quality assurance training, visit this link: https://www.mindsmapped.com/courses/quality-assurance/software-testing-training-with-hands-on-project-on-e-commerce-application/
Agile is one of the most important topics . Software testing interview preparation requires
knowledge of agile methodologies and terms.
Important Topics :
Agile - Manifesto
Agile - Characteristics
Agile - Daily Standup Meeting
Agile - Release Planning
Agile - Iteration Planning
Agile - Product Backlog.
Agile Software Development is an iterative development process . Scrum and Kanban are the common methodologies in Agile.
Comprises of various approaches to software development under which requirements & solutions evolve through the collaborative effort of cross-functional teams and their stakeholders.
like Google, Improve your Test perception & practices and learn how Test might be a key lever to improve your business.
- Understand the different types of Test
- Best & Worst practices of Test
What is Agile Methodology?
AGILE methodology is a practice that promotes continuous iteration of development and testing throughout the software development lifecycle of the project. Both development and testing activities are concurrent unlike the Waterfall model
To successfully deliver your IT project: build your team, build your Agile it...Jean-François Nguyen
Today, we are hearing a lot talking about digital company but many of those same companies are forgetting what is a digital company. Back to basics, It's simply a company dealing with IT projects. So, here is my lessons learnt regarding 'How to deliver successfull IT projects' from my 15 years spent as an IT project manager and my 5 years spent as a Lean & Agile coach.
Learn about Agile Methodology of Software Engineering and study concepts like What is Agile, Why Agile is there, Agile Principles, Agile Manifesto with Pros & Cons of it.
Presentation also include Agile Testing Methodology like Scrum, Crystal Methodologies, DSDM, Feature Driven Development, Lean Software Development & Extreme Programming.
If you watch this one please rate it and do share this presentation to others so then can easily learn more about the Agile Methodology.
As we are talking about a ‘Sprint Zero’ to frame a project before its implementation, I proposed to talk about a ‘Program Increment (PI) Zero’ to frame a Program
As an internal consultant for 8 years now, I realized I was experiencing in some way the Spotify model where the Team Manager (Chapter Lead) is not working in a daily basis with its Team members
Rex - How User Stories can help you manage standard components of an IT projectJean-François Nguyen
What is the link between your User Story catalogue and Data Model, Data Dictionary, Entity life cycle, all your tests (dynamic, static, ...).
Warning: subject a little bit technical ;-)
Scrum product owner: how build a project charter & frame the project?Jean-François Nguyen
To frame and present your project, you can use business, product canvas. But sometimes you’ll have to use other internal standard like project charter.
Tool digital meeting room solutions for efficient cross border meeting v1....Jean-François Nguyen
Improve meeting efficiency when attendees are not co-located
How get all attendees involved?
How efficiently manage the activity of a cross-border team?
combine Lean & Agile principles & technical tools from the market. Practices already used in education in Canada e.g. for on-line courses
You want to manage an important Change culture in your firm or team? First, Initiate your Change Story with your Customer needs. Learn to better know him, to better communicate with him to build a relation of Trust & partnership.
Describe the structure of the 15 weeks mission to initiate the Culture Change. Based on Lean & Agile priciples, framework & toolkit. Result from 5 years experience
LF Energy Webinar: Electrical Grid Modelling and Simulation Through PowSyBl -...DanBrown980551
Do you want to learn how to model and simulate an electrical network from scratch in under an hour?
Then welcome to this PowSyBl workshop, hosted by Rte, the French Transmission System Operator (TSO)!
During the webinar, you will discover the PowSyBl ecosystem as well as handle and study an electrical network through an interactive Python notebook.
PowSyBl is an open source project hosted by LF Energy, which offers a comprehensive set of features for electrical grid modelling and simulation. Among other advanced features, PowSyBl provides:
- A fully editable and extendable library for grid component modelling;
- Visualization tools to display your network;
- Grid simulation tools, such as power flows, security analyses (with or without remedial actions) and sensitivity analyses;
The framework is mostly written in Java, with a Python binding so that Python developers can access PowSyBl functionalities as well.
What you will learn during the webinar:
- For beginners: discover PowSyBl's functionalities through a quick general presentation and the notebook, without needing any expert coding skills;
- For advanced developers: master the skills to efficiently apply PowSyBl functionalities to your real-world scenarios.
GraphSummit Singapore | The Art of the Possible with Graph - Q2 2024Neo4j
Neha Bajwa, Vice President of Product Marketing, Neo4j
Join us as we explore breakthrough innovations enabled by interconnected data and AI. Discover firsthand how organizations use relationships in data to uncover contextual insights and solve our most pressing challenges – from optimizing supply chains, detecting fraud, and improving customer experiences to accelerating drug discoveries.
Epistemic Interaction - tuning interfaces to provide information for AI supportAlan Dix
Paper presented at SYNERGY workshop at AVI 2024, Genoa, Italy. 3rd June 2024
https://alandix.com/academic/papers/synergy2024-epistemic/
As machine learning integrates deeper into human-computer interactions, the concept of epistemic interaction emerges, aiming to refine these interactions to enhance system adaptability. This approach encourages minor, intentional adjustments in user behaviour to enrich the data available for system learning. This paper introduces epistemic interaction within the context of human-system communication, illustrating how deliberate interaction design can improve system understanding and adaptation. Through concrete examples, we demonstrate the potential of epistemic interaction to significantly advance human-computer interaction by leveraging intuitive human communication strategies to inform system design and functionality, offering a novel pathway for enriching user-system engagements.
Climate Impact of Software Testing at Nordic Testing DaysKari Kakkonen
My slides at Nordic Testing Days 6.6.2024
Climate impact / sustainability of software testing discussed on the talk. ICT and testing must carry their part of global responsibility to help with the climat warming. We can minimize the carbon footprint but we can also have a carbon handprint, a positive impact on the climate. Quality characteristics can be added with sustainability, and then measured continuously. Test environments can be used less, and in smaller scale and on demand. Test techniques can be used in optimizing or minimizing number of tests. Test automation can be used to speed up testing.
zkStudyClub - Reef: Fast Succinct Non-Interactive Zero-Knowledge Regex ProofsAlex Pruden
This paper presents Reef, a system for generating publicly verifiable succinct non-interactive zero-knowledge proofs that a committed document matches or does not match a regular expression. We describe applications such as proving the strength of passwords, the provenance of email despite redactions, the validity of oblivious DNS queries, and the existence of mutations in DNA. Reef supports the Perl Compatible Regular Expression syntax, including wildcards, alternation, ranges, capture groups, Kleene star, negations, and lookarounds. Reef introduces a new type of automata, Skipping Alternating Finite Automata (SAFA), that skips irrelevant parts of a document when producing proofs without undermining soundness, and instantiates SAFA with a lookup argument. Our experimental evaluation confirms that Reef can generate proofs for documents with 32M characters; the proofs are small and cheap to verify (under a second).
Paper: https://eprint.iacr.org/2023/1886
Goodbye Windows 11: Make Way for Nitrux Linux 3.5.0!SOFTTECHHUB
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.
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdfPaige Cruz
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:
Removing Uninteresting Bytes in Software FuzzingAftab Hussain
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.
Alt. GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using ...James Anderson
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.
Dr. Sean Tan, Head of Data Science, Changi Airport Group
Discover how Changi Airport Group (CAG) leverages graph technologies and generative AI to revolutionize their search capabilities. This session delves into the unique search needs of CAG’s diverse passengers and customers, showcasing how graph data structures enhance the accuracy and relevance of AI-generated search results, mitigating the risk of “hallucinations” and improving the overall customer journey.
GraphSummit Singapore | The Future of Agility: Supercharging Digital Transfor...Neo4j
Leonard Jayamohan, Partner & Generative AI Lead, Deloitte
This keynote will reveal how Deloitte leverages Neo4j’s graph power for groundbreaking digital twin solutions, achieving a staggering 100x performance boost. Discover the essential role knowledge graphs play in successful generative AI implementations. Plus, get an exclusive look at an innovative Neo4j + Generative AI solution Deloitte is developing in-house.
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...James Anderson
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.
GridMate - End to end testing is a critical piece to ensure quality and avoid...ThomasParaiso2
End to end testing is a critical piece to ensure quality and avoid regressions. In this session, we share our journey building an E2E testing pipeline for GridMate components (LWC and Aura) using Cypress, JSForce, FakerJS…
UiPath Test Automation using UiPath Test Suite series, part 6DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 6. In this session, we will cover Test Automation with generative AI and Open AI.
UiPath Test Automation with generative AI and Open AI webinar offers an in-depth exploration of leveraging cutting-edge technologies for test automation within the UiPath platform. Attendees will delve into the integration of generative AI, a test automation solution, with Open AI advanced natural language processing capabilities.
Throughout the session, participants will discover how this synergy empowers testers to automate repetitive tasks, enhance testing accuracy, and expedite the software testing life cycle. Topics covered include the seamless integration process, practical use cases, and the benefits of harnessing AI-driven automation for UiPath testing initiatives. By attending this webinar, testers, and automation professionals can gain valuable insights into harnessing the power of AI to optimize their test automation workflows within the UiPath ecosystem, ultimately driving efficiency and quality in software development processes.
What will you get from this session?
1. Insights into integrating generative AI.
2. Understanding how this integration enhances test automation within the UiPath platform
3. Practical demonstrations
4. Exploration of real-world use cases illustrating the benefits of AI-driven test automation for UiPath
Topics covered:
What is generative AI
Test Automation with generative AI and Open AI.
UiPath integration with generative AI
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Large Language Model (LLM) and it’s Geospatial Applications
IT Software - Release cycle & Delivery roadmap
1. Release cycle
(development process)
&
Delivery roadmap
the Goal:
• Design a well balanced Release Cycle in regard of your constraints
• Define your catalog of release cycles (one per User Story family) and your SLA
2. Release cycle (development process)& delivery roadmap
the key points: the development process, the different type of Test
Key Basics:
• A release cycle is a development macro process
• it’s build around the major steps: Business Requirement/Spec/Dev/Test/Prod setup
• Some steps are ‘Value Added’ for the End User, others are not
• The goal is
• to continuously reduce your constraints to an acceptable level (e.g. reduce your non
regression phase from 1 week to 1 day, …)
• to balance the steps to have an acceptable global ROI
• The base is your average ratio Spec/Dev/Test (in workload, in lead-time)
• This ratio is defined by family of User Story you find in your Backlog
• Each new request should match a family, follow its associated process
Case Study:
We propose to simulate a simplified case study where we’ll mix
• 3 different families of User Stories defined around the criteria of urgency & complexity
• Different levers of improvement: eliminate, improve, reorganise
Hypothesis regarding the Test:
• to simplify the exercise, we take only regression & UAT. Others (Unitary, Functional,
Integration,…) are not taken into account here but should be in the real world
• we also suppose Functional tests are done just after the dev and not only in UAT (too late)
the Goal:
• Design a well balanced Release Cycle in regard of your constraints
• Define your catalog of release cycles (one per User Story family) and your SLA
3. Release cycle (development process)& delivery roadmap
the key points: Value added for the client/End User
Key Understandings:
• Qualify the 3 steps (Spec/Dev/Test) in ‘Value Added’/’Non Value Added’ for the End User
Hypothesis simplified for the case study:
• Let’s say your backlog is composed by 3 families: standard urgent, standard non urgent and
complex
the Goal:
• Understand the dev process step in terms of ‘Value Added’, ‘Non Value Added’ for the User
Spec Dev Test
VA VA Non VA
Average workload Average
Leadtime
Spec Dev Reg UAT
Standard urgent 25%
2.5MD
50%
5MD
10%
1MD
15%
1.5MD
2 weeks
Standard non urgent 25%
2.5MD
50%
5MD
10%
1MD
15%
1.5MD
4 weeks
Complex 25%
10MD
25%
10MD
25%
10 MD
25%
10MD
8 weeks
4. Release cycle (development process)& delivery roadmap
the key points: workload, leadtime, ratio ROI
Key understanding
• Current situation: the 3 release cycles are totally sequential
• Assess the quality of each release cycle in terms of workload & leadtime
• (1): ratio just balanced 1MD of VA for 1MD of NVA. Instead for standard 3MD for 1MD
• (2): any steps can be done in parallel?
the Goal:
• Assess the current Release Cycles in terms of ROI regarding the workload, the leadtime
• For the leadtime, it’s key to get the Voice Of the Customer
Average workload Assessment Average
Leadtime
Assessment
Spec
(VA)
Dev
(VA)
Reg
(NVA)
UAT
(NVA)
VA/NVA
Standard urgent 25%
2.5MD
50%
5MD
10%
1MD
15%
1.5MD
OK 7.5/2.5 2 weeks KO (2)
Standard non urgent 25%
2.5MD
50%
5MD
10%
1MD
15%
1.5MD
OK 7.5/2.5 4 weeks KO (2)
Complex 25%
10MD
25%
10MD
25%
10 MD
25%
10 MD
KO
(1)
1/1 8 weeks KO (2)
5. Release cycle (development process)& delivery roadmap
the key points: User Story family
the Goal:
• Assess the current Release Cycles in terms of ROI regarding the workload, the leadtime
Current situation
Key understanding: what can be improved?
2 weeks
4 weeks
8 weeks
6. Release cycle (development process)& delivery roadmap
key point: pull the Flow, paralellisation
the Goal:
• To reduce your leadtime, you can reduce steps, do some steps in parallel
• Let’s try first to parallelize dev and spec when you can
Lever: parallelisation (pull the flow)
Key understanding: start the dev as soon as the spec is ready (don’t wait artificially). Do it
for any step.
< 2 weeks
< 4 weeks
< 8 weeks
7. Release cycle (development process)& delivery roadmap
key point: continuous integration, code factory (code for the code), Test Driven Development
the Goal:
• Let’s try now to parallelize regression and dev
• you need to reduce the effort & time doing build & regression. Can you automate?
Lever: Continuous integration (Test Driven)
Key understanding:
• Continuous Integration is regular build & regression test all along the dev process. The
coder code to automate the build & regression test (code factory).
• Discover problem early in the process cost less (less root cause analysis, less effort to solve)
< 2 weeks
3 weeks
6 weeks
8. Release cycle (development process)& delivery roadmap
key point: continuous improvement, Test methodology, Over Quality when not required
the Goal:
• Improve your most heavy steps with No Value Added (e.g. UAT for complex User Story)
• Test methodology is question of taking a Risk: Which tests are required, which are not?
Lever: Continuous Improvement on UAT for complex User Stories
Key understanding: in the continuous improvement activity, optimise the UAT process. Some
ideas: Test expert can bring you best practices to optimise your strategy, the data used, etc …
< 2 weeks
3 weeks
5 weeks
9. Release cycle (development process)& delivery roadmap
key point: continuous improvement, dynamic Team capacity management, Visual management
the Goal:
• build your delivery roadmap using your catalog of release cycles
• Define the best strategy (regular deliveries variable content, fix content ad-hoc deliveries, …)
Best case: your flow of User Story is quite homogeneous, predictable & activities quite
independent. You’re able to build & present to your client a stable delivery roadmap for the
next months. Regular deliveries with variable content is more ‘Agile’ & ensure process stability.
Easier to define & apply a SLA. Your team capacity management is capacity planning.
Example: 4 team members working on 3 applications
Key understanding: your reality is particular. Based on best practices/methodology, build
your own model.
Worst case: your flow of User Story is heterogeneous, unpredictable & activities dependant.
You can’t build a stable delivery roadmap in advance. You build dynamically & regularly
depending of your new User request. Your team capacity management is also highly dynamic
and is eased by visual management. Think about what is best for you regarding your
constraints: ad-hoc/regular deliveries, fix/variable release content
10. Release cycle (development process)& delivery roadmap
key point: daily & weekly meeting should be complementary not redundant
the Goal:
• How to use a release cycle?
• Check your team capacity, build your weekly meeting agenda, ….
Build your release cycle per activity/project
Key understanding:
Check your team capacity:
• Team members are not developing at the same time on Appli2 and Appli3
• Book time for your team to do continuous improvement
Read on the roadmap the weekly team meeting agenda
• Depending on where the team is on the release cycle, the agenda can cover subjects
like post mortem, performance monitoring, Best Practice sharing, …
• If not adapted to your context, weekly might be fortnightly or monthly
2
1
4
3
11. Release cycle (development process)& delivery roadmap
the key points: Project management, methodologies, technical tools … should do a ONE consistent
the Goal:
• List of key topics to assess to improve your release cycle & delivery roadmap
• Assess your team, your development process, your code management, your test, …
Code factory
• Create transversal/product team (Spotify)
• Review the development process from the request initiation to production
• onshore-offshore & RA(CI)
• Review roles:
• Team lead, Tech Lead, Scrum master & Product Owner
• others on offshore side
Review project & team management with Agile & Scrum key concepts (events & roles)
• work with MVP (Minimum Viable Product)
• build your final product incrementally through short iterations (PDCA cycle)
• adjust the meeting cascade (hoshin-kanri) to be aligned with TOP management vision
• Implement an electronic dashboard for splitted team to visualize & ease the communication
Review development factory with Lean key concepts
• easily control your code: code management & coder community (GitHub)
• easily deploy technical environment (PaaS/IaaS)
• easily deploy the code: automated package building & deployment (DevOps)
• prove your code is working (Google):
• test methodology & strategy
• continuous integration (build & automated test)
• improve continuously your Code & Factory: architecture & refactoring (SaaS)
1. Build the team: do you empower people?
2. Build the Agile iteration: do you try & adapt in short iteration?
3. Build the Code Factory: do you ensure code quality & fluidity in the process?
12. Appendix
the key points: all tools available in the Lean tool kit
A few examples of analyses you can do to improve your process:
To help your team understand where is inefficiency
1. Workflow mapping combined with RA(CI)
2. Post Mortem to compare your worst project and a successful one
3. And many others in the Lean tool kit …
13. Appendix 1
the key points: team work, all tools available in the Lean tool kit
Workflow mapping combined with RA(CI):
• Be careful not to mix several families
Waste of
time
D0
leadtime
processing time
1 02
03
0
3
0
2
15
1
3
0
2
0
1 12
15
3
in %
in days
processing time
vs
leadtime
step
11
1
step
10
0
step
9
2
step
8
3
step
7
50
step
6
10
step
5
3
step
4
5
step
3
50
step
2
25
step
1
60
D29D10 D20
~ 33 % ~ 33 % ~33 %
80
20
waiting
time
processing
• Too many stakeholders
• 1 request is dependent on 2 decisions levels
• Lack of coordination to avoid waiting time
• Waiting time (~80%) vs Processing (~20%)
• Steps 6, 9 with stakeholder X, 5, 8 (CC), 1 may be the first to focus on but feasibility requires to be checked
Team X – workflow mapping – process Y
14. Appendix 1
the key points: team work, workload, leatime, waiting time
Workflow mapping combined with RA(CI):
• Be careful not to mix several families
• Step C: one person is doing, 4 other people are validating. This split generates 70% of waiting time (14 working days)
• Step D: meeting, writing minutes and make all sign generates 97% of waiting time (7 working days)
• Questions:
• Is the split required?
• If the split is required, is it possible to reduce the waiting time?
process step
0 1 2 3 4
role Step A Step B Step C Step D Step E
Stakeholder 1 RA
Stakeholder 2 RA A RA
Stakeholder 3 R R RA
Stakeholder 4 A R
Stakeholder 5 A RA
Stakeholder 6 A RA
Processing time
(in days) 5.7 0.155 0.005
leadtime
(in days) 20 8 1
waiting time
(in days) 14.3 7.845 0.995
1 2
Lean Best Practice
• To avoid waiting time, R and A should be in the same box to
avoid potential waiting time
• To better visualise the problem, don’t put the C & I of the RACI
Legend:
R: Responsible. The person who is doing the action
A: Accountable. The person who is accountable for the action
1
2
Team X – workflow mapping – process Y
15. Appendix 2
the key points: team work, workload, leadtime, waiting time
Post Mortem to compare your worst project and a successful one
• Be careful not to mix several families
Team X – workflow mapping – process Y
Production
Release
Delay due to
technical operation
25 Feb 2011
Specs & Estimates Dev Prep UAT
17 Jan 2011
6
Amendment
Release Estimate
0,1
Project Start with
Release Content:
05 Jan 2011
0,1
2 6
0,2
2
71,4
1
Change Content
Release:
03 Feb 2011
Freeze Content
07 Feb 2011
3
2
17,3
4
1
6
0,5 6,5
3 2
1,5 1,5
15
23 April 2011
9,7
27
5,218
Bugs Fixing
Initial Prod Release:
09 April 2011
8 Mars 2011
UAT
38%
62%45%55%
Processing Time: 59 days
Lead Time: 108 days
Waiting time: 49 days
Workload: 113 md
Rework: 43,5 md
▪ Ratio processing vs total lead time = 55% | % Rework: 38 %
• Important Rework
• Delay in Release Date
• Several Bugs fixing
• Risk to release after shorter UAT to compensate delay
lower quality of the release / bugs in prod
• Important Change in Release Content
• Missing Test Cases at specification time
• Development prior to Freeze Content to anticipate heavy
workload
• Late Freeze Content