SuperOffice has established a culture where QA is an important and integral part of the daily work in R&D. It's about highlighting the quality aspect of everything we do and what actions we need to execute in order to use the new level of visibility that is created. This presentation was held on the Software Product Engineering Conference in Colombo in June 2103 (www.spec.lk) and is about what SuperOffice has done to bring QA to this level
Shift left as first transformation step into Quality AssuranceZbyszek Mockun
Do you work in a company which has established effective testing process, which ensure high quality and support Agile methodologies? Can your testing process be used as a model for other companies? Fortunately, we were in that place a few years ago and had to ask ourselves a question about the next step. The answer was: Let’s be Quality Assurance Engineers rather than Testers. But what should we do? How can we do this transformation?
At the same time, I got feedback from my colleague – Head of Java practice: “Your testers found defects in areas / scenarios which weren’t included in development scope / my devs didn’t know that should cover those edge cases. What can we do with that?”
I had to agree with him. There is no sense to test scenarios which weren’t implemented. This was the starting point of our transformation. We decided to implement Shift left model as it looks like the most promising one. But when we implemented it not everything worked as smooth as we wished. New challenges appeared, but more in my presentation.
Product QA - A test engineering perspectiveImaginea
Imaginea's time test product qa methodology. Our hawkeye methodology helps products get released to maker more efficiently and in lesser time. Products have to be tested with a gotomarket testing approach and thats what we specialize at.
Overview of the different aspects of agile engineering practices (the modern practices for software development) and how they can be adopted in [agile] teams.
Shift left as first transformation step into Quality AssuranceZbyszek Mockun
Do you work in a company which has established effective testing process, which ensure high quality and support Agile methodologies? Can your testing process be used as a model for other companies? Fortunately, we were in that place a few years ago and had to ask ourselves a question about the next step. The answer was: Let’s be Quality Assurance Engineers rather than Testers. But what should we do? How can we do this transformation?
At the same time, I got feedback from my colleague – Head of Java practice: “Your testers found defects in areas / scenarios which weren’t included in development scope / my devs didn’t know that should cover those edge cases. What can we do with that?”
I had to agree with him. There is no sense to test scenarios which weren’t implemented. This was the starting point of our transformation. We decided to implement Shift left model as it looks like the most promising one. But when we implemented it not everything worked as smooth as we wished. New challenges appeared, but more in my presentation.
Product QA - A test engineering perspectiveImaginea
Imaginea's time test product qa methodology. Our hawkeye methodology helps products get released to maker more efficiently and in lesser time. Products have to be tested with a gotomarket testing approach and thats what we specialize at.
Overview of the different aspects of agile engineering practices (the modern practices for software development) and how they can be adopted in [agile] teams.
This presentation introduces agile methodology, talks about scrum and the pros and cons of agile from a various perspectives. It also talks about cost of an agile project
Quality Engineering Approaches by Yotam Sharan
A lecture given by Yotam on October 8, 2013 at eBay Israel Development Center, as part of eBay's QA Conference.
Agile Testing – embedding testing into agile software development lifecycle Kari Kakkonen
My presentation on Agile Testing, including a tuning concept and a case study of agile testing choices in a project, held 16 of June, 2014 at a customer internal seminar.
A software testing practice that follow the principle of agile software development is called Agile Testing.
Agile is an iterative development methodology where requirement evolve through collaboration between the customer and self-organizing teams and agile aligns development with customer need.
Website: https://www.1solutions.biz/
Agile Testing - presentation for Agile User Groupsuwalki24.pl
Agile testing was present on Agile User Group. Presentation covers all aspects of testing on agile process, highlight the role of automation and issues with managing it.
The concept of “shifting testing left” in the software development lifecycle is not new. Shifting testing from manual to automated and then upstream into engineering is a driving factor in DevOps and agile software development. However, Michael Nauman wonders why test automation, DevOps, and agile software development still frequently fail to deliver on their promises? Aligning and hardening your DevOps and test automation—along with streamlining your agile processes—is critical to your project. Michael shares how AutoCAD’s shifting testing left enabled improvements within their engineering team. Learn how the team increased engineering reliability and velocity, and forced process changes upstream into design and research all the way through to product support. Leave knowing why the concept of separation of concerns with regards to quality is as fundamental as the separation of code quality from product quality. Learn how the AutoCAD web team used process dogma and ruthless prioritization to combat metric idolatry and the host of other evils that hold teams back from fully realizing their potential and going beyond agile.
Presented in BSPIN Conference (http://bspin.org/conference2014/) on "Succeeding in SMAC World". Had great interactions and glad to see great interest on Agile Testing concepts with Participants.
Agile Testing examines software from the customer point of view, and requires that the entire team tests the product to deliver value.
According to James Bach, testing is the questioning of a product in order to evaluate it.
Agile Testing takes the fundamentals of software testing, and provides options for testing products delivered in Agile workflows. It focuses on early involvement of testers, defect prevention, quick feedback loops, test automation, and exploratory testing.
This presentation will start with selected ideas from Agile Testing, and
More Agile Testing, then Dag Rowe will tie in ideas from other practices and practitioners, notably BDD and Specification by Example
Impetus Technologies - Partners in Software R&D and Product EngineeringImpetus Technologies
Impetus Mission - ‘To create asymmetric advantages for technology businesses
through Software Product Engineering and Innovation Excellence.’
Impetus offers state-of-the-art Technology and R&D services for software
product development.
Service offerings:
- Product R&D Consulting
- Product Development and Implementation
- Product Sustenance and Support
- Product Architecture and Design
Know more at: www.impetus.com
This presentation introduces agile methodology, talks about scrum and the pros and cons of agile from a various perspectives. It also talks about cost of an agile project
Quality Engineering Approaches by Yotam Sharan
A lecture given by Yotam on October 8, 2013 at eBay Israel Development Center, as part of eBay's QA Conference.
Agile Testing – embedding testing into agile software development lifecycle Kari Kakkonen
My presentation on Agile Testing, including a tuning concept and a case study of agile testing choices in a project, held 16 of June, 2014 at a customer internal seminar.
A software testing practice that follow the principle of agile software development is called Agile Testing.
Agile is an iterative development methodology where requirement evolve through collaboration between the customer and self-organizing teams and agile aligns development with customer need.
Website: https://www.1solutions.biz/
Agile Testing - presentation for Agile User Groupsuwalki24.pl
Agile testing was present on Agile User Group. Presentation covers all aspects of testing on agile process, highlight the role of automation and issues with managing it.
The concept of “shifting testing left” in the software development lifecycle is not new. Shifting testing from manual to automated and then upstream into engineering is a driving factor in DevOps and agile software development. However, Michael Nauman wonders why test automation, DevOps, and agile software development still frequently fail to deliver on their promises? Aligning and hardening your DevOps and test automation—along with streamlining your agile processes—is critical to your project. Michael shares how AutoCAD’s shifting testing left enabled improvements within their engineering team. Learn how the team increased engineering reliability and velocity, and forced process changes upstream into design and research all the way through to product support. Leave knowing why the concept of separation of concerns with regards to quality is as fundamental as the separation of code quality from product quality. Learn how the AutoCAD web team used process dogma and ruthless prioritization to combat metric idolatry and the host of other evils that hold teams back from fully realizing their potential and going beyond agile.
Presented in BSPIN Conference (http://bspin.org/conference2014/) on "Succeeding in SMAC World". Had great interactions and glad to see great interest on Agile Testing concepts with Participants.
Agile Testing examines software from the customer point of view, and requires that the entire team tests the product to deliver value.
According to James Bach, testing is the questioning of a product in order to evaluate it.
Agile Testing takes the fundamentals of software testing, and provides options for testing products delivered in Agile workflows. It focuses on early involvement of testers, defect prevention, quick feedback loops, test automation, and exploratory testing.
This presentation will start with selected ideas from Agile Testing, and
More Agile Testing, then Dag Rowe will tie in ideas from other practices and practitioners, notably BDD and Specification by Example
Impetus Technologies - Partners in Software R&D and Product EngineeringImpetus Technologies
Impetus Mission - ‘To create asymmetric advantages for technology businesses
through Software Product Engineering and Innovation Excellence.’
Impetus offers state-of-the-art Technology and R&D services for software
product development.
Service offerings:
- Product R&D Consulting
- Product Development and Implementation
- Product Sustenance and Support
- Product Architecture and Design
Know more at: www.impetus.com
Indus Aviation's Product Engineering expertise. The services includes Product Engineerings, Product Development, Product Testing - right from ideation to the end of life.
We believe people can and should experience last-minute traveling because all those spontaneous moments enrich our lives.
Therefore, we are building a world-class mobile product that makes last-minute hotel booking fast and rewarding.
Do you want to help us build this product? Then join us! RTFM @ GitHub
https://github.com/HotelQuickly/WeAreHiring/
More info about our Product & Engineering
http://product.hotelquickly.com
Teq Diligent is Product Engineering partner that systematically delivers measurable business value from concept to realization and sustenance.
Teq Diligent addresses the needs of PRODUCT ENGINEERING SERVICES in the field of ELECTRONICS & EMBEDDED by partnering AT ANY STAGE of product realization process with REQUIRED CAPACITY.
What should Product Managers know about the Engineering organization? Why should they care? How will understanding the goals and processes of the engineering team help you get better results?
Agile Development | Product Engineering | Drupal - A Success StorySrijan Technologies
How and why AVTRANZ chose Srijan and how we improved their Drupal applications' performance. Major success pointers were:
○ File transfer time reduced from 15 minutes to 6 seconds
○ Enabling AVTRANZ to save more than $1,000/per month on servers
○ Recognize productivity gain for contractors greater
than 30%
○ Improve on-time delivery of projects from 86% to
better than 95% each month
○ Reduce support calls from external customers by
50%
Read full document for details.
Recent technological advancements have changed the way enterprises do business. Happiest Minds can not only help organizations stay afloat, but also ensure that they gain a competitive edge by leveraging new technologies to drive innovation, manage scalability and explore new markets.
Мар`ян Цар: Product Engineering Thinking: cultivate and maintain a product mi...Lviv Startup Club
Kyiv Project Management Day 2016 Мар`ян Цар: Product Engineering Thinking: cultivate and maintain a product mindset
Сайт конференції: http://pmday.org/
Спільнота в мережі Linkedin: http://bit.ly/PMDayLin
Спільнота в мережі facebook: http://bit.ly/PMDayKyivFB
Twitter конференції: https://twitter.com/LvivPMDay
Agile and Design: creating and implementing products (in Italy) is possibleIlaria Mauric
The wiseman says: "A company specialized in IT consultancy cannot make products."
If you decide to break this taboo, the road is only one: understanding how that product can be realized and working hard to make it.
This is the story of Indyco, a tool born merging an agile dev team and a lean design team. Teams that didn't know each other before. And they made Indyco real in 6 months.
We will share the simple but powerful principles that lead us up to the go-live.
Now we are measuring and collecting data for next step.
These slides have been presented at Better Software 2014.
Agile and Design: creating and implementing products (in Italy) is possibleManuel Spezzani
The wiseman says: "A company specialized in IT consultancy cannot make products."
If you decide to break this taboo, the road is only one: understanding how that product can be realized and working hard to make it.
This is the story of Indyco, a tool born merging an agile dev team and a lean design team. Teams that didn't know each other before. And they made Indyco real in 6 months.
We will share the simple but powerful principles that lead us up to the go-live.
Now we are measuring and collecting data for next step.
These slides have been presented at Better Software 2014.
This is a presentation that Margaret Menzies has used to introduce myself to new teams. The last section is an executive summary of Scrum methodology and a basic implementation schedule.
Delivering beautiful software & web products efficiently 2022_Sep.pdfLaSoft
LaSoft is Web & Mobile Development Agency.
We have been a trusted technology partner for businesses, consulting companies, and startups since 2014. We work with partners worldwide from the USA, Canada, Netherlands, Israel, Germany, Switzerland, and the UK to Saudi Arabia and Nigeria.
Our main expertise lies in data analytics & visualization, business optimization and digitalization, real estate, marketplaces, HR management, and education tech projects.
Our teams successfully delivered more than 85 big web projects and continue to support them; all our projects solve global business tasks. Top Silicon Valley Companies use the product we build.
LaSoft is excellent in web, and mobile development, product design, cloud deployment, business analysis, project specification, project management, and technical partner support.
For more information about us, visit www.lasoft.org
Webinar - Design Thinking for Platform EngineeringOpenCredo
Design Thinking is revolutionising the delivery of next-level digital services with best-of-breed product design and user interface principles ensuring close alignment with users and making services a joy to use.
While much of this success has been in the delivery of customer-facing services, there is untapped potential when it comes to delivering frictionless experiences for the internal users of your infrastructure services – promising business value through increased productivity and reduced frustration in your development and operations teams.
Check out the slides from our webinar on approaching platform engineering with a design thinking mindset.
How Quality Assurance is Important in Development Life Cycleijtsrd
In recent days the requirement of quality has grown up universally. Away back, quality culture was practiced only by software industries, today it has also been embraced by companies using technology in their internal projects. The project should not be risked due to contingency and advancement that may come along the way. This is one of the precepts of software quality. Capacity development are imminent, but must be planned for another sprint, unless there is an urgent need on the part of the customer. The software architecture must adhere to the specified requirements. It can be innovative, lasting and still try to solve, not only the predicted problems, but also the unforeseen ones. It is at this point that the development team must glimpse what is really desired and not just what was asked for. One of the biggest causes of failure in software projects is lack of scope. In the eagerness to start work soon, the scope definition phase is reduced to the extreme. The result of this is a large number of corrections made during a sprint for a feature that was not properly planned. Aayush Tiwari "How Quality Assurance is Important in Development Life Cycle" Published in International Journal of Trend in Scientific Research and Development (ijtsrd), ISSN: 2456-6470, Volume-4 | Issue-4 , June 2020, URL: https://www.ijtsrd.com/papers/ijtsrd31580.pdf Paper Url :https://www.ijtsrd.com/computer-science/other/31580/how-quality-assurance-is-important-in-development-life-cycle/aayush-tiwari
Make It Fast: Delivering UX Research to Agile TeamsUXPA Boston
One of the biggest challenges facing UX designers working with agile teams is providing user research in a quick, effective way. Design sprints take less time than in the past and development makes it difficult to slip user feedback into the mix. Traditional research takes time to design, set up, recruit for, run and analyze. Since that could span several sprints, “traditional” research simply doesn’t work in today’s rapid pace development, and the user experience suffers. Many organizations are tackling this challenge.
We’ve brought together 4 panelists who are using methods to address the issue of rapid UX research. Panelists come from both in-house teams and agencies. We’ll share our approaches and offer practical advice about how to do it, why it works and what could be improved. We’ll cover both unmoderated tests and more traditional moderated tests. You’ll learn some new approaches and get a chance to ask questions or share your own experiences.
Putting the SPARK into Virtual Training.pptxCynthia Clay
This 60-minute webinar, sponsored by Adobe, was delivered for the Training Mag Network. It explored the five elements of SPARK: Storytelling, Purpose, Action, Relationships, and Kudos. Knowing how to tell a well-structured story is key to building long-term memory. Stating a clear purpose that doesn't take away from the discovery learning process is critical. Ensuring that people move from theory to practical application is imperative. Creating strong social learning is the key to commitment and engagement. Validating and affirming participants' comments is the way to create a positive learning environment.
Improving profitability for small businessBen Wann
In this comprehensive presentation, we will explore strategies and practical tips for enhancing profitability in small businesses. Tailored to meet the unique challenges faced by small enterprises, this session covers various aspects that directly impact the bottom line. Attendees will learn how to optimize operational efficiency, manage expenses, and increase revenue through innovative marketing and customer engagement techniques.
Enterprise Excellence is Inclusive Excellence.pdfKaiNexus
Enterprise excellence and inclusive excellence are closely linked, and real-world challenges have shown that both are essential to the success of any organization. To achieve enterprise excellence, organizations must focus on improving their operations and processes while creating an inclusive environment that engages everyone. In this interactive session, the facilitator will highlight commonly established business practices and how they limit our ability to engage everyone every day. More importantly, though, participants will likely gain increased awareness of what we can do differently to maximize enterprise excellence through deliberate inclusion.
What is Enterprise Excellence?
Enterprise Excellence is a holistic approach that's aimed at achieving world-class performance across all aspects of the organization.
What might I learn?
A way to engage all in creating Inclusive Excellence. Lessons from the US military and their parallels to the story of Harry Potter. How belt systems and CI teams can destroy inclusive practices. How leadership language invites people to the party. There are three things leaders can do to engage everyone every day: maximizing psychological safety to create environments where folks learn, contribute, and challenge the status quo.
Who might benefit? Anyone and everyone leading folks from the shop floor to top floor.
Dr. William Harvey is a seasoned Operations Leader with extensive experience in chemical processing, manufacturing, and operations management. At Michelman, he currently oversees multiple sites, leading teams in strategic planning and coaching/practicing continuous improvement. William is set to start his eighth year of teaching at the University of Cincinnati where he teaches marketing, finance, and management. William holds various certifications in change management, quality, leadership, operational excellence, team building, and DiSC, among others.
"𝑩𝑬𝑮𝑼𝑵 𝑾𝑰𝑻𝑯 𝑻𝑱 𝑰𝑺 𝑯𝑨𝑳𝑭 𝑫𝑶𝑵𝑬"
𝐓𝐉 𝐂𝐨𝐦𝐬 (𝐓𝐉 𝐂𝐨𝐦𝐦𝐮𝐧𝐢𝐜𝐚𝐭𝐢𝐨𝐧𝐬) is a professional event agency that includes experts in the event-organizing market in Vietnam, Korea, and ASEAN countries. We provide unlimited types of events from Music concerts, Fan meetings, and Culture festivals to Corporate events, Internal company events, Golf tournaments, MICE events, and Exhibitions.
𝐓𝐉 𝐂𝐨𝐦𝐬 provides unlimited package services including such as Event organizing, Event planning, Event production, Manpower, PR marketing, Design 2D/3D, VIP protocols, Interpreter agency, etc.
Sports events - Golf competitions/billiards competitions/company sports events: dynamic and challenging
⭐ 𝐅𝐞𝐚𝐭𝐮𝐫𝐞𝐝 𝐩𝐫𝐨𝐣𝐞𝐜𝐭𝐬:
➢ 2024 BAEKHYUN [Lonsdaleite] IN HO CHI MINH
➢ SUPER JUNIOR-L.S.S. THE SHOW : Th3ee Guys in HO CHI MINH
➢FreenBecky 1st Fan Meeting in Vietnam
➢CHILDREN ART EXHIBITION 2024: BEYOND BARRIERS
➢ WOW K-Music Festival 2023
➢ Winner [CROSS] Tour in HCM
➢ Super Show 9 in HCM with Super Junior
➢ HCMC - Gyeongsangbuk-do Culture and Tourism Festival
➢ Korean Vietnam Partnership - Fair with LG
➢ Korean President visits Samsung Electronics R&D Center
➢ Vietnam Food Expo with Lotte Wellfood
"𝐄𝐯𝐞𝐫𝐲 𝐞𝐯𝐞𝐧𝐭 𝐢𝐬 𝐚 𝐬𝐭𝐨𝐫𝐲, 𝐚 𝐬𝐩𝐞𝐜𝐢𝐚𝐥 𝐣𝐨𝐮𝐫𝐧𝐞𝐲. 𝐖𝐞 𝐚𝐥𝐰𝐚𝐲𝐬 𝐛𝐞𝐥𝐢𝐞𝐯𝐞 𝐭𝐡𝐚𝐭 𝐬𝐡𝐨𝐫𝐭𝐥𝐲 𝐲𝐨𝐮 𝐰𝐢𝐥𝐥 𝐛𝐞 𝐚 𝐩𝐚𝐫𝐭 𝐨𝐟 𝐨𝐮𝐫 𝐬𝐭𝐨𝐫𝐢𝐞𝐬."
Attending a job Interview for B1 and B2 Englsih learnersErika906060
It is a sample of an interview for a business english class for pre-intermediate and intermediate english students with emphasis on the speking ability.
Business Valuation Principles for EntrepreneursBen Wann
This insightful presentation is designed to equip entrepreneurs with the essential knowledge and tools needed to accurately value their businesses. Understanding business valuation is crucial for making informed decisions, whether you're seeking investment, planning to sell, or simply want to gauge your company's worth.
Premium MEAN Stack Development Solutions for Modern BusinessesSynapseIndia
Stay ahead of the curve with our premium MEAN Stack Development Solutions. Our expert developers utilize MongoDB, Express.js, AngularJS, and Node.js to create modern and responsive web applications. Trust us for cutting-edge solutions that drive your business growth and success.
Know more: https://www.synapseindia.com/technology/mean-stack-development-company.html
RMD24 | Retail media: hoe zet je dit in als je geen AH of Unilever bent? Heid...BBPMedia1
Grote partijen zijn al een tijdje onderweg met retail media. Ondertussen worden in dit domein ook de kansen zichtbaar voor andere spelers in de markt. Maar met die kansen ontstaan ook vragen: Zelf retail media worden of erop adverteren? In welke fase van de funnel past het en hoe integreer je het in een mediaplan? Wat is nu precies het verschil met marketplaces en Programmatic ads? In dit half uur beslechten we de dilemma's en krijg je antwoorden op wanneer het voor jou tijd is om de volgende stap te zetten.
Unveiling the Secrets How Does Generative AI Work.pdfSam H
At its core, generative artificial intelligence relies on the concept of generative models, which serve as engines that churn out entirely new data resembling their training data. It is like a sculptor who has studied so many forms found in nature and then uses this knowledge to create sculptures from his imagination that have never been seen before anywhere else. If taken to cyberspace, gans work almost the same way.
As a business owner in Delaware, staying on top of your tax obligations is paramount, especially with the annual deadline for Delaware Franchise Tax looming on March 1. One such obligation is the annual Delaware Franchise Tax, which serves as a crucial requirement for maintaining your company’s legal standing within the state. While the prospect of handling tax matters may seem daunting, rest assured that the process can be straightforward with the right guidance. In this comprehensive guide, we’ll walk you through the steps of filing your Delaware Franchise Tax and provide insights to help you navigate the process effectively.
What are the main advantages of using HR recruiter services.pdfHumanResourceDimensi1
HR recruiter services offer top talents to companies according to their specific needs. They handle all recruitment tasks from job posting to onboarding and help companies concentrate on their business growth. With their expertise and years of experience, they streamline the hiring process and save time and resources for the company.
Skye Residences | Extended Stay Residences Near Toronto Airportmarketingjdass
Experience unparalleled EXTENDED STAY and comfort at Skye Residences located just minutes from Toronto Airport. Discover sophisticated accommodations tailored for discerning travelers.
Website Link :
https://skyeresidences.com/
https://skyeresidences.com/about-us/
https://skyeresidences.com/gallery/
https://skyeresidences.com/rooms/
https://skyeresidences.com/near-by-attractions/
https://skyeresidences.com/commute/
https://skyeresidences.com/contact/
https://skyeresidences.com/queen-suite-with-sofa-bed/
https://skyeresidences.com/queen-suite-with-sofa-bed-and-balcony/
https://skyeresidences.com/queen-suite-with-sofa-bed-accessible/
https://skyeresidences.com/2-bedroom-deluxe-queen-suite-with-sofa-bed/
https://skyeresidences.com/2-bedroom-deluxe-king-queen-suite-with-sofa-bed/
https://skyeresidences.com/2-bedroom-deluxe-queen-suite-with-sofa-bed-accessible/
#Skye Residences Etobicoke, #Skye Residences Near Toronto Airport, #Skye Residences Toronto, #Skye Hotel Toronto, #Skye Hotel Near Toronto Airport, #Hotel Near Toronto Airport, #Near Toronto Airport Accommodation, #Suites Near Toronto Airport, #Etobicoke Suites Near Airport, #Hotel Near Toronto Pearson International Airport, #Toronto Airport Suite Rentals, #Pearson Airport Hotel Suites
Skye Residences | Extended Stay Residences Near Toronto Airport
Making quality visible in Product Engineering
1. Making QA Visible
by JAN PETTER HAGBERG
COLOMBO FRI 14. JUNE 2013
in product engineering
2. A quality
assurance company
should champion
processes that build
quality into the code
from the start rather
than test quality
in later
Mary Poppendieck
3. my talk today
how we have made QA an
integral part of what we
do, and why we do it
15. our vision is to deliver
software solutions which
positively influence the
individual user, by making their
daily tasks more efficient,
easier and fun
The SuperOffice vision statement - 1990
16. second
build
a culture
we discussed…
How we really wanted to develop our
software
How we wanted to be proud of not
only the software we created, but
also how we created it
17. In product development there
is no such thing as
it works on my machine
it is just a 10 min job
a favorite hero who solves your current
problems with dazzling programming
= problems!
21. each phase produces deliverables
that should be «tested» before
handed over to the next phase in the
development process
22. document inspection
Formal quality verification of a
finalized document. May be used on
all documents. Document updated.
1/3 presentation
A small informal presentation of a
solution aimed to generate discussion
and maybe alternative solutions
backlog meetings
Presentation of User Stories
code review
Quality Assurance of code or unit
test code before feature complete or
after implementation of bugfix
pair testing
Developer gets help with dev.test
from a tester. Bugs found are fixed
different
types
of
reviews
23. project
retrospective
Regardless of what we
discover, we understand and truly
believe that everyone did the best
job they could, given what they
knew at the time, their skills
and abilities, the resources
available, and the situation at
hand
Norman L. Kerth
27. -> 97 - Source Control system
- Developers tested during weekends when product was considered finished
1997 - The developers tested at the end of the development cycle
- BugTracker, our own implemented bug database
- Improved our Release Test routines
1998 - We introduced a common coding StyleGuide
- Specification and Technical design templates was introduced
- Bought a professional bug tracking system - DevTrack
1999 - A dedicated test person was hired
- Code Reviews introduced
- Rational Rose and UML was introduced
- Nightly builds
- Milestones with testing of each Milestone
- First Project Review
2000 - We enhanced the templates for Specification and Technical design
2002 - Test Procedures were introduced
- Two persons on the Test team
2003 - StateZero DB created which is a DB you know the content of.
2004 - Developers Test (checklist)
- Unit Tests on NetServer
2005 - Three persons on the Test team
- 1/3 Reviews and Document Inspections
2006 - QA Plan template and QA Progress Plan template
- Smoke test introduced
- Hired Hans Schaefer to help us with analyzing our test work
2007 - Sri Lanka test resources was hired (3 people)
- SCRUM introduced
2008 - Improved our Beta program
- More Test people hired
2009 - SCRUM used in our largest project so far SuperOffice 7.0 win & web
- Sri Lanka test resource now counts 3 more people = 6 people, 4 people in Norway
- One tester on each team
2011 - Microsoft TFS tool introduced, supports working with the SCRUM as an Agile method
28. SCRUM process makes QA
work visible
sprint
test
functional
test
TDD
testing is part of daily work
backlog
meeting sprint
planning
32. frequent releases
will give you quick feedback from your
users and increase the quality
awareness among your product
developers
33. beta program
«testing carried out by real users
in real environments»
the beta program can be an
opportunity to let your
product developers
get to know
your users
38. about
me
I am experienced in most roles involved in software development
after 20 years in the business. I have worked both in the ISV industry
as well as a consultant. After many years as a programmer, I started
to look closer to the processes and methods used in software
development and how to improve these.
With a special interest in delivering good quality software on time I
have build up the QA team in SuperOffice and also embraced Agile
methodologies as the development process to be used within the
company.
Today I am working with offshoring, distributed teams, processes in
R&D and as SCRUM master. I am also the QA Manger in SuperOffice
SuperOffice have 200 employees, 42 of us work in R&D
Editor's Notes
QA are all the activities we do to ensure correct quality during development of new products
What we in SuperOffice wanted to achieve was to find the defects early in the development cycle, preferably before they where implementedfinding defects should be the exception not the rule. if verification triggers test- and fix cycles, then the dev.process is defective.What you want Is a culture where you don't blame testers for escaped bugsIn the earlier days, Quality Aassurance was initially used, like in World War II when munitions were inspected and tested for defects AFTER they were made. Today's quality assurance systems emphasize catching defects BEFORE they get into the final product and by that eliminate waste
I strongly believe in these three principles
Software product development is about making a great product that your audience want to buy. You do this by building the product first and then people will evaluate it and buy it if they like it."Like it" does not only mean functionality, but also that ithas an easy to understand designactually works as intended, meaning that the user gets a good feeling of the product in his experience of using it
Quality is important for good user experience. Not only in the design, but also in the materials usedYou wouldn't build a great design chair using rotten wood, would you? Steve Jobs was extreme in his thoughts about this when he built his Macintosh computers. You don't need to go that far, but it is important that:Good quality architecture and code that is maintainable AND extensible over time/versions
You want to eliminate waste because you need that time to work with your next versionmore bugs means more time until you are able to releasefor every month you delay your release because of bad quality (it is not ready) you both loose sales and the opportunity to start on the next version of your product= bugs are waste
This might look like a finished project ready to ship, but is not! I believe in what I see and not what project plans tells me. I need to see a working piece of software to know the statusThe picture above is from early 2000. The cards on the wall are not user stories, but functional areas (large piece of functionality)In this image there are a lot of hidden work – bugs, not completed features, works on my machine etc= You do not know the status of this project before you have tested it
In theproject:Eachbugfound late in thedevelopmentcycleinvolvesseveralpeople and administrationofthebug; Tester (findsbug, logs it)Product Owner (reproduces thebug, evaluatesthebug)Developer (reproduces thebug, fixes it, developers test)Tester (verifiesfix)This sums up to manyhours used pr bug = waste
After the Release:In Product Development you must always think of your next version and start developing it as soon you have released. You don't want to use your time fixing faults in a released product ==> It ruins your flowWhen you release you should know the defects that exist in your product. Your software will always have errors, but you should know about them so you are able to evaluate which ones to fix and which ones to ship with your softwareSpending less resources on older versions means you can focus on improving your product-line and delivering a better user experience.
I believe that taking QA seriously, doing things right the first time will free up time for improving your product and make it more competitive
Not time to tell abouteverythinghere, but I willgiveyou 5 thingsthatwe have done to ensurethat QA is visible in our R&D department and is a part oftheeverydaylifeofeach and oneofus, not onlythe testers.
This vision actually sets the standardIf you are so lucky that your company have a vision, you can find a lot of useful information here. The SuperOffice vision guides us in where to put our efforts when we develop our software. We can spend some time on a user control if we think it will apply with our vision about being more efficient and easier to use.The same goes for bugs – our software should POSITIVELY influence our users, and you don’t do that with a piece of software with serious defects OR a lot of minor defects that the user runs into all the time => gives a negative user experience and not positive
At one time in SuperOffice we started to talk about how we really wanted to develop software. This was important because it created a concensus for the basic To establish the culture we started with study groups. Once a week at almost at the end of the day, we gathered in a study group and discussed books like “Code Complete” and “Clean Code” (Steve McConnel), Design Patterns, The Deadline, Peopleware (Tom DeMarco) to mention a few.
The code must work on the test servers – no discussion and it is your job to make sure that it worksThere is no such thing as a 10 min job: It is not just to "add" not planned functionality just because the developer sees an opportunity. It´s inevitable that it will involve other resources from Design, Testing, error handling and prioritization by Product Owner etc also = use a lot of time not scheduled forA hero in your team that always fixes your problems as a Project Manager, but very often with consequences revealed later.= this causes problems
How to build the QA culture - At SuperOffice we all have the title "Product Developer", but we have different skills in designing, development and testing etc.
Everybody participates – all meetings are rescheduled – it is Fun and we all learn new things about our product
Reviews and retrospectivesareactivitiesthatreally supports theconceptofthat QA is everyonesresponsibility. Thesearetechniquesthatare used bothearly and late in thedevelopmentprocess and theyarethere to ensuregoodqualityearly or to improveyourprocess and learn from yourmistakes.
Testing in thiscontext is Reviews, Presentations ofhowwethinkaboutthatthenewarchitectureshould be (Technical review) etc…
Reviews are the maybe mot visible QA thing you do since it involves almost everyone. Shows that you have to deliver Quality before you send you work to the next person in the working chain.Sogeti claims that 40% of the bugs are introduced before the coding starts. This very much align with what Tom Gilb also saysStart early - look for bugs in your documentation. Use techniques like: Document review, backlog meetings, 1/3 presentation etc. This involves Product Owners, Designers, Testers and Developers and makes the Quality Assurance aspect very visible
Even if you do SCRUM and sprint retrospectives, it is also a good idea to run a project retrospective and get an analyze of the whole project from start to end.The Project Retrospective technique does not focus on blame, but that we did what we did because of the situation at hand and the knowledge we had at that time
Within Product Engineering it will be the same peoplethatwillworkonthenextversionofyourproduct. It will be veryuseful to analyzewhatworked and whatdidwe not yetknowhow to dealwith etc.Whathappened in theprojectWhydid it happenWhatcanwe do to make sure it does not happenagainThe workshop aims to build 5 posters:Whatworkedwellthatwewill not forgetWhat have welearnedWhatshallwe do differentlynext timeWhatweneed to discussfurther, still puzzles us.Whatwedon’tknowhow to solve at this moment
You want to have everybody on boardPeople are only able to adjust to a few changes in each project, not all at once
QA is very visible in the Agile and SCRUM process.Sprint TestPerformed by a QA person when a part of a functionality is finishedimplemented to ensurethat it works and that it workswithother parts ofthefunctionality and the rest oftheapplication.Functional TestPerformed by a QA team when a functionlity is finishedimplemented and all bugsfound by Sprint Tests arefixed. Last test offunctionalitybefore a System Test.
Tools, like TFS - everything is in the same tool. Apply rulesUsing a tool that contains functionality or is integrated with all sub-systems so that everybody easily gets an overview of open User Stories and unresolved bugs at any time makes both the progress and quality more visible for every team memberAbilty to apply rules for submitting of code
This is where you connect with your users
We are often working “behind closed doors”, only our bosses gets to meet our customers and users now and then
This is also an opportunity for you to let your Product Developers experience how the product they have created is received by your usersIt is easier to understand the problem of a user if you get to see what a fault in your program causes him in his daily work.Gamification – possible for users to “like” functionality so that your dev.teams get scores?In two projects we have used a pre-beta program with 20 users that have helped us testing. They where given a short test assignment that also teached them about the new functionality. We shared the result in a tool where everyone could watch the progress and the comments written by the testers. We answered the testers ASAP and logged bugs if they found anything interesting – the best part; the users thought it was fun Free testers
…becauseyou do it right the first timeDon’tneed to use time on fighting bugs