Software testing is an investigation conducted to provide stakeholders with information about the quality of the product or service under test. I hope this ppt will help u to learn about software testing.
Presentation on what is the Software Quality in terms of the Software Engineering Process and as part of Software Development Industry. It also talks about what's Standards & Procedures plus explaining different types of Standards & kinds of Procedures that comes under Software Quality.
It also contain details about SQA Activities, Software Review with different kind of Review Techniques. Then after Software Reliability is discussed with Quality Standards like ISO 9001, CMM & Six Sigma at the presentation end.
“Quality at Speed” is Atlassian’s approach to QA, and we are constantly evolving what that means and how it translates to actual dev team processes. Our developers can confidently take on testing activities, while our QA Engineers tackle larger, harder, and bolder challenges. Teams can ship better features, faster, and reach ambitious quality improvement goals.
We'll talk about how our team has embraced this mindset, how this changes our role in dev teams, and the results we want to achieve. We'll cover the different ways that quality can be defined, the importance of fast deployments, and how we work with teams like DevOps, Growth and Customer Insights to help our dev teams and ultimately benefit our users.
Products covered:
JIRA Software, Bitbucket, Bamboo
Software testing is an investigation conducted to provide stakeholders with information about the quality of the product or service under test. I hope this ppt will help u to learn about software testing.
Presentation on what is the Software Quality in terms of the Software Engineering Process and as part of Software Development Industry. It also talks about what's Standards & Procedures plus explaining different types of Standards & kinds of Procedures that comes under Software Quality.
It also contain details about SQA Activities, Software Review with different kind of Review Techniques. Then after Software Reliability is discussed with Quality Standards like ISO 9001, CMM & Six Sigma at the presentation end.
“Quality at Speed” is Atlassian’s approach to QA, and we are constantly evolving what that means and how it translates to actual dev team processes. Our developers can confidently take on testing activities, while our QA Engineers tackle larger, harder, and bolder challenges. Teams can ship better features, faster, and reach ambitious quality improvement goals.
We'll talk about how our team has embraced this mindset, how this changes our role in dev teams, and the results we want to achieve. We'll cover the different ways that quality can be defined, the importance of fast deployments, and how we work with teams like DevOps, Growth and Customer Insights to help our dev teams and ultimately benefit our users.
Products covered:
JIRA Software, Bitbucket, Bamboo
Quality, quality concepts
Software Quality Assurance
Software Reviews
Formal Technical Reviews
SQA Group Plan
ISO 9000, 9001
Example
Internal and external attributes
An overview of the Agile Manifesto and why Agile SDLC is super important to excellent project management practices. Agile Software development is dominating the game these days. Whether you're going responsive, managing ecommerce, magento, or iphone apps Agile practices will help your efforts succeed.
Quality, quality concepts
Software Quality Assurance
Software Reviews
Formal Technical Reviews
SQA Group Plan
ISO 9000, 9001
Example
Internal and external attributes
An overview of the Agile Manifesto and why Agile SDLC is super important to excellent project management practices. Agile Software development is dominating the game these days. Whether you're going responsive, managing ecommerce, magento, or iphone apps Agile practices will help your efforts succeed.
چند هفته ایست که ساخت طبقه دوم بزرگراه صدر به پایان رسیده است. از نگاه فنی و مدیریت اجرایی الحق جای تبریک و تحسین دارد. به جرات می توان گفت که نمونه چنین پروژه بزرگ شهری قبلا در سابقه پروژه های عمرانی شهر تهران انجام نگردیده است. قطعا مهمترین معیار انتخاب چنین سناریویی برای اجرا رفع گلوگاه های ترافیکی منطقه مربوطه بوده است و حتما ذیل چنین طرح مهمی تائید چندین مهندس مشاور ترافیک و حمل و نقل هم وجود دارد. در طول اجرای طرح و پس از افتتاح آن دیدگاه های مختلفی پیرامون اجرای این پروژه از نگاه متخصصین امر ارائه گردیده است. مجریان طرح با ذکر دلایلی و مستنداتی این سناریو را بهترین گزینه قلمداد کرده و پیش بینی می کنند که اثرات مثبتی در جریان حرکت خودروها در منطقه داشته باشد. از سوی دیگر گروهی از متخصصین حمل و نقل ترافیک هم اصولا با مقوله بزرگراه سازی مخالف بوده و در تاثیر چنین پروژه هایی بر روان سازی ترافیک تردید جدی دارند.
حال که این پروژه به بهره برداری رسیده است تب دوطبقه سازی بالا گرفته و پیش بینی می گردد که مسیرهای دیگری نیز از جمله بزرگراه بعثت , آزادگان و همت هم کاندیدای بعدی باشند. البته دیگر شهرها هم نسبت به این موضوع واکنش مثبت نشان داده و صحبت از اجرای پروژه های مشابه در شهرهای متبوع خود می نمایند.
حال سوال این است که از نگاه مدیریت شهری و توسعه پایدار در خصوص اجرای پروژه های توسعه معابر چه رویکردی را بایستی در پیش گرفت؟ نقش حمل و نقل عمومی و توسعه حمل و نقل ریلی شهری نظیر مترو در این بین چه می شود؟ در انتخاب بهترین سناریو مطالعات هزینه منفعت از نگاه شهری و شاید هم ملی چه جایگاهی دارد؟
خوب است دوستانی که در حوزه حمل و نقل و ترافیک دارای تجربه و مطالعاتی هم هستند در این خصوص مشارکت داشته باشند. باید بررسی شود که عملکرد بزرگراه دوطبقه صدر پس از افتتاح چگونه است و آیا صرف میلیارها تومان هزینه در مقایسه با دستاوردهای آن منطقی بوده است؟
Want to work in advertising? 68% of all ex-Farmers have a job in advertising. Subscribe for selection day at http://farm2014.be
Maybe, you'll be one of the lucky twelve who can take part in a 3-week BBDO advertising bootcamp that breeds the most wanted talent in the sector.
AEM Maxed = Agile + Automation.
Time Warner Cable and iCiDIGITAL reveal how a stellar agile development team delivers an award-winning website using Adobe Experience Manager. Highlights include team interactions, scaling the team, collaborative moments, testing automation, and continuous integration. Also, they will share previews of a few open source attractions that will accelerate your Adobe Experience Manager delivery.
Case Study: Time Warner Cable's Formula for Maximizing Adobe Experience Manager Mark Kelley
Time Warner Cable and iCiDIGITAL reveal how a stellar agile development team delivers an award-winning website using Adobe Experience Manager. Highlights include team interactions, scaling the team, collaborative moments, testing automation, and continuous integration. Also, they share previews of a few open source attractions that will accelerate your Adobe Experience Manager delivery.
An overview of IT challenges and how Perficient China uses agile frameworks, methodologies, and practices to address these challenges and consistently deliver valued results to our clients.
Critical Capabilities to Shifting Left the Right WaySmartBear
The concept of testing earlier in the SDLC isn't new, but the term "shift left" has reignited its importance. See how shifting left can help you, and how to do it right.
This is a practical guide for sprint development based on the OutSystems Delivery Method.
It helps you focus some of the main challenges found when using Agile in the field:
- Your sprints often start not being ready?
- Delivering at sprint end is always struggle?
Then you should take a look!
Target audience: Agile Project Managers (including Engagement and Delivery Managers)
Irresponsible Disclosure: Short Handbook of an Ethical DeveloperLemi Orhan Ergin
Ethics... It could be the most important and underrated topic in software industry. It is directly related with professionalism, craftsmanship and professional discipline. From time to time we have to jump into the discussions, however we never discuss it deeper.
I have found himself in a huge blast of discussions when he tweeted about a **HUGE** security issue at the most popular operating system. Then I had deep thoughts about ethics and the behaviours of ethical developers.
In this session I talk about the followings:
* I refer to real-life stories of many good practices for professional ethics that are critical in the software development world.
* I mention technical and non-technical aspects of being an ethical developer.
* I deep dive into the arguments against the ethical controversies and the debate over the sharing of a major error in MacOS via Twitter.
DevOps & Technical Agility: From Theory to PracticeLemi Orhan Ergin
This is the content I presented in meetups for giving brief information about Agile, Devops, Software Craftsmanship, Opertions and Continuous Delivery and their connection with each other.
Yazılım Geliştirme Kültürünün Kodları: Motivasyon, Teknik Mükemmellik ve İnov...Lemi Orhan Ergin
Bugünün acımasız rekabet ortamında hayatta kalabilmek için her şirketin bir yazılım şirketi olması gerekir. Bu çok büyük bir mücadele demek. Kaliteli yazlımcılar işe alınmalı, projeler doğru yönetilmeli ve proje teslim tarihleri belirlenmelidir. Ancak, gerçekte çok farklı bir tabloyla karşılaşıyoruz. Yüzlerce geliştiriciyle iş görüşmesi yapılıyor ancak bulunamıyor. Geliştiricilerden oluşan bir ekip oluşturulsa bile, motivasyonel sorunlar, sürekli artan teknik problemler, iletişim sorunları, inovasyon eksikliği ve işten ayrılmalar ile ediyoruz. Müşteriler, kaçırılan tarihler ve çıktının düşük kalitesi nedeniyle hayal kırıklığına uğruyor.
Her yazılım geliştirme ekibi kendi dinamiklerini yaratır. Çalışanların davranışlarıyla ekiplerin gizli dinamiklerini toplandığımızda şirketteki yazılım geliştirme kültürünü oluşturuyoruz. Bu, bir yazılım geliştirme takımının ne kadar başarılı olabileceğini tanımlayan, en önemli faktörlerden biridir.
Bu oturumda, motivasyon, teknik mükemmellik, işbirliği, yardımlaşma, yenilikçilik ve başarı sağlayan bir yazılım geliştirme kültürünün nasıl kurulacağından bahsedeceğim. Yazılım dünyasına girmiş ve ilgilenen herkes katılabilir.
Bu sunum Dinamikler 2017 Kongresinde kullanılmıştır.
Git Anti-Patterns: How To Mess Up With Git and Love it AgainLemi Orhan Ergin
Git is one of the most powerful tool in developers' toolbox. If you use it correctly, it dramatically increases productivity of developers and eliminates the waste products continuously. Developers cultivate a development culture on top Git most of the time.
It's powerful but its power is untamed. Many teams fall into several traps of misusing commands and therefore feel uncomfortable while using Git. We mess up Git history, the codebase and the whole preferred branching strategy in seconds. We use branches, merge/rebase strategies, creating commits in wrong ways. Even we never take committing paradigms into account while using Git.
As a software craftsman, I've been using Git for years and I've already educated Git to hundreds of developers in all levels. I'm so lucky; I had a chance to experience huge amount of anti-patterns in time. In this talk, I will talk about what those anti-patterns are and what should we do in order not to fall into them.
TDD is the elengant way of designing software. People scares from it so much, because software design is hard and it requires discipline. In this talk, I tried to describe what TDD is from software design perspective.
Karabük Üniversitesi Programlama Günleri 2016'da gerçekleştirdiğim Git sunumu yansılarıdır.
These are the slides of my talk at Karabuk University Programming Days 2016. The slides are in Turkish.
PHP Frameworks: I want to break free (IPC Berlin 2024)Ralf Eggert
In this presentation, we examine the challenges and limitations of relying too heavily on PHP frameworks in web development. We discuss the history of PHP and its frameworks to understand how this dependence has evolved. The focus will be on providing concrete tips and strategies to reduce reliance on these frameworks, based on real-world examples and practical considerations. The goal is to equip developers with the skills and knowledge to create more flexible and future-proof web applications. We'll explore the importance of maintaining autonomy in a rapidly changing tech landscape and how to make informed decisions in PHP development.
This talk is aimed at encouraging a more independent approach to using PHP frameworks, moving towards a more flexible and future-proof approach to PHP development.
Dev Dives: Train smarter, not harder – active learning and UiPath LLMs for do...UiPathCommunity
💥 Speed, accuracy, and scaling – discover the superpowers of GenAI in action with UiPath Document Understanding and Communications Mining™:
See how to accelerate model training and optimize model performance with active learning
Learn about the latest enhancements to out-of-the-box document processing – with little to no training required
Get an exclusive demo of the new family of UiPath LLMs – GenAI models specialized for processing different types of documents and messages
This is a hands-on session specifically designed for automation developers and AI enthusiasts seeking to enhance their knowledge in leveraging the latest intelligent document processing capabilities offered by UiPath.
Speakers:
👨🏫 Andras Palfi, Senior Product Manager, UiPath
👩🏫 Lenka Dulovicova, Product Program Manager, UiPath
"Impact of front-end architecture on development cost", Viktor TurskyiFwdays
I have heard many times that architecture is not important for the front-end. Also, many times I have seen how developers implement features on the front-end just following the standard rules for a framework and think that this is enough to successfully launch the project, and then the project fails. How to prevent this and what approach to choose? I have launched dozens of complex projects and during the talk we will analyze which approaches have worked for me and which have not.
Neuro-symbolic is not enough, we need neuro-*semantic*Frank van Harmelen
Neuro-symbolic (NeSy) AI is on the rise. However, simply machine learning on just any symbolic structure is not sufficient to really harvest the gains of NeSy. These will only be gained when the symbolic structures have an actual semantics. I give an operational definition of semantics as “predictable inference”.
All of this illustrated with link prediction over knowledge graphs, but the argument is general.
GraphRAG is All You need? LLM & Knowledge GraphGuy Korland
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
Transcript: Selling digital books in 2024: Insights from industry leaders - T...BookNet Canada
The publishing industry has been selling digital audiobooks and ebooks for over a decade and has found its groove. What’s changed? What has stayed the same? Where do we go from here? Join a group of leading sales peers from across the industry for a conversation about the lessons learned since the popularization of digital books, best practices, digital book supply chain management, and more.
Link to video recording: https://bnctechforum.ca/sessions/selling-digital-books-in-2024-insights-from-industry-leaders/
Presented by BookNet Canada on May 28, 2024, with support from the Department of Canadian Heritage.
Search and Society: Reimagining Information Access for Radical FuturesBhaskar Mitra
The field of Information retrieval (IR) is currently undergoing a transformative shift, at least partly due to the emerging applications of generative AI to information access. In this talk, we will deliberate on the sociotechnical implications of generative AI for information access. We will argue that there is both a critical necessity and an exciting opportunity for the IR community to re-center our research agendas on societal needs while dismantling the artificial separation between the work on fairness, accountability, transparency, and ethics in IR and the rest of IR research. Instead of adopting a reactionary strategy of trying to mitigate potential social harms from emerging technologies, the community should aim to proactively set the research agenda for the kinds of systems we should build inspired by diverse explicitly stated sociotechnical imaginaries. The sociotechnical imaginaries that underpin the design and development of information access technologies needs to be explicitly articulated, and we need to develop theories of change in context of these diverse perspectives. Our guiding future imaginaries must be informed by other academic fields, such as democratic theory and critical theory, and should be co-developed with social science scholars, legal scholars, civil rights and social justice activists, and artists, among others.
Let's dive deeper into the world of ODC! Ricardo Alves (OutSystems) will join us to tell all about the new Data Fabric. After that, Sezen de Bruijn (OutSystems) will get into the details on how to best design a sturdy architecture within ODC.
DevOps and Testing slides at DASA ConnectKari Kakkonen
My and Rik Marselis slides at 30.5.2024 DASA Connect conference. We discuss about what is testing, then what is agile testing and finally what is Testing in DevOps. Finally we had lovely workshop with the participants trying to find out different ways to think about quality and testing in different parts of the DevOps infinity loop.
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf91mobiles
91mobiles recently conducted a Smart TV Buyer Insights Survey in which we asked over 3,000 respondents about the TV they own, aspects they look at on a new TV, and their TV buying preferences.
Kubernetes & AI - Beauty and the Beast !?! @KCD Istanbul 2024Tobias Schneck
As AI technology is pushing into IT I was wondering myself, as an “infrastructure container kubernetes guy”, how get this fancy AI technology get managed from an infrastructure operational view? Is it possible to apply our lovely cloud native principals as well? What benefit’s both technologies could bring to each other?
Let me take this questions and provide you a short journey through existing deployment models and use cases for AI software. On practical examples, we discuss what cloud/on-premise strategy we may need for applying it to our own infrastructure to get it to work from an enterprise perspective. I want to give an overview about infrastructure requirements and technologies, what could be beneficial or limiting your AI use cases in an enterprise environment. An interactive Demo will give you some insides, what approaches I got already working for real.
How world-class product teams are winning in the AI era by CEO and Founder, P...
How To Review The Sprints Efficiently
1. the sprints
Lemİ Orhan ERGİN
Principal Software Engineer @ Sony
@lemiorhan
Review
EFFICIENTLY
how to
agilistanbul.com
2. Lemİ Orhan Ergİn
Principal Software Engineer in Sony
has worked in Tüsside, BYM, GittiGidiyor/eBay
and Sony as lead developer, team leader,
technical coordinator and scrum master
got CSM certificate from Jim Coplien
year as Scrum Master
sprints in 4 years as team member and
scrum master
experienced in agile transformation and
building agile culture in teams & organizations
2001
2013
2009
1
56
agile
CSM, PSM1
3. The meaning in agile
how it should be held
recommendations
4. So let’s check out why we prefer
agile development
Sotware is the product we aim to develop.
for building our product
5. ?Agile = ıncremental + Iterative
Agile development is a group of methods based
on incremental and iterative development
6. A Big Bang approach is neither iterative or
incremental. Architectural components are
built to full fidelity, for the full scope, and are
fully integrated once at the end.
bing bang
Data and images are originally from “Fidelity – The Lost Dimension of the Iron Triangle” article by Karl Scotland
http://availagility.co.uk/2009/12/22/fidelity-the-lost-dimension-of-the-iron-triangle/
7. The purely incremental approach builds each
feature, across all components, to full fidelity,
one by one.
Incremental
Data and images are originally from “Fidelity – The Lost Dimension of the Iron Triangle” article by Karl Scotland
http://availagility.co.uk/2009/12/22/fidelity-the-lost-dimension-of-the-iron-triangle/
8. The purely iterative approach builds all the
features, across all components, to the lowest
fidelity, and then increases the fidelity to the
highest level.
ıterative
Data and images are originally from “Fidelity – The Lost Dimension of the Iron Triangle” article by Karl Scotland
http://availagility.co.uk/2009/12/22/fidelity-the-lost-dimension-of-the-iron-triangle/
9. An Agile approach combines the incremental
and iterative approach by building each feature,
one by one, at a low fidelity, and then both
gradually adding features andincreasing their
fidelity until the right combination is achieved.
Full fidelity is not always necessary.
agile
Data and images are originally from “Fidelity – The Lost Dimension of the Iron Triangle” article by Karl Scotland
http://availagility.co.uk/2009/12/22/fidelity-the-lost-dimension-of-the-iron-triangle/
11. Review Meetings are organized to review
the status of evolution of the product with stakeholders
and customers and direct the focus on business value
controlled evolution
12. Show the customers and stakeholders the work
they have accomplished over the sprint
reasonstoconduct
Inspect the sprint and adapt the product backlog for
the next sprint
Gather feedback and foster collaboration
13. The meaning in agile
how it should be held
recommendations
14. At the end of
each iteration
timings
Timeboxed4 hours for
a 1 month iteration
15. No internet through
cellphones or laptops
meeting guidelines
Mails should only be
checked on breaks
Only urgent calls
are allowed
common rules
16. Timing/agenda should be
written on white board
Agenda, timings and
meeting rules should be
mentioned at the beginning
of the meeting
Strictly give breaks and
obey the timings
meeting guidelinesagenda, Breaks & Rules
17. Product Owner facilitates the
meeting, but it not uncommon to have
team members run the meeting
The whole team and
stakeholders attend
PEOPLEthe attendees
The format and the rules should be
explained to the ones
who has no experience
18. Product Owner is the one
who says ship it and
gives "done!" decision
Product Owner is not a
customer representative
PEOPLEProduct Owner
Product Owner identifies
done and not-done items,
discusses backlog and deadlines
19. No slides are allowed.
Working software is reviewed
The team should be prepared
for the review in advance
PEOPLEDevelopment team
All team members should
participate in the review
20. Definition of Done should be
defined and agreed by the
team in advance
Acceptance criteria should be
defined for each story in the
planning meeting
Agreementsthat the review will be based on
Let’s jump to these topics for few minutes
22. Acceptance criteria define the boundaries of a user story,
and are used to confirm when the software is working as intended,
which means the story is completed
Acceptance criteriawhat is it?
The criteria defined by Product Owner to assess completed stories.
It is also be called “Conditions of Satisfaction”
23. Acceptance criteriaFeatures of a good acceptance criteria
Usability Funcitonality error handling Performance Stress tests
Include measures
of usability
Identify specific
user tasks,
business
processes or
functions that
must be in place
at the end of the
project
Enumerate error
cases and how
each should be
handled
Test system
performance
from the
perspective of an
individual user
Acceptable
threasholds
should be defined
for stress testing
24. Acceptance criteriaExample of a Good acceptance criteria
As a customer, I want to order and pay for the book via a secure web-based form,
so that my credit card information is safe.
Description:
✴All mandatory fields must be completed before a customer can submit a form.
✴Information from the form is stored in the customer orders database.
✴Payment can be made via Amex, Master Card, or Visa credit card.
✴The system shall accurately calculate and apply sales tax.
✴The system shall accurately calculate and apply shipping charges.
✴The customer shall be able to verify the accuracy of the order.
✴An acknowledgment email is sent to the customer submitting the form.
✴Protection against spam is working.
✴The code should be deployed and running in Staging environment
acceptance criteria:
26. Focuses of value added steps
Items should add verifiable/demonstrable value to the product
Explains in what conditions a PBI is described as "done"
It is used for assessing the work when it is completed
It guides the team in knowing how many PBIs can be selected
definition of donewhat is it?
DoD is a checklist of valuable activities required to produce software
27. The team should decide the items in the DoD list
DoD is not static, it changes over time
DoD should be reviewed in retrospectives
definition of done
DoD is the primary reporting mechanism for team members
How Related with The team?
28. DoD for a task
DoD for a feature/story
DoD for a iteration/sprint
DoD for a release
definition of done
DoD is informed by the reality
What kind of DOD we can have?
29. ?
Code is readable, it documents itself
JavaDoc and inline comments are entered
Code is refactored
Code obeys clean code principles
Code obeys naming conventions and indentation rules
definition of done
Not a good idea, since DOD items should be verifiable/demonstrable
Clean Code Principles as DOD?
Clean Code Principles are already a must
30. definition of doneWhat can be the Dod entries?
DOD for Tasks DOD for stories DOD for Sprints DOD for releases
Unit tests are written
CI default builds are green Integration/acceptance
tests are written
Design/analysis documents
are written
No critical bugs
Code is reviewed by peers
Demo scenarios are
created
All CI builds are green
No major & critical bugs
Code coverage calculated
SIT is done
Performance/load tests are
completed
Release notes are prepared
Cutover plan is prepared
UAT is done
As the team mature, the DoD could expand for higher quality
Fits to acceptance criteria
31. For reviewing the
points having business
value with customers
and stakeholders
For reviewing the points
directly related with the
technical improvements,
refactoring, quality
metrics with the team
must-haves should-haves
two sections
split the review into
32. must-havessection of the review meeting
Focuses on stories having business value
Audience does not expect to have too much technical detail
Acceptance criteria should pass
The product should be potentially shippable
33. must-havessection of the review meeting
Technical Dept
(If it’s worth mentioning to stakeholders)
Features/Stories with Demo
(The ones the team commited to delivering)
Major/Critical bugs
(Could change according to DoD)
Key Decisions
(Could be technical, market driven, requirements and made by anyone else)
34. section of the review meeting
No need to have stakeholders in the meeting
Technical details could be reviewed
Focuses quality of implementation and support
should-haves
35. section of the review meeting
should-haves
Success Rates of Continuous Integration Builds
Support Cases
Available Bugs
Test/Code Coverage
Release Notes
Change Log
36. All attendees collaborate
on what to do next
Use retrospective to
improve the efficiency of
review meetings
All missing points should be
noted to add to next iterations
as new tasks or stories
Finalizing the meeting
37. The meaning in agile
how it should be held
recommendations
38. The development teams has to be prepared in advance to the
meeting. At most 1 hour preparation per sprint should be enough
for the team.
Problem
Demo/Review is too slow. Development team spends too much
time for preparing the demo.
recommendation
39. Doing a simulation of the review for complex stories before
the meeting will make the team be sure about the software.
Problem
Software is not working in the demo even though it was
working before the meeting
recommendation
40. Focus on reviewing what has done and do not go off the road
Pre-reviews by product owner should be done by the team
Team should be prepared for the review
Allowing too many external audience might cause to exceed the timebox
Problem
Meeting exceeds timebox
recommendation
Let’s jump to pre-review topic for few minutes
42. Whenever a story is completed (or almost completed),
ask PO to spend few minutes to review all the details
Pre-review with PO
It is safer to review with PO before the review meeting to notice
missing points and misunderstandings in advance
What is it about?
That increases success rates of developments,
and as a side effect, the efficiency of review meetings is improved.
43. Problem
Too much technical discussions
recommendation
DoD should cover quality standards
Technical details should be clarified in the sprint before the meeting
44. Problem
Some people are talking, the others are sleeping
recommendation
Everyone should participate in the meeting, no excuse
45. Problem
People are not following the meeting, just surfing and chatting
recommendation
Internet should be closed in cellphones and laptops
Mails should be checked on breaks
Only urgent calls are allowed
These rules should be mentioned in the beginning of the meeting
46. Problem
The team is cheating on what is done and not done
recommendation
Trust is a must
Everything should be transparent, including the failures
No blaming, no finger-pointing..
47. Problem
Chaos in the meeting
recommendation
Show agenda to the team and the progress of the meeting
Remind the rules of review meetings to the team
48. Problem
Too much negotiation with the Product Owner
about accepting the stories
recommendation
Acceptance criteria should be defined in advance
DoD should be checked by team in advance
All parties should be positive and objective
49. Problem
The team gives status reports to Product Owner
recommendation
It is not a status report of individual team members
It is not a "what I did in the last sprint" discussion
It is not a status meeting
51. Problem
Product Owner changed its mind about the predefined
acceptance criteria during the review
recommendation
Too late for any change, stories are reviewed by the agreed acceptance criteria
Product Owner adds new items to the next sprint if required
52. Photos used in the slidES
http://www.flickr.com/photos/therahim/5587920310
http://www.flickr.com/photos/mesfoto/4245156422
http://www.flickr.com/photos/keysring/3493912575
http://www.flickr.com/photos/bealluc/158962685
http://www.flickr.com/photos/unclefuz/4506302304
http://i48.tinypic.com/2saghhs.jpg
References
Definition of Done:
http://www.scrumalliance.org/community/articles/2008/september/what-is-definition-of-done-(dod)
http://www.agilistanbul.com/2012/12/definition-of-done-nin-gucu.html
Big Bang, Iterative, Incremental, Agile:
http://availagility.co.uk/2009/12/22/fidelity-the-lost-dimension-of-the-iron-triangle/
Acceptance Criteria:
http://wiki.servicenow.com/index.php?title=Well-Written_Scrum_Stories#Story_Acceptance_Criteria