This presentation is about -
What are the different phases of SDLC?,
How does the process of Software Development Start?,
Project Initiation,
Requirement Gathering and Analysis,
What is Requirement document and what it contains?,
What is use case document and what it contains?,
What is Basic path and Alternate Path?,
Role of Business Analyst,
Example for explaining each phase,
Role of technical specification team,
What is Technical specification document?,
What is System Design?,
Role of Design team,
What is design document?,
Role of architecture team,
System development,
Role of development team,
Deliverable of Development phase,
System testing,
Role of testers and types of testing,
User acceptance testing,
System deployment,
System maintenance,
Events in the maintenance phase like bug fixes,
This presentation is about -
What are the different phases of SDLC?,
How does the process of Software Development Start?,
Project Initiation,
Requirement Gathering and Analysis,
What is Requirement document and what it contains?,
What is use case document and what it contains?,
What is Basic path and Alternate Path?,
Role of Business Analyst,
Example for explaining each phase,
Role of technical specification team,
What is Technical specification document?,
What is System Design?,
Role of Design team,
What is design document?,
Role of architecture team,
System development,
Role of development team,
Deliverable of Development phase,
System testing,
Role of testers and types of testing,
User acceptance testing,
System deployment,
System maintenance,
Events in the maintenance phase like bug fixes,
Scaling Kanban in the Enterprise with GreenHopperDavid Jellison
Presentation delivered @Atlassian Summit 2012. Balancing the coordination of many Agile product delivery teams on the same major release cycle -- and still allowing these teams to self-organise -- is a craft Agile Enterprises must master. JIRA, GreenHopper and Confluence provide a rich platform that accommodates cross team co-ordination and the flexibility required for teams to self-organise. In this talk, David will walk the audience through the process of breaking down a Kanban value chain into steps and transitions, mapping out compatible workflows, and building the combined board. David will also share details of how Constant Contact provides visibility into the progress of teams and the release cycle. Constant Contact was able to deliver 15% more often in 2011 than prior years by refining their Agile practices.
Webvirtue is a leading offshore software development company based in India specialized in ecommerce software development, custom software development, web software development and more. For more details visit here http://www.webvirtue.com/software-development.php
Scaling Kanban in the Enterprise with GreenHopperDavid Jellison
Presentation delivered @Atlassian Summit 2012. Balancing the coordination of many Agile product delivery teams on the same major release cycle -- and still allowing these teams to self-organise -- is a craft Agile Enterprises must master. JIRA, GreenHopper and Confluence provide a rich platform that accommodates cross team co-ordination and the flexibility required for teams to self-organise. In this talk, David will walk the audience through the process of breaking down a Kanban value chain into steps and transitions, mapping out compatible workflows, and building the combined board. David will also share details of how Constant Contact provides visibility into the progress of teams and the release cycle. Constant Contact was able to deliver 15% more often in 2011 than prior years by refining their Agile practices.
Webvirtue is a leading offshore software development company based in India specialized in ecommerce software development, custom software development, web software development and more. For more details visit here http://www.webvirtue.com/software-development.php
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.
Butch Landingin, CTO of Orange & Bronze Software Labs, talks about the Agile Methodology for the Philippine Software Industry Association's Enablement Seminar on April 27 at the AIM.
About O&B:
Orange & Bronze is an offshore product and software development firm in the Philippines, is one of the first companies in Asia to use and advocate Agile Software Development, and has been using it since our inception in 2005, back when Agile was still an emerging movement. O&B offers training courses for Agile with Scrum and XP - these classes were developed and are taught by some of the Philippines' well-known and respected Agile / Scrum coaches and practitioners, and uses the format trusted by some of the best companies in the Philippines.
this presentation contains agile engineering practices which are used by software community.
These practices provides agility in the software development. Applying agile software development without these practices is not easy for software developers.
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.
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.
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.
JMeter webinar - integration with InfluxDB and GrafanaRTTS
Watch this recorded webinar about real-time monitoring of application performance. See how to integrate Apache JMeter, the open-source leader in performance testing, with InfluxDB, the open-source time-series database, and Grafana, the open-source analytics and visualization application.
In this webinar, we will review the benefits of leveraging InfluxDB and Grafana when executing load tests and demonstrate how these tools are used to visualize performance metrics.
Length: 30 minutes
Session Overview
-------------------------------------------
During this webinar, we will cover the following topics while demonstrating the integrations of JMeter, InfluxDB and Grafana:
- What out-of-the-box solutions are available for real-time monitoring JMeter tests?
- What are the benefits of integrating InfluxDB and Grafana into the load testing stack?
- Which features are provided by Grafana?
- Demonstration of InfluxDB and Grafana using a practice web application
To view the webinar recording, go to:
https://www.rttsweb.com/jmeter-integration-webinar
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/
UiPath Test Automation using UiPath Test Suite series, part 3DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 3. In this session, we will cover desktop automation along with UI automation.
Topics covered:
UI automation Introduction,
UI automation Sample
Desktop automation flow
Pradeep Chinnala, Senior Consultant Automation Developer @WonderBotz and UiPath MVP
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Essentials of Automations: Optimizing FME Workflows with ParametersSafe Software
Are you looking to streamline your workflows and boost your projects’ efficiency? Do you find yourself searching for ways to add flexibility and control over your FME workflows? If so, you’re in the right place.
Join us for an insightful dive into the world of FME parameters, a critical element in optimizing workflow efficiency. This webinar marks the beginning of our three-part “Essentials of Automation” series. This first webinar is designed to equip you with the knowledge and skills to utilize parameters effectively: enhancing the flexibility, maintainability, and user control of your FME projects.
Here’s what you’ll gain:
- Essentials of FME Parameters: Understand the pivotal role of parameters, including Reader/Writer, Transformer, User, and FME Flow categories. Discover how they are the key to unlocking automation and optimization within your workflows.
- Practical Applications in FME Form: Delve into key user parameter types including choice, connections, and file URLs. Allow users to control how a workflow runs, making your workflows more reusable. Learn to import values and deliver the best user experience for your workflows while enhancing accuracy.
- Optimization Strategies in FME Flow: Explore the creation and strategic deployment of parameters in FME Flow, including the use of deployment and geometry parameters, to maximize workflow efficiency.
- Pro Tips for Success: Gain insights on parameterizing connections and leveraging new features like Conditional Visibility for clarity and simplicity.
We’ll wrap up with a glimpse into future webinars, followed by a Q&A session to address your specific questions surrounding this topic.
Don’t miss this opportunity to elevate your FME expertise and drive your projects to new heights of efficiency.
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.
State of ICS and IoT Cyber Threat Landscape Report 2024 previewPrayukth K V
The IoT and OT threat landscape report has been prepared by the Threat Research Team at Sectrio using data from Sectrio, cyber threat intelligence farming facilities spread across over 85 cities around the world. In addition, Sectrio also runs AI-based advanced threat and payload engagement facilities that serve as sinks to attract and engage sophisticated threat actors, and newer malware including new variants and latent threats that are at an earlier stage of development.
The latest edition of the OT/ICS and IoT security Threat Landscape Report 2024 also covers:
State of global ICS asset and network exposure
Sectoral targets and attacks as well as the cost of ransom
Global APT activity, AI usage, actor and tactic profiles, and implications
Rise in volumes of AI-powered cyberattacks
Major cyber events in 2024
Malware and malicious payload trends
Cyberattack types and targets
Vulnerability exploit attempts on CVEs
Attacks on counties – USA
Expansion of bot farms – how, where, and why
In-depth analysis of the cyber threat landscape across North America, South America, Europe, APAC, and the Middle East
Why are attacks on smart factories rising?
Cyber risk predictions
Axis of attacks – Europe
Systemic attacks in the Middle East
Download the full report from here:
https://sectrio.com/resources/ot-threat-landscape-reports/sectrio-releases-ot-ics-and-iot-security-threat-landscape-report-2024/
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
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.
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.
"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.
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.
1. Agile Product Management &
Development in a nut shell
―Where common sense prevails, so shall Agile‖
Ashwinee Kumar
6 Jan 2012
4/19/2012 * I have used ideas, & content from other resources in this presentation. 1
2. Agenda
• Agile Manifesto
• Types of Agile
• Best practices of Agile
• Scrum
• Documentation
• Sprint details
• User Stories
• Planning & Estimations
• Metrics
• Product Backlog
• Appendix
• Best Practices of Distributed Scrum
• Non-functional Requirements
• Product Requirement Document
• Product Vision
• Benefits to Marketing & Sales
4/19/2012 2
3. Realities of Projects
• Requirements/scope changes frequently due to factors beyond our control
• Defects are expensive
– Defect found during test phase could cost 10–15 times more than if found and fixed during
implementation phase.
– Fixing defects in the field can cost 10–100 times more than fixing the same defect in the
coding phase
• 20% of your features will give 80% of a product’s value
• Artifacts such as Detailed design, Requirement document do not add value
to the product
• Features not meeting customer expectation leaves him dissatisfied,
irrespective of what is in the contract
4/19/2012 3
4. Agile Manifesto
• Individuals and interactions over processes and tools
• Evolving - Working software over comprehensive documentation
• Collaborative - Customer collaboration over contract negotiation
• Adaptive - Responding to change over following a plan
4/19/2012 4
5. Types of Agile
• Lean Software Development
– evolved from the ideas of lean manufacturing in automotive industry
– includes thoughts on eliminating waste, adding customer value, and empowering workers.
• The Agile Unified Process combines a process with tools and is a derivate of
Rational’s Unified Process.
• Test Driven Development emphasizes the definition of test cases even prior to the
actual implementation of the code.
• Extreme Programming is a toolbox of engineering practices like pair programming, or
continuous integration
• Scrum is an extremely efficient and streamlined process of managing and tracking
teams.
4/19/2012 5
6. Best Practices of Agile
• Search for the root cause of failure
• Focus on the customer value and avoid any waste
• Decentralize responsibility and accountability
• Focus on teaming and collaboration rather than splitting work
• Continuous improvement (Kaizen)
• Flexibility to react to changing customer requirements
• Standardization of processes
• Planning and anticipatory thinking
• Simple and pragmatic tools
4/19/2012 6
7. Scrum
• Roles - Product owner (play customer), team (implement), scrum master (manage
project)
• Teams – Cross functional
– entrust individual teams with entire end-to-end tasks
• Documents - product backlog, sprint backlog, sprint result, stories, test cases, user
documentation
• Sprints are broken into stories, stories are broken into tasks
• Large, loosely defined stories are known as epics. Epics are broken into stories in
product backlog
• Tasks can be bug fixes, Features are user stories
• Sprint size - 2 weeks
• Meetings - Sprint planning, daily scrum meeting, sprint review, scrum of scrum
• Tracking – Burn down chart
• A task or a user story is only counted as complete if it is completely done
– including automated test cases, all tests executed, all documentation done, and all remaining
defects fixed
4/19/2012 7
8. Documentation in Scrum
• Backlog lists and team charters will provide a prioritized list of use cases that are to
be delivered.
• Continuously updated burn down charts provide data to assess the project status and
help to uncover risks and delays.
• Defect documentation keeps a record of bugs that are being resolved
• Design documents share architectural decisions and technical details with a larger
community and are an excellent source of information for those who will use the
resulting implementation.
• Coding guidelines are useful to achieve a common programming model. They will
help to write consistent code that considers aspects like accessibility, translation,
performance, etc.
• Specifications describe programming interfaces and are needed if other teams will re-
use code provided as a common component.
• Test scenarios describe test cases to be executed.
• Checklists include a lot of know-how that was gained in the past. It absolutely makes
sense to leverage them to make sure that nothing has been forgotten.
4/19/2012 8
9. Sprint/Iteration
Iteration 0 Iteration 2 … Iteration n •Continuous iterative and adaptive planning
•Continuous design
Iteration Test 1 Iteration Test 2 … Iteration Test n •Continuous testing (automated)
•Continuous listening
Function and System Verification •Continuous conversation and collaboration
•Continuous demos
•Continuous consumption of our own output
Translation Test
•Continuous status
•Continuous feedback
Final Functional &
•Continuous learning
System Regression
•Continuous progress
Performance Testing
• The idea of iterations is to create an even and steady rhythm of progress in a sustainable, constant pace –
repetitively and predictably
• Development proceeds by designing and implementing small chunks of code, which are immediately tested and
continuously integrated into the code base, without lag time in between
• All teams and their daily work are synchronized in the common schedule of iterations – the heartbeat of the project
• Sprint Length
– thirty days for a "traditional" software product
– two weeks for a fast moving web service
– weekly iterations might be appropriate for an early stage product, or for delivering rapid fixes on a project
that has a frustrated customer base and/or is in jeopardy of being cancelled.
– iteration cycles longer than four weeks risk behaving like traditional software projects.
4/19/2012 9
10. Sprint/Iteration
• Company Vision -> Product Visions -> Product Strategy-> Release Plan -> Product Requirement
Document (PRDs) -> Product Backlog -> Iteration Backlog -> Epic -> User Stories -> Tasks
• As the goal is to have a customer-ready deliverable at the end of each iteration, it is paramount to
have all the user stories of an iteration completed at the end of that iteration
• Get together with the project sponsor and create a joint vision for the project
• Write the resulting requirements into user stories that should on the one hand be complete but
also as simple as possible
• Acceptance test criteria should be defined for each story before the sprint to allow a clean sprint
exit
• The Sprint Fest is organized as an event in which all development teams give a demo of the use
case they have implemented in the most recent iteration
– Participants - entire team, including testers, product management, executive management,
and -if possible- customers as well
– Respective stakeholders get first hand information on the project progress
4/20/2012 10
11. User Stories
• Story has to be INVEST
– Independent - Avoid dependencies between stories
– Negotiable - They are not a command. Open to alternatives that might work better and/or require less effort
– Valuable—Always demonstrate why the story is worth implementing
– Estimable—The story should be small enough and contain enough detail that the development team can
estimate the effort.
– Small—A story should represent between a half-day and two weeks. Should fit into an iteration
– Testable—Acceptance criteria for the story should be able to be tested
• Each user story is now broken into tasks. These tasks are sized(and estimated) and assigned to
team members
• MMF (Minimal Marketable Feature) is a good way to start the story. MMF is normally an epic.
• Non-functional requirements (QOS) are written on the User Story as a constraint
– PAPRMIC - Performance, Accuracy, Portability, Reusability, Maintainability, Interoperability, Capacity
Sample User Story
Sample NFR
As an end user, I would like to calculate the value my
As a customer, I'd like to be able to use the browser of my
stocks based on the real-time value at the Stock Exchange
choice so I don't have to download a new browser.
so I can see the accumulated loss or gain.
Sample Constraint
Sample Tasks
The application shall run on Internet Explorer 7.x and
- Write test cases
higher, Firefox 3.x and higher, and Safari 4.x and higher.
- Integrate into test framework
- Get all stocks
- Get the current value
- Get exchange rates
- Calculate value
- Handle exceptions
4/19/2012 11
12. User Story Estimation – Ideal Days
• Ideal time is:
– The time it takes you to completely finish the user story or tasks.
– The time required to complete design, coding, automated test cases, testing, and
documentation and everything else the task requires.
– The time needed for just doing the work, without breaks, meetings, emails, other parallel
activities, colleagues asking you for advice, and all the other things that usually stop you from
completing the task.
• Ways to estimate
– Planning Poker
– Estimate by Analogy
4/19/2012 12
13. Metrics for Scrum Projects
• In a project, there should be a clear separation between
Defects: Something that prevents the product from functioning as specified.
Features: New functionality that is either in addition to what the product provides so
far or a change of behavior.
Refactoring needs: The program works as designed, but there are things that the
team wants to improve, for example to improve the maintainability or to remove
unused code.
4/19/2012 13
14. Product Backlog
Repriori
Add
tize
High priority,
high level of
Remove detail
Low priority,
low level of
detail
Pick the
highest
priority work
item
4/20/2012 14
15. Adopting Agile
Waterfall Model
Development Defect Backlog
Effort •Huge efforts in development during first half
•Huge efforts in testing and defect fixing during second
half
•Large number of open defects towards the end
Open Defects •No scope for significant scope changes during second
half
Testing Effort
Project Start Project End
Agile Model •Development, testing, defect fixing efforts evenly
distributed
Development
Effort •Small number of open defects towards the end
Defect Backlog •Scope changes possible any time
Testing Effort
Project Start Project End
4/20/2012 15
16. Pitfalls
• If team tries to deliver more in haste in an iteration, they can only deliver
less in the next iteration due to the bugs introduced in this iteration
• Agile does not mean NO documentation
• Rushing into implementation before stable design
• Bug fixing is non-productive. Customers pay us for adding feature not for
fixing bugs. Minimizing bugs maximizes time for features
• Jumping to a new functionality without resolving pending quality issues
4/20/2012 16
17. Nitty-gritty of Sprint
• Throughout the release, the teams maintain their team charter document, which includes the prioritized product
backlog with all use cases they tentatively want to address in the foreseeable future.
• Team elaborate a rough high-level design outlining all items of their focus area .
• Only the current iteration is being precisely planned, confirmed, and detailed into an iteration backlog, which lists
the low-level use case descriptions.
• Iterations are time-boxed. They have a defined start and end date. Usually, all teams operate on the same
iteration schedule.
• The content of each iteration is defined at the beginning of each iteration. A team picks the top use cases from the
prioritized product backlog in their team charter and starts designing and coding those items.
• Large user stories are broken in to into smaller, digestible chunks to ensure that a use case can be implemented
within an iteration.
• The teams continuously integrate their code throughout the iteration, documentation, and automated test cases
into a common code stream. There are daily builds of the entire product. Continuous integration with immediate
testing is done to avoid destabilization.
• Ensuring the stability of each build is everyone’s responsibility. Disruptive changes must be avoided by all means.
Every single developer will plan and perform thorough unit testing and automated regression for the code he is
delivering.
• It is a mandate to focus on any open issues and bugs first, before proceeding with the development of new
functionality
• Functional verification testing is part of the iteration within the team. Only tested and properly working use cases
are accepted as a delivered achievement.
• Performance and documentation are further aspects to be covered within the iteration.
• An ―Sprint Fest‖ is held at the end of each iteration
• Each iteration will be signed-off by the stakeholders, confirming that the delivered use cases are working properly
4/19/2012 17
18. Appendix A – Best Practices of Distributed Scrum teams
• Each site conducts a local standup in their morning to address immediate issues.
• All teams join a daily teleconference standup, ideally scheduled at a common work time for all. A
video-conference standup is better.
• Each location has a Scrum Master Proxy and a Product Owner Proxy. The proxies synch with
their counterparts regularly and learn to guide their local teams and keep them productive.
• Team members visit other sites to deepen relationships and information exchange.
• VOIP and webcams can go along way to overcoming cultural awkwardness and maintaining a co-
located feel
• Distributed teams also need to implement a collaboration tool to function as a virtual task board.
Eg. Rally Software, VersionOne, Xplanner.org, and Atlassian Jira with the GreenHopper plugin
• The Scrum of Scrums is a meeting of Scrum Masters (or other appropriate leads) from all the
product and shared resource teams. Unlike the Daily Scrum that meets every day, the Scrum of
Scrums is generally held between one and three times a week.
4/19/2012 18
19. Appendix B – Non-functional Requirement (PAPRMIC)
• Functional Requirement = "what the system will do"
• Non Functional Requirement = "how well the system will do it"
1. Performance: Ninety percent of product searches will return results in less than
three seconds.
2. Accuracy: The software will dynamically generate and adjust reorder points to
provide in stock levels of 98 percent for all standard products while maintaining
less than fourteen days' inventory on hand for 95 percent of all standard
products.
3. Portability: The software shall be designed to be ported to Android.
4. Reusability: The graphics rendering engine will be reusable by our other
applications.
5. Maintainability: Automated unit tests must be written for all new code and be run
after each build.
6. Interoperability: All documents shall be stored in XML.
7. Capacity: The data mart must be able to store one hundred and eighty million per
month for five years) and support the real-time analytics tools.
4/19/2012 19
20. Appendix C –PRD
1. Project goals—tie project to product strategy with measurable goals, such as market share, revenue, customer
satisfaction, productivity improvement, time to deployment, etc.
2. Timeline—target dates for key milestones.
3. Product Background and scope of release—describe whether this is a new product, next release, or an extension of
an existing product, and if it will complement or replace any existing products.
4. User interface constraint—any standards to which the user interface must comply
5. Compatibility constraint—any external and internal interfaces and backwards compatibility that must be developed or
maintained and may impact on other systems.
6. Scalability—system quality defining user, data volume, or transaction levels.
7. Usability and learnability—system quality definition for ease of use or ease of learning the system for a defined
persona.
8. Performance—system quality defining performance goals.
9. Documentation—any documents that must be created, consumer of documents, and intended use.
10. Security—any security issues that must be accommodated and standards that must be observed.
11. Regulatory—any regulation that must be supported.
12. Manageability—any requirements for customer support, account management, or operations to manage the system
and support customers.
13. Reporting—any new metrics that need to be captured and reported against.
14. International—any issues that must be accommodated to support international markets.
15. Assumptions—any assumption that could impact the project.
16. Open Issues—any unresolved issues that could impact the project.
4/19/2012 20
21. Appendix D - Product Vision
• Company vision might be: "Helping digital photography enthusiasts fulfill their passion.―
• The product vision, which might be considered the corporate mission (i.e., how we will fulfill the corporate vision)
might be: "The most comprehensive selection of equipment combined with the right advice to guide purchase for
the digital photography enthusiast.―
• This statement says a lot.
– First, we are going to carry a lot of products;
– second, we are targeting hobbyists;
– third, we will be providing advice that goes beyond the typical product catalog.
• As this translates into product trade-offs, we will emphasize making products easy to find and providing guidance
to help customers find the right product for their skill levels and interests.
• This is very different from
– choosing to be the low cost leader,
– choosing to serve the professional photography market,
– choosing to take a more paternalistic approach by carrying a limited set of "best in class" products.
4/19/2012 21
22. Appendix E – Impact of Agile on Marketing & Sales
• Increased revenue, as a result of capturing more customers sooner
• Lower costs by not over-building the product (ultimately you will realize more value for less
development effort);
• Better resource and prioritization decisions due to faster feedback cycles.
4/19/2012 22