A session held for students at San Jose State University. A live pair-programming session and these slides were used before that session. For the code in the live exercise, follow instructions in the slides.
This document discusses unit testing Typescript code using QUnit and Sinon. It covers:
1. The basics of QUnit and how to set up tests with it.
2. Writing Typescript tests using QUnit and Sinon, including basic mocking, mocking with Sinon, and advanced tips.
3. Different unit testing workflows including a manual workflow, an automated workflow using Grunt, scaffolding HTML runner files using Grunt, and using external modules.
The document provides code examples and demos of writing tests and different workflows. It is intended to teach best practices for unit testing Typescript code.
This document summarizes an agenda for a talk on TypeScript and test-driven development. It introduces TypeScript, discusses test-driven development principles and code katas. It then outlines doing a string calculator kata with TypeScript, Visual Studio and Jasmine as an example. The speaker is introduced as a technical lead who enjoys test-driven development, software architecture and TypeScript.
Go is an open source programming language designed for building simple, fast, and reliable software. It is concurrent and garbage collected, with tools to manage dependencies, support version control, and test code. The document discusses Go's philosophy, tools, web development capabilities using net/http, concurrency with goroutines, exception handling without exceptions, popular frameworks, organizations using Go, and references for learning more.
This document outlines a hands-on session on behaviour driven development (BDD) that uses the "CodeBreaker" guessing game as an example. It introduces the Gherkin language for writing BDD specifications, shows examples of Gherkin features and scenarios for the CodeBreaker game, and outlines the BDD development process and coding steps. It also lists feedback from the session and resources on BDD.
C++ Unit testing - the good, the bad & the uglyDror Helper
C++ is a powerful language when used by a seasoned developer. It is being used everywhere from operating systems and compilers to cross platform mobile apps development.
But this power comes with a cost - C++ programming is not simple nor easy – with memory leaks, stack overflows and strange exceptions, a software developer needs all of the power he can use.
By harnessing the power of unit tests a software developer can find defects quickly, avoid regression and speed up development time.
In this talk I’ll show how to use the right unit testing tools and practices available that will help you get your C++ code under control and even test legacy code which no one ever want to touch.
Do you have a healthy CI/CD pipeline? Do releases simply flow through? CI, CD, PRs, Pipelines, Releases, Deployments and all that jazz.
Whether you're new to Continuous Delivery or a hardened traveller down that road, this session has something for you. We’ll start with an exploration of branching strategy (releaseflow.org) before walking through a healthy continuous delivery configuration.
We’ll watch a code change make it's way through a pipeline to production and discuss how we can apply such practices to our everyday work.
The document discusses contributing to open source projects. It begins by asking participants about their experience with coding and git. It then lists many ways one can contribute such as documentation, bug reports, reviews, development, and translations. The rest of the document outlines an activity where participants are split into groups to collaboratively develop a calculator application implementing various math functions over multiple tasks. It provides guidance on development practices like coding style, testing, and using git. It concludes by discussing the open source development process and encouraging participants to get involved in a project.
The document discusses strategies for working with legacy C++ code, including gaining control over legacy code through iterative refactoring while ensuring existing functionality is maintained. It emphasizes learning what the code does, making sure it continues functioning properly, and making gradual improvements. Specific techniques mentioned include writing tests, creating fake objects to inject into code under test instead of real dependencies, and using templates or friendship to fake classes that are otherwise difficult to mock.
DevOpsDaysRiga 2018: Neil Crawford - Trunk based development, continuous depl...DevOpsDays Riga
Practices of trunk based development and continuous deployment have helped our six vertical slice product delivery teams be able to work together on a single product (and codebase) while maintaining rapid iteration and experimentation. With this talk I hope to inspire more teams to try these practices.
ATO 2014 - So You Think You Know 'Go'? The Go Programming LanguageJohn Potocny
The document is a presentation about the Go programming language. It provides a brief history of Go, noting it was created in 2007 by Google employees and became open source in 2009. It discusses some of Go's key features like being statically typed, garbage collected, and having built-in concurrency support. The presentation aims to show examples of writing simple programs in Go.
JavaScript was created in 1995 by Brendan Eich at Netscape and was influenced by languages like Self, Scheme, Java, C, and Perl. It is a client-side scripting language that allows for dynamic web page interactions and is used in both web pages and node.js applications. Major JavaScript engines include V8, SpiderMonkey, Chakra, and Rhino. The presentation provides an overview of JavaScript's history, uses, and influence on other languages like TypeScript, CoffeeScript, and Dart.
The document provides guidance for developers on best practices for writing code. It emphasizes following rules like clean code, code reviews, and refactoring. Key points include writing simple and readable code, avoiding duplication, learning from others, and ensuring code meets definitions of done that specify requirements like testing and code quality. Refactoring is advised to reduce technical debt by improving structure without changing functionality. Code reviews are recommended to catch defects through constructive peer review.
Great Android apps only include what's needed to achieve the goals of the product, not enhance the resume of the developer. What’s more, the more maintainable an application is, the more likely it will have increased user satisfaction and decreased time to market.
Improving Code Quality In Medical Software Through Code Reviews - Vincit Teat...VincitOy
The document discusses improving code quality in medical software through code reviews. It describes how one project implemented peer code reviews to prevent bugs, share knowledge, and improve discipline. The project evolved its workflow from long review cycles with many changes to immediate reviews of individual commits. Reviews check functionality, style, implementation, and readability. Commit messages are also reviewed to improve the project history. Tools like Git, Gerrit and Buildbot help automate version control, reviews and continuous integration.
JAZOON'13 - Andres Almiray - Spock: boldly go where no test has gone beforejazoon13
The document introduces Spock, a Groovy-based testing framework. It provides information about Spock's creator and key features, including its use of blocks like given, when, and then; lifecycle methods; data-driven testing capabilities using lists and tables; mocking interactions; and extensibility. The presentation encourages learning more about Spock's capabilities on its website and through existing plugins.
Don't be a git - the essentials you should know about git to use it correctly
Presentation by Otto Kekäläinen held at Vincit Teatime on Nov 11th 2015
http://www.vincitteatime.fi/
The document discusses different development strategies and tactics for driving software development, including test-driven development (TDT), domain-driven design (DDD), and behavior-driven development (BDD). It provides overviews of each approach and examples from real-world open source projects demonstrating how companies have implemented these strategies and tactics.
This document provides an overview of test driven development (TDD) and the RSpec testing framework in Ruby. It defines TDD as a software development process that was created in the 1990s to practice test-first design. RSpec is introduced as a popular testing framework for Ruby that supports behavior driven development (BDD). The basics of RSpec are explained, including the describe, context, and it methods for organizing tests and defining examples. Hooks and expectations are also summarized.
The document discusses building CI/CD workflows with OpenShift Container Platform and OpenShift Dedicated. It includes an agenda that outlines presentations and demos of CI/CD strategies using Source-to-Image, custom strategies, and pipeline strategies. The demos will utilize ImageStreams, BuildConfigs, DeploymentConfigs, and integrate Jenkins with Kubernetes and OpenShift. Resources used in the demos are linked in GitHub.
Spend some time working with OpenAPI and gRPC and you’ll notice that these two technologies have a lot in common. Both are open source efforts, both describe APIs, and both promise better experiences for API producers and consumers. So why do we need both? If we do, what value does each provide? What can each project learn from the other? We’ll bring the two together for a side-by-side comparison and pose answers to these and other questions about two API methodologies that will do much to influence the future of networked APIs.
Continuous Delivery for Python Developers – PyCon OttoPeter Bittner
Peter Bittner presented on continuous delivery for Python developers. He defined continuous delivery as building, testing, and releasing software faster and more frequently to put release schedules in the hands of business rather than IT. He discussed that continuous delivery requires version control, code reviews, build servers, artifact storage, hosting, and monitoring. He provided Python-specific examples of using tools like Tox, pytest, Docker, Travis CI, and README files to implement continuous delivery for a Python project.
This document discusses test-driven development (TDD) and unit testing. It begins with an introduction to TDD and examples using PHPUnit. It then explores the TDD cycle, common excuses for not using TDD, and pros and cons of TDD. Next, it distinguishes unit testing from TDD and discusses unit testing frameworks like PHPUnit and SimpleTest. Finally, it provides examples of code for a simple game that could be used to learn TDD and unit testing techniques.
Caleb Jenkins discusses best practices for writing automated unit tests, including having a test runner, setting the test context or scene, and handling dependencies through techniques like dependency injection and mocking. He advocates writing tests first to define requirements and ensure code meets expectations. Jenkins also addresses challenges with testing edges or interfaces and advocates separating UI/data logic from edges to increase testability.
Driving application development through behavior driven developmentEinar Ingebrigtsen
This document discusses Behavior Driven Development (BDD) and how it can be used to drive application development. It introduces BDD, focusing on behaviors of the system rather than tests. It discusses key aspects of BDD like Gherkin, units, test doubles, writing testable code, frameworks like SpecFlow and recommended reading. The overall message is that BDD changes the way software is developed by shifting the focus to behaviors and improving collaboration.
Do you have a healthy CI/CD pipeline? Do releases simply flow through? CI, CD, PRs, Pipelines, Releases, Deployments and all that jazz.
Whether you're new to Continuous Delivery or a hardened traveller down that road, this session has something for you. We’ll start with an exploration of branching strategy (releaseflow.org) before walking through a healthy continuous delivery configuration.
We’ll watch a code change make it's way through a pipeline to production and discuss how we can apply such practices to our everyday work.
The document discusses contributing to open source projects. It begins by asking participants about their experience with coding and git. It then lists many ways one can contribute such as documentation, bug reports, reviews, development, and translations. The rest of the document outlines an activity where participants are split into groups to collaboratively develop a calculator application implementing various math functions over multiple tasks. It provides guidance on development practices like coding style, testing, and using git. It concludes by discussing the open source development process and encouraging participants to get involved in a project.
The document discusses strategies for working with legacy C++ code, including gaining control over legacy code through iterative refactoring while ensuring existing functionality is maintained. It emphasizes learning what the code does, making sure it continues functioning properly, and making gradual improvements. Specific techniques mentioned include writing tests, creating fake objects to inject into code under test instead of real dependencies, and using templates or friendship to fake classes that are otherwise difficult to mock.
DevOpsDaysRiga 2018: Neil Crawford - Trunk based development, continuous depl...DevOpsDays Riga
Practices of trunk based development and continuous deployment have helped our six vertical slice product delivery teams be able to work together on a single product (and codebase) while maintaining rapid iteration and experimentation. With this talk I hope to inspire more teams to try these practices.
ATO 2014 - So You Think You Know 'Go'? The Go Programming LanguageJohn Potocny
The document is a presentation about the Go programming language. It provides a brief history of Go, noting it was created in 2007 by Google employees and became open source in 2009. It discusses some of Go's key features like being statically typed, garbage collected, and having built-in concurrency support. The presentation aims to show examples of writing simple programs in Go.
JavaScript was created in 1995 by Brendan Eich at Netscape and was influenced by languages like Self, Scheme, Java, C, and Perl. It is a client-side scripting language that allows for dynamic web page interactions and is used in both web pages and node.js applications. Major JavaScript engines include V8, SpiderMonkey, Chakra, and Rhino. The presentation provides an overview of JavaScript's history, uses, and influence on other languages like TypeScript, CoffeeScript, and Dart.
The document provides guidance for developers on best practices for writing code. It emphasizes following rules like clean code, code reviews, and refactoring. Key points include writing simple and readable code, avoiding duplication, learning from others, and ensuring code meets definitions of done that specify requirements like testing and code quality. Refactoring is advised to reduce technical debt by improving structure without changing functionality. Code reviews are recommended to catch defects through constructive peer review.
Great Android apps only include what's needed to achieve the goals of the product, not enhance the resume of the developer. What’s more, the more maintainable an application is, the more likely it will have increased user satisfaction and decreased time to market.
Improving Code Quality In Medical Software Through Code Reviews - Vincit Teat...VincitOy
The document discusses improving code quality in medical software through code reviews. It describes how one project implemented peer code reviews to prevent bugs, share knowledge, and improve discipline. The project evolved its workflow from long review cycles with many changes to immediate reviews of individual commits. Reviews check functionality, style, implementation, and readability. Commit messages are also reviewed to improve the project history. Tools like Git, Gerrit and Buildbot help automate version control, reviews and continuous integration.
JAZOON'13 - Andres Almiray - Spock: boldly go where no test has gone beforejazoon13
The document introduces Spock, a Groovy-based testing framework. It provides information about Spock's creator and key features, including its use of blocks like given, when, and then; lifecycle methods; data-driven testing capabilities using lists and tables; mocking interactions; and extensibility. The presentation encourages learning more about Spock's capabilities on its website and through existing plugins.
Don't be a git - the essentials you should know about git to use it correctly
Presentation by Otto Kekäläinen held at Vincit Teatime on Nov 11th 2015
http://www.vincitteatime.fi/
The document discusses different development strategies and tactics for driving software development, including test-driven development (TDT), domain-driven design (DDD), and behavior-driven development (BDD). It provides overviews of each approach and examples from real-world open source projects demonstrating how companies have implemented these strategies and tactics.
This document provides an overview of test driven development (TDD) and the RSpec testing framework in Ruby. It defines TDD as a software development process that was created in the 1990s to practice test-first design. RSpec is introduced as a popular testing framework for Ruby that supports behavior driven development (BDD). The basics of RSpec are explained, including the describe, context, and it methods for organizing tests and defining examples. Hooks and expectations are also summarized.
The document discusses building CI/CD workflows with OpenShift Container Platform and OpenShift Dedicated. It includes an agenda that outlines presentations and demos of CI/CD strategies using Source-to-Image, custom strategies, and pipeline strategies. The demos will utilize ImageStreams, BuildConfigs, DeploymentConfigs, and integrate Jenkins with Kubernetes and OpenShift. Resources used in the demos are linked in GitHub.
Spend some time working with OpenAPI and gRPC and you’ll notice that these two technologies have a lot in common. Both are open source efforts, both describe APIs, and both promise better experiences for API producers and consumers. So why do we need both? If we do, what value does each provide? What can each project learn from the other? We’ll bring the two together for a side-by-side comparison and pose answers to these and other questions about two API methodologies that will do much to influence the future of networked APIs.
Continuous Delivery for Python Developers – PyCon OttoPeter Bittner
Peter Bittner presented on continuous delivery for Python developers. He defined continuous delivery as building, testing, and releasing software faster and more frequently to put release schedules in the hands of business rather than IT. He discussed that continuous delivery requires version control, code reviews, build servers, artifact storage, hosting, and monitoring. He provided Python-specific examples of using tools like Tox, pytest, Docker, Travis CI, and README files to implement continuous delivery for a Python project.
This document discusses test-driven development (TDD) and unit testing. It begins with an introduction to TDD and examples using PHPUnit. It then explores the TDD cycle, common excuses for not using TDD, and pros and cons of TDD. Next, it distinguishes unit testing from TDD and discusses unit testing frameworks like PHPUnit and SimpleTest. Finally, it provides examples of code for a simple game that could be used to learn TDD and unit testing techniques.
Caleb Jenkins discusses best practices for writing automated unit tests, including having a test runner, setting the test context or scene, and handling dependencies through techniques like dependency injection and mocking. He advocates writing tests first to define requirements and ensure code meets expectations. Jenkins also addresses challenges with testing edges or interfaces and advocates separating UI/data logic from edges to increase testability.
Driving application development through behavior driven developmentEinar Ingebrigtsen
This document discusses Behavior Driven Development (BDD) and how it can be used to drive application development. It introduces BDD, focusing on behaviors of the system rather than tests. It discusses key aspects of BDD like Gherkin, units, test doubles, writing testable code, frameworks like SpecFlow and recommended reading. The overall message is that BDD changes the way software is developed by shifting the focus to behaviors and improving collaboration.
- Testing shows the presence, not the absence of bugs. Tests are driven by requirements and business rules, focusing only on relevant cases rather than testing everything.
- Tests improve quality and confidence by verifying that each scenario works as expected. Tests serve as live documentation of the system.
- While testing has been used for decades in different forms like debugging, demonstration, and evaluation, modern test-driven development and integrated testing frameworks from the 1990s helped establish testing as a mainstream practice.
● What is Unit Testing?
● Benefits
● What is Test Driven Development?
● What is Behavior Driven Development?
● Categories of (Unit) Tests / Software Testing
Pyramid, Frameworks
● C++, Java, .NET, Perl, PHP frameworks
● Unit-testing Zend Framework application
TDD involves writing tests before code to help design and develop software incrementally. It can find defects earlier and make software easier to maintain with fewer bugs. While difficult to learn, TDD seeks to build better modular code through a simple iterative process. Starting small with katas and practicing regularly, including pair programming, can help adapt to TDD's mechanics. Though challenges exist, it is worth trying TDD to potentially improve software quality and reduce costs over time.
This document provides an introduction to automated testing. It discusses the motivations for automated testing such as improving quality and catching bugs early. It covers basic testing concepts like unit, integration, and system tests. It explains testing principles such as keeping tests independent and focusing on visible behavior. The document also discusses popular testing frameworks for different programming languages and provides examples of tests from a codebase.
Test Driven Development With YUI Test (Ajax Experience 2008)Nicholas Zakas
This document discusses test-driven development (TDD) using the YUI Test framework. It introduces TDD principles like writing tests before code and iterating through failing tests, passing tests, and refactoring. It then covers key aspects of YUI Test like writing unit tests, simulating events, handling asynchronous code, and hooking into the test runner. The document provides examples and recommendations for effectively using TDD and YUI Test in web development.
Automated testing overview discusses the importance of software testing and automated testing. It defines software testing as verifying that software meets requirements and works as expected. The document covers different types of testing and why automated testing is needed to reduce costs, protect reputation, and address difficulties in testing. It provides examples of unit testing simple objects, objects with dependencies, and user interfaces to illustrate how to implement automated tests.
(automatic) Testing: from business to university and backDavid Rodenas
This talk cares about the fundamentals of testing, a little bit history of how the professional community developed what we currently know as testing, but also about why I should care about testing? why is it important to do a test? What is important to test? What is not important to test? How to do testing?
There some examples in plnker just to see each step, and many surprises.
This talk also compares what people learned in the Computer Sciences and Engineering degrees and what people does in testing. It gives some tips to catch up with current state of art and gives some points to start changing syllabus to make better engineers.
This talk is good for beginners, teachers, bosses, but also for seasoned techies that just want to light up some of the ideas that they might have been hatching.
Spoiler alert: testing will save you development time and make you a good professional.
Agile Testing: A pragmatic overview and new entry in Intelliware’s Agile Methodology Series.
What you’ll learn in this presentation:
Intelliware’s Chief Technologist, BC Holmes, provides a pragmatic overview of Agile testing. Complete with many examples, this presentation is ideal for those looking for a practical take on software testing in an Agile environment.
The presentation covers:
- Why do we use Agile testing?
- What Agile testing isn’t
- What Agile testing is: unit testing and test-driven development (TDD)
- High-level properties of good tests
- Testing in different languages
- Test suites and code coverage
- Using mock objects to help isolate units
- Beyond unit testing
Intelliware’s Chief Technologist, BC Holmes, provides a pragmatic overview of Agile testing. Complete with many examples, this presentation is ideal for those looking for a practical take on software testing in an Agile environment.
Learn about the benefits of writing unit tests. You will spend less time fixing bugs and you will get a better design for your software. Some of the questions answered are:
Why should I, as a developer, write tests?
How can I improve the software design by writing tests?
How can I save time, by spending time writing tests?
When should I write unit tests and when should I write system tests?
This document introduces automated testing and provides guidance on how to implement it. It discusses:
1) The benefits of unit tests such as finding bugs quickly, preventing regressions, and improving design.
2) The different types of automated tests including unit, system, and performance tests. Unit tests are fast and robust while system tests test entire systems.
3) How to set up an automated testing environment including tools for different languages, integrating tests into development workflows, and using build servers to run tests on commits.
Test-Driven Developments are Inefficient; Behavior-Driven Developments are a ...Abdelkrim Boujraf
The document discusses the authors' experience with different testing strategies at their company StratEx. They initially used Selenium for UI testing but found it did not help when they frequently changed screens. They then investigated Test-Driven Development (TDD) but found it inefficient, as tests are also code that must be written and maintained. Behavior-Driven Development (BDD) showed more promise as it focuses on functionality rather than architecture and bridges communication between users and developers. However, no methodology fully describes large, complex systems. The search for the best testing approach is ongoing.
Test driven development as the state of the art of todays software developement. These slides provides a short introduction into test driven development (TDD) and gives some arguments why you should use tddTDD or why not
Test and Behaviour Driven Development (TDD/BDD)Lars Thorup
In this introduction to Test Driven Development (TDD) or Behaviour Driven Development (BDD) we give a high level description of what it is and why it is useful for developers. Then we go into some details on stubs and mocks, test data, UI testing, SQL testing, JavaScript testing, web services testing and how to start doing TDD/BDD on an existing code base.
The document discusses techniques for making test-driven development (TDD) more enjoyable. It provides examples of conversations where a programmer asks if they can have quality assurance write tests, and whether tests are needed if code is working. The creator of TDD notes that tests should be written to reach a high level of confidence, not just to print "OK". Several rationalizations for not writing tests are debunked. The document advocates designing programs by writing tests first, and making initial tests fail on purpose in order to have the short-term goal of fixing them. This focuses effort and makes the process more fun. Less testing is needed than achieving 100% coverage; tests should be written when most useful, such as for new code
FEI Digital Week Webinar at Innovation Management - October 2019 SmartOrg
Presenter: Ralph Morales III, formerly of HP.
On his innovation journey, Ralph once played the role of controller for an innovative business delivering on its milestones but failing to create enterprise value. It wasn’t tracking the world’s evidence of value. As an innovation scout, he was a witness to HP’s Smartwatch team accomplishing market traction and subsequent de-funding for failing meaningful scaling potential. Incomplete lean methods provided little value of evidence, which led the team astray. In the last chapter of his innovation journey, experience and skill combine to deliver innovation accountability and superior returns in his role as Director of Innovation. A winning formula for Return on Innovation is feasible with the proper framework.
Learn how to sustain innovative spirit in the face of hardship, match the language of innovation to the language of executives, and a missing key to breakthrough growth.
The webinar replay can be watched here: https://bit.ly/2CANrF4
Comic Book: Adventures in Product InnovationSmartOrg
This comic book was created for SmartOrg, Inc. by intern Puneet Sharma in 2015. It captures product sales conversations that go south due to the IT question from hell, "Why can't we build this in-house?"
The document is a worksheet to help evaluate the quality of decision making. It provides a scale from 0% to 100% for various factors involved in making high quality decisions. These factors include having a useful perspective, meaningful inquiries, distinct directions considered, credible information sources, clear metrics to measure options against, and insightful reasoning. The highest quality decision making also includes developing actionable plans, maintaining aligned intentions and commitment, as well as balancing rational thinking with emotional motivation.
Embedded DA vs Consultative DA: Audience WorkshopSmartOrg
At DAAG 2014, in the Ubiquitous DA: Embedded DA session on Mar 27, 2014 at Boston, David Matheson facilitated an audience workshop to reflect on the differences between Embedded DA and Consultative DA. The first four slides are a summary of speaker talks in that session, while the rest are the result of audience contributions. The original flipchart photos are also included.
Embedded Decision Analysis: Systems Design PatternsSmartOrg
This deck was presented at INFORMS on Mar 27, 2014 by Somik Raha, for the session "Ubiquitous DA: Embedded Decision Analysis", and looks at design patterns for system design in the context of Embedded DA.
The document discusses design strategies for building multi-page applications with AngularJS. It describes mapping routes to controllers and views, defining controllers as TypeScript classes to encapsulate logic, and binding views to controllers with Angular directives. Key aspects covered include defining routes with $routeProvider, implementing controllers to handle routes, and linking templates to controllers.
Stanford-SDG Webinar Six critical principles of strategic portfolio managementSmartOrg
The document discusses six critical principles of strategic portfolio management:
1) Aligned decision forum - Drive real decision making and conflict resolution at all levels.
2) Value creation focus - Maximize value created across the organization.
3) Credible, comparable evaluations - Allow participants to make and accept decisions.
4) Embrace uncertainty and dynamics - Treat uncertainty explicitly.
5) Clear communication and learning - Share information, update it, and improve results.
6) Inclusive, collaborative process - All stakeholders participate openly and benefit.
The document provides examples and discussion of how to apply these principles to strategic portfolio management. It also includes polls to gauge participants' interests and challenges.
A talk given to the Society of Decision Professionals by Somik Raha on Jul 23, 2014
Abstract: When we hear “values,” we interpret it in three different ways: cultural norms, metrics for tradeoffs (if you happen to be a decision analyst), or distinguishing between means and ends (if you’ve read “Value-Focused Thinking”). This talk will share a fourth way of hearing the term “values,” offering an interpretation of values as “meta-strategy” by understanding intrinsic purpose. Exploring intrinsic purpose is unfamiliar territory, and stories will be shared on how such an exercise helped unlock the creative juice of an organization, gave dignity to their work and transformed their frame. Along the way, a $2 million portfolio turned into a $30 million portfolio. That story and other experiments in mapping the values of organizations will be shared. A reformulation of the six elements of decision quality along the head and heart dimensions will also be offered.
A great technology and a compelling customer need are necessary but not sufficient to change the world. What is missing? This workshop on failing forward explores common model of innovation, pivoting and generating insights and results.
The document provides an overview of bringing agile principles and practices to business development. It begins with defining business development and describing the agile manifesto values of collaborative development, working models/software, customer collaboration, and responding to change. It then contrasts traditional versus agile approaches to business development. The remainder of the document discusses evaluating options using techniques like option value analysis and outlines an agenda to apply agile practices like collaborative development and learning from failures to business development.
Accelerating the deployment of technology to business opportunities-chevron T...SmartOrg
ChevronTexaco implemented a value-based management process and tools to optimize its heavy oil technology portfolio and accelerate the deployment of technologies. The process provided standard templates and metrics to consistently evaluate and compare projects. It helped prioritize projects based on their expected value, technical risk, and alignment with business strategy. Tracking project uncertainties and outcomes provided transparency. The results included faster initiation and deployment of projects, earlier termination of less promising projects, and increased portfolio value through accelerated technology development.
Principles of strategic portfolio managementSmartOrg
This document discusses principles of strategic portfolio management and provides an overview of SmartOrg, a consulting firm that helps companies improve their portfolio management processes. Some key points:
- David Matheson is the President and CEO of SmartOrg. He has helped companies improve results from portfolio management, product development, and other areas.
- SmartOrg provides software, services, and training to help companies build their capability for strategic portfolio management. This includes tools to evaluate projects, focus stakeholders, and compare portfolios.
- Good strategic portfolio management principles include having an aligned decision forum, focusing on value creation, using credible and comparable evaluations, embracing uncertainty, and having an inclusive process.
This presentation gives actionable insight on your innovation project helping you to improve your ability to formulate innovation projects. The presentation provides five must-do's of innovation management and making innovation soar.
Patterns that support agile business development. These patterns can also be called Evaluation Patterns, for they provide the building blocks to take an evaluation-driven approach to funding R&D.
This document provides an overview of framing in decision making. It discusses how a frame acts as a limited description that filters what is relevant to a problem. Inappropriate frames can lead to poor decisions. The document then discusses different patterns and tools that can be used to properly frame a decision problem, such as establishing what is at stake, selecting the right size process, communicating the strategy arc, using issue raising as an icebreaker, employing the whine bottle technique, identifying hidden assumptions, and using a decision hierarchy. The overall intent is to provide a catalog of patterns and tools to help structure the framing phase of a decision process.
"Hymenoptera: A Diverse and Fascinating Order".pptxArshad Shaikh
Hymenoptera is a diverse order of insects that includes bees, wasps, ants, and sawflies. Characterized by their narrow waists and often social behavior, Hymenoptera play crucial roles in ecosystems as pollinators, predators, and decomposers, with many species exhibiting complex social structures and communication systems.
IDSP is a disease surveillance program in India that aims to strengthen/maintain decentralized laboratory-based IT enabled disease surveillance systems for epidemic prone diseases to monitor disease trends, and to detect and respond to outbreaks in the early phases swiftly.....
Students will research and orally present a Colombian company using a visual tool, in order to develop their communication skills and intercultural understanding through the exploration of identity, innovation, and local culture, in connection with the IB global themes.
Stewart Butler - OECD - How to design and deliver higher technical education ...EduSkills OECD
Stewart Butler, Labour Market Economist at the OECD presents at the webinar 'How to design and deliver higher technical education to develop in-demand skills' on 3 June 2025. You can check out the webinar recording via our website - https://oecdedutoday.com/webinars/ .
You can check out the Higher Technical Education in England report via this link 👉 - https://www.oecd.org/en/publications/higher-technical-education-in-england-united-kingdom_7c00dff7-en.html
You can check out the pathways to professions report here 👉 https://www.oecd.org/en/publications/pathways-to-professions_a81152f4-en.html
Prottutponnomotittwa: A Quiz That Echoed the Pulse of Bengal
On the 31st of May, 2025, PRAGYA – The Official Quiz Club of UEM Kolkata – did not merely organize another quiz. It hosted an ode to Bengal — its people, its quirks, its politics, its art, its rebellion, its heritage. Titled Prottutponnomotittwa, the quiz stood as a metaphor for what Bengal truly is: sharp, intuitive, spontaneous, reflective. A cultural cosmos that thrives on instinct, memory, and emotion.
From the very first slide, it became clear — this wasn’t a quiz made to showcase difficulty or elitism. It was crafted with love — love for Bangla, for its past, present, and its ever-persistent contradictions.
The diversity of the answer list tells the real story of the quiz. The curation was not random. Each answer was a string on a veena of cultural resonance.
In the “Cultural Pairings” round, Anusheh Anadil and Arnob were placed not just as musicians, but as voices of a modern, cross-border Bangla. Their works, which blend baul, jazz, and urban folk, show how Bengal exists simultaneously in Dhaka and Shantiniketan.
The inclusion of Ritwik Chakraborty and Srijit Mukherjee (as a songwriter) showed how the quiz masters understood evolution. Bangla cinema isn’t frozen in the Ray-Ghatak past. It lives, argues, breaks molds — just like these men do.
From Kalyani Black Label to Radhunipagol Chal, consumer culture too had its place. One is liquid courage, the other culinary madness — both deeply Bengali.
The heart truly swelled when the answers touched upon Baidyanath Bhattacharya and Chandril. Both satirists, both sharp, both essential. It was not just about naming them — it was about understanding what different types of literature means in a Bengali context.
Titumir — the play about a peasant rebel who built his own bamboo fort and dared to challenge the British.
Krishnananda Agamvagisha — the mystical Tantric who shaped how we understand esoteric Bengali spiritualism.
Subhas Chandra Bose — the eternal enigma, the braveheart whose shadow looms large over Bengal’s political psyche.
Probashe Ghorkonna — a story lived by many Bengalis. The medinipur daughter, who made a wholesome family, not only in bengal, but across the borders. This answer wasn’t just information. It was emotion.
By the end, what lingered was not the scoreboard. It was a feeling.
The feeling of sitting in a room where Chalchitro meets Chabiwala, where Jamai Shosthi shares the stage with Gayatri Spivak, where Bhupen Hazarika sings with Hemanga Biswas, and where Alimuddin Road and Webskitters occupy the same mental map.
You don’t just remember questions from this quiz.
You remember how it made you feel.
You remember smiling at Keet Keet, nodding at Prabuddha Dasgupta, getting goosebumps at the mention of Bose, and tearing up quietly when someone got Radhunipagol Chal right.
This wasn’t a quiz.
This was an emotional ride of Bangaliyana.
This was — and will remain — Prottutponnomotittwa.
How to Create Time Off Request in Odoo 18 Time OffCeline George
Odoo 18 provides an efficient way to manage employee leave through the Time Off module. Employees can easily submit requests, and managers can approve or reject them based on company policies.
How to Use Owl Slots in Odoo 17 - Odoo SlidesCeline George
In this slide, we will explore Owl Slots, a powerful feature of the Odoo 17 web framework that allows us to create reusable and customizable user interfaces. We will learn how to define slots in parent components, use them in child components, and leverage their capabilities to build dynamic and flexible UIs.
Order Lepidoptera: Butterflies and Moths.pptxArshad Shaikh
Lepidoptera is an order of insects comprising butterflies and moths. Characterized by scaly wings and a distinct life cycle, Lepidoptera undergo metamorphosis from egg to larva (caterpillar) to pupa (chrysalis or cocoon) and finally to adult. With over 180,000 described species, they exhibit incredible diversity in form, behavior, and habitat, playing vital roles in ecosystems as pollinators, herbivores, and prey. Their striking colors, patterns, and adaptations make them a fascinating group for study and appreciation.
TechSoup Microsoft Copilot Nonprofit Use Cases and Live Demo - 2025.05.28.pdfTechSoup
In this webinar we will dive into the essentials of generative AI, address key AI concerns, and demonstrate how nonprofits can benefit from using Microsoft’s AI assistant, Copilot, to achieve their goals.
This event series to help nonprofits obtain Copilot skills is made possible by generous support from Microsoft.
Updated About Me. Used for former college assignments.
Make sure to catch our weekly updates. Updates are done Thursday to Fridays or its a holiday/event weekend.
Thanks again, Readers, Guest Students, and Loyalz/teams.
This profile is older. I started at the beginning of my HQ journey online. It was recommended by AI. AI was very selective but fits my ecourse style. I am media flexible depending on the course platform. More information below.
AI Overview:
“LDMMIA Reiki Yoga refers to a specific program of free online workshops focused on integrating Reiki energy healing techniques with yoga practices. These workshops are led by Leslie M. Moore, also known as LDMMIA, and are designed for all levels, from beginners to those seeking to review their practice. The sessions explore various themes like "Matrix," "Alice in Wonderland," and "Goddess," focusing on self-discovery, inner healing, and shifting personal realities.”
Introduction to Online CME for Nurse Practitioners.pdfCME4Life
Online CME for nurse practitioners provides a flexible, cost-effective way to stay current with evidence-based practices and earn required credits without interrupting clinical duties. Accredited platforms offer a wide range of self-paced courses—complete with interactive case studies, downloadable resources, and immediate digital certificates—that fit around demanding schedules. By choosing trusted providers, practitioners gain in-depth knowledge on emerging treatments, refine diagnostic and patient-management skills, and build professional credibility. Know more at https://cme4life.com/the-benefits-of-online-cme-for-nurse-practitioners/
The PDF titled "Critical Thinking and Bias" by Jibi Moses aims to equip a diverse audience from South Sudan with the knowledge and skills necessary to identify and challenge biases and stereotypes. It focuses on developing critical thinking abilities and promoting inclusive attitudes to foster a more cohesive and just society. It defines bias as a tendency or prejudice affecting perception and interactions, categorizing it into conscious and unconscious (implicit) biases. The content highlights the impact of societal and cultural conditioning on these biases, particularly within the South Sudanese context.
♥☽✷♥
Make sure to catch our weekly updates. Updates are done Thursday to Fridays or its a holiday/event weekend.
Thanks again, Readers, Guest Students, and Loyalz/teams.
This profile is older. I started at the beginning of my HQ journey online. It was recommended by AI. AI was very selective but fits my ecourse style. I am media flexible depending on the course platform. More information below.
AI Overview:
“LDMMIA Reiki Yoga refers to a specific program of free online workshops focused on integrating Reiki energy healing techniques with yoga practices. These workshops are led by Leslie M. Moore, also known as LDMMIA, and are designed for all levels, from beginners to those seeking to review their practice. The sessions explore various themes like "Matrix," "Alice in Wonderland," and "Goddess," focusing on self-discovery, inner healing, and shifting personal realities.”
♥☽✷♥
“So Life Happens-Right? We travel on. Discovering, Exploring, and Learning...”
These Reiki Sessions are timeless and about Energy Healing / Energy Balancing.
A Shorter Summary below.
A 7th FREE WORKSHOP
REiki - Yoga
“Life Happens”
Intro Reflections
Thank you for attending our workshops. If you are new, do welcome. We have been building a base for advanced topics. Also, this info can be fused with any Japanese (JP) Healing, Wellness Plans / Other Reiki /and Yoga practices.
Power Awareness,
Our Defense.
Situations like Destiny Swapping even Evil Eyes are “stealing realities”. It’s causing your hard earned luck to switch out. Either way, it’s cancelling your reality all together. This maybe common recently over the last decade? I noticed it’s a sly easy move to make. Then, we are left wounded, suffering, accepting endless bad luck. It’s time to Power Up. This can be (very) private and quiet. However; building resources/EDU/self care for empowering is your business/your right. It’s a new found power we all can use for healing.
Stressin out-II
“Baby, Calm down, Calm Down.” - Song by Rema, Selena Gomez (Video Premiered Sep 7, 2022)
Within Virtual Work and VR Sims (Secondlife Metaverse) I love catching “Calm Down” On the radio streams. I love Selena first. Second, It’s such a catchy song with an island feel. This blends with both VR and working remotely.
Its also, a good affirmation or mantra to *Calm down* lol.
Something we reviewed in earlier Workshops.
I rarely mention love and relations but theres one caution.
When we date, almost marry an energy drainer/vampire partner; We enter doorways of no return. That person can psychic drain U during/after the relationship. They can also unleash their demons. Their dark energies (chi) can attach itself to you. It’s SYFI but common. Also, involving again, energy awareness. We are suppose to keep our love life sacred. But, Trust accidents do happen. The Energies can linger on. Also, Reiki can heal any breakup damage...
(See Pres for more info. Thx)
How to Setup Renewal of Subscription in Odoo 18Celine George
A subscription is a recurring plan where you set a subscription period, such as weekly, monthly, or yearly. Based on this period, the subscription renews automatically. In Odoo 18, you have the flexibility to manage renewals either manually or automatically.
Forestry Model Exit Exam_2025_Wollega University, Gimbi Campus.pdfChalaKelbessa
This is Forestry Exit Exam Model for 2025 from Department of Forestry at Wollega University, Gimbi Campus.
The exam contains forestry courses such as Dendrology, Forest Seed and Nursery Establishment, Plantation Establishment and Management, Silviculture, Forest Mensuration, Forest Biometry, Agroforestry, Biodiversity Conservation, Forest Business, Forest Fore, Forest Protection, Forest Management, Wood Processing and others that are related to Forestry.
Based in Wauconda, Diana Enriquez teaches dual-language social studies at West Oak Middle School, guiding students in grades 6-8. With a degree from Illinois State University and an ESL/Bilingual certification, she champions diversity and equity in education. Diana’s early experience as a special education paraprofessional shaped her commitment to inclusive and engaging learning.
Dashboard Overview in Odoo 18 - Odoo SlidesCeline George
Odoo 18 introduces significant enhancements to its dashboard functionalities, offering users a more intuitive and customizable experience. The updated dashboards provide real-time insights into various business operations, enabling informed decision-making.
5. Waterfall is a result of human
confusion
5
“Managing the Development of Large Software Systems”, Dr.
Winston W. Royce (Link) - 1970
6. 6
For some mysterious reason, people latched
on to Fig 2, and thought it looked like a
waterfall.
The name caught up and ushered in
“phased” mindset of development.
8. 8
And a Fig. 4! As far back as 1970, Royce
was describing the
beginnings of an agile
mindset, but the Waterfall
religion had already
started, based on a
misunderstanding!
9. Meanwhile, a community of philosophers in
software engineering started forming in the
90’s
9
Ward Cunningham
Founding of the WikiWikiWeb in 1994.
Ward’s wiki became the home for
conversations on Design Patterns.
10. 10
1995, caused a revolution in
Object-Oriented thinking
Book knows as the
“Gang of Four”
11. The false religion of Waterfall was then seriously
challenged in 2000
11
12. 12
Source: agileatlas.org
Barry Boehm’s Cost of Change Curve
We were initially justified in doing high-quality design when
computer time was more expensive than programmer time
13. 13
Aspirational Cost of Change curve
But now, programmer time is much more expensive, and we
would love to flatten the curve
time
costofchange
This is what Extreme Programming
was inviting us to consider
16. XP’s success led to a broader umbrella under a
more neutral-sounding “Agile Software
Development”
16
Core practices like TDD and Refactoring are no longer
controversial - they are a part of a programmer’s foundation.
Martin Fowler’s book is now a classic.
Most conventional IDEs support automated
refactoring.
17. 17
Erich Gamma
One of the Gang of Four, authored
JUnit with Kent Beck, while on a long flight together,
1997
Great Article by Alberto Savoia: Beautiful Tests
History of xUnit by Martin Fowler
“JUnit took off like a rocket - and was essential to supporting
the growing movement of Extreme Programming and Test
Driven Development. I've seen a huge change of attitude
towards testing in the last decade, and I think JUnit played a
big role in that. By being small and simple it encouraged
people to learn and use it. It also proved amenable to others
extending it integrating it into tools.” — Martin Fowler
18. Lots of JUnit ports, generally
referred to as xUnit
18
nUnit - C#
cppUnit - C++
pyunit- Python
24. We will use TypeScript
24
Anders Hejlsberg
Creator of C# and
TypeScript
Superset of Javascript
Supports class-based OO concepts
Takes the tedium out of JS
Keeps you in JS paradigm
(as opposed to coffee script)
25. We will use Testem
25
Continuously runs our unit tests
26. Step 1. git clone https://github.com/behappyrightnow/anagram.git
Step 2. cd anagram
Step 3. git checkout step1
Step 4. Install NodeJS from http://nodejs.org/
Step 5. npm install testem
Let’s start with checking out a basic stub from
Github
26
27. Let’s start by writing tests
27
Come up with 5 English words, jumble them up
Find all other words you can create with those letters
List your tests.
e.g.
INPUT OUTPUT
leppa apple
rodo door, odor
28. Challenge for you
28
Make the following game using existing codebase to help
game show hosts construct a puzzle.
Given an input word, create clues by adding one extra letter.
INPUT OUTPUT
rose horse without “h”
sores without “s”
Game show host can now use this program to construct
their show saying:
Can you find flowers using this clue…
Your web-interface should provide this:
29. PASS 1: Write the code without any tests
PASS 2: Keep your code aside, write tests first and then write code
Reflection: Write an essay on what you learned by comparing Pass 1 and
Pass 2, and in general what you learned from this session
Crack this challenge in the following way:
29