In this presentation, Roni explains the basics of Kanban and the principles governing the application of Kanban for process improvement. We also look at a comparison between Scrum and Kanban and visit the basic differences between them.
It includes pointers telling what’s wrong with the current system, history of Kanban, introduction to Kanban, benefits of using Kanban, practices used in Kanban, principles of Kanban, how is Scrum different from Kanban. The tutorial begins with details about the current system and what’s wrong with it. It includes pointers like burnout, low throughput, unidentified bottlenecks, too much work which tell what’s wrong with the current system.
Followed by is a section about the history of Kanban which includes points like how the name originated, who discovered it, design, visual signals, based on which system. Resulting in an introduction section which talks about Kanban, what method it uses, scheduling system, what it consists of, amount of work, identification etc. Next comes the benefits section which includes the benefits of using Kanban like helps in visualizing the system, allows to evaluate, identify bottlenecks, establish trust in process etc.
Afterwards there is a section about Kanban practices. It includes practices used in Kanban like visualize, limit WIP in each phase of development, managing flow by keeping it under monitor, make policies explicit, improve collaboratively through the use of scientific models and some terms like lead time, cycle time, throughput etc. Moreover, it also includes the board for easy visualization, story card for keeping track, charts for measurement, control charts to measure average time taken for each task, cumulative flow diagrams showing relative amount of work.
Then comes the principles of Kanban. It includes principles which should be used in Kanban like agree to pursue incremental, evolutionary change, optimize what already exists, respect the current process, roles, responsibilities, leadership at all levels to empower the workforce to bring about change. The last section of this tutorial is Scrum vs Kanban. It explains how scrum is different from Kanban by giving pointers like Scrum prescribes roles, time boxed iterations, backlog items must fit, limit WIP in a different way. It also includes pointers giving reason why it shouldn’t matter because emphasis should be on the goal and not the tool.
Kanban is the simplest approach which is currently used in software development. Since Kanban prescribes close to nothing there are often a lot of basic questions about the method.
The presentation depicts what Kanban is generally using Scrum as a reference point. Then it presents a series of situations to answer basic questions about working with Kanban
Kanban is a tool that allows you to fully visualize the status of your processes through a board with dynamic columns that make all tasks and processes steps clear.
Kanban 101 workshop by John Goodsen and Michael Sahota.
This covers everything you will need to know to play Russell Healy's Kanban Game: visualizing the work, metrics, and creating explicit policies.
Slides are available on request. Please email me.
Implementing Kanban to Improve your WorkflowJennifer Davis
Tutorial from LOPSA East
System, network, and security senior engineers manage intricate relationships ensuring that everything from simple tasks to complex projects gets completed in a timely manner. In this workshop, we will talk about using agile processes to identify, visualize, and improve work.
Outline:
Overview of the kanban process. What is kanban?
Identify common problems.
Define common terminology explicitly.
Work through common problems as a group using kanban.
Identify metrics for improvement.
Review, next steps, additional resources.
At the end of this tutorial, attendees will have a solid understanding of kanban and agile processes to take back to their environments.
Kanban method in four easy steps. Enjoy kanban.
Kanban in 4 easy steps is one of the most popular Kanban presentations. Learn how to successfully implement Kanban in your business process or life. Get to know basic Kanban principles and to see how easily you can improve your productivity using Kanban boards.
Kanban is the simplest approach which is currently used in software development. Since Kanban prescribes close to nothing there are often a lot of basic questions about the method.
The presentation depicts what Kanban is generally using Scrum as a reference point. Then it presents a series of situations to answer basic questions about working with Kanban
Kanban is a tool that allows you to fully visualize the status of your processes through a board with dynamic columns that make all tasks and processes steps clear.
Kanban 101 workshop by John Goodsen and Michael Sahota.
This covers everything you will need to know to play Russell Healy's Kanban Game: visualizing the work, metrics, and creating explicit policies.
Slides are available on request. Please email me.
Implementing Kanban to Improve your WorkflowJennifer Davis
Tutorial from LOPSA East
System, network, and security senior engineers manage intricate relationships ensuring that everything from simple tasks to complex projects gets completed in a timely manner. In this workshop, we will talk about using agile processes to identify, visualize, and improve work.
Outline:
Overview of the kanban process. What is kanban?
Identify common problems.
Define common terminology explicitly.
Work through common problems as a group using kanban.
Identify metrics for improvement.
Review, next steps, additional resources.
At the end of this tutorial, attendees will have a solid understanding of kanban and agile processes to take back to their environments.
Kanban method in four easy steps. Enjoy kanban.
Kanban in 4 easy steps is one of the most popular Kanban presentations. Learn how to successfully implement Kanban in your business process or life. Get to know basic Kanban principles and to see how easily you can improve your productivity using Kanban boards.
Imported from Japan, Kanban is an agile methodology that is gaining a lot of traction. Kanban, or Japanese for signal card, is a process that focuses on transparency and limiting the work in progress. By utilizing Kanban, you can pinpoint the bottlenecks and address them easily. In this session you will learn what Kanban is, how it evolved from its roots in the Toyota Production System (TPS) and lean manufacturing to software development, Kanban’s benefits, and how best to implement a Kanban system. We’ll also discuss when not to use Kanban and how to modify other agile methodologies, such as Scrum, to be used in conjunction with Kanban.
A Kanban board is a work and workflow visualization tool that enables you to optimize the flow of your work. It utilizes a visual cues that tell you what to produce, how much to produce and when to produce it. This presentation contains brief information related to Kanban board like what is Kanban board, how Kanban works and how to start with Kanban board.
In this 1-hour webinar you’ll learn what Lean is, why Lean is good for business and how some of the basic Lean concepts like 8 Wastes and Visual Management can improve and transform your operation.
Download the slides and more at https://goleansixsigma.com/webinar-introduction-to-lean/
Start your free Yellow Belt Training at http://www.goleansixsigma.com/free-lean-six-sigma-training/
Get The 8 Wastes Poster at https://goleansixsigma.com/product/the-8-wastes-poster/
Finding a way to do things more efficiently is important - no matter what business you are in or what kind of projects you do.
Check out the basic Kanban principles that might change the way you work.
Good luck!
Updated version at https://www.slideshare.net/GiulioRoggero/kanban-board-82363781
Do you have a team that works on both project and maintenance? Do you need to organize your team activities? Do you have a lot of activities in parallel and the time to market it's a problem? With a Kanban board and an Agile approach you can solve your problems!
Take a look of the animation of the slides to discover how it works.
Learn How to Implement Kanban in Lean Manufacturing. This presentation gives an overview of
1. What is a Kanban?
2. Why Kanban?
3. Types of Kanban.
4. How to Implement a Kanban System in a Production / Shop Floor
Imported from Japan, Kanban is an agile methodology that is gaining a lot of traction. Kanban, or Japanese for signal card, is a process that focuses on transparency and limiting the work in progress. By utilizing Kanban, you can pinpoint the bottlenecks and address them easily. In this session you will learn what Kanban is, how it evolved from its roots in the Toyota Production System (TPS) and lean manufacturing to software development, Kanban’s benefits, and how best to implement a Kanban system. We’ll also discuss when not to use Kanban and how to modify other agile methodologies, such as Scrum, to be used in conjunction with Kanban.
A Kanban board is a work and workflow visualization tool that enables you to optimize the flow of your work. It utilizes a visual cues that tell you what to produce, how much to produce and when to produce it. This presentation contains brief information related to Kanban board like what is Kanban board, how Kanban works and how to start with Kanban board.
In this 1-hour webinar you’ll learn what Lean is, why Lean is good for business and how some of the basic Lean concepts like 8 Wastes and Visual Management can improve and transform your operation.
Download the slides and more at https://goleansixsigma.com/webinar-introduction-to-lean/
Start your free Yellow Belt Training at http://www.goleansixsigma.com/free-lean-six-sigma-training/
Get The 8 Wastes Poster at https://goleansixsigma.com/product/the-8-wastes-poster/
Finding a way to do things more efficiently is important - no matter what business you are in or what kind of projects you do.
Check out the basic Kanban principles that might change the way you work.
Good luck!
Updated version at https://www.slideshare.net/GiulioRoggero/kanban-board-82363781
Do you have a team that works on both project and maintenance? Do you need to organize your team activities? Do you have a lot of activities in parallel and the time to market it's a problem? With a Kanban board and an Agile approach you can solve your problems!
Take a look of the animation of the slides to discover how it works.
Learn How to Implement Kanban in Lean Manufacturing. This presentation gives an overview of
1. What is a Kanban?
2. Why Kanban?
3. Types of Kanban.
4. How to Implement a Kanban System in a Production / Shop Floor
Concepts of cutover planning and managementSanjay Choubey
Global Business Transformation, SAP, ERP, Cutover Management, Manufacturing Excellence, Blackout period Management, Direct and Indirect Procurement, Business Intelligence, Data Management and Analytic,
Now that you have chosen the right business productivity platform for your business, you must consider the factors when migrating your data to your new platform. The planning and processes involved in transitioning from one platform to another is a major undertaking. And with so many different migration paths to and from the cloud, the migration process can be a challenge, especially if you do not have the expertise or technical staff in-house.
Learn from two Microsoft Exchange & Office 365 migration experts on how to make the migration easy, no matter which platform you have selected.
During this presentation you will learn:
• The differences between mindSHIFT’s Hosted Exchange Security Bundle and Office 365 Business Premium Package
• How to make the migration as easy as possible for whatever business productivity platform you select
• The different migration methods for each platform and how to determine what is best for your business
To view part 1 of this 2-part series, please visit: http://www.mindshift.com/Resources/Webinars/Hosted-Exchange-vs-Office-365.aspx
A strategic approach to Human Resource Management
Please see:
https://flevy.com/browse/business-document/strategic-human-resources-147
For an improved version
How to make strategy work in a complex and unpredictable world. In its essence, strategy is simple. It is about answering two fundamental and interrelated questions: where to play and how to win.
Almost 200 Scandinavian top managers, managers and strategists participated in an intensive day at Implement Consulting Group focusing on how to develop a winning strategy in a world that is increasingly unpredictable.
Strategist and author of the bestseller Playing to Win, Roger Martin was challeging the typical strategy processes where we try to control the risk and uncertainty through elaborate and detailed planning. In his opinion these processes often seem to end up being long-winded, abstract and complex. Sometimes even without any clear choices being made.
Explores the underlying reasons why project managers often fear the CMMI, explains that their negative reaction is sometimes justified, and offers practical guidance on how to avoid this undesirable (and unsustainable) state.
First delivered at the NDIA CMMI Technology Conference in Denver, November 2011. [CmmiTraining.com]
Contains a quick review of the Scrum process, talks about the dangers of trying to map PMBOK to Scrum, and then tries to talk about the concepts behind managing an Agile project using Scrum.
Principles and Practices in Continuous Deployment at EtsyMike Brittain
Presented at ALM Forum 2014.
Like what you've read? We're frequently hiring for a variety of engineering roles at Etsy. If you're interested, drop me a line or send me your resume: mike@etsy.com.
http://www.etsy.com/careers
In the 1940s, Toyota developed a scheduling system to improve their manufacturing production. Aligning the supply of materials with the demand of the production line reduced the amount of inventory in the system, and enabled a flexibility never before seen in the automobile industry.
Over the years, teams dealing with knowledge work (e.g. software development) adapted many of these ‘lean’ ideas, such as limiting the amount of work in progress, to improve the flow of work through their system.
Ideal for product owners, business analysts, developers, testers, and any users of Agile/Scrum, this presentation explains the basics of this system, called Kanban, and how it can be used to improve workflow and delivery rate.
Kanban is a scheduling system for lean manufacturing and just-in-time manufacturing. Kanban is an inventory-control system to control the supply chain. Taiichi Ohno, an industrial engineer at Toyota, developed kanban to improve manufacturing efficiency.
Kanban is a simple logical approach to project and task management.
What you will learn.
What’s wrong?
Why Kanban?
What is Kanban & it’s origins
How to use Kanban
Possible ways to use Kanban
Tools for KanBan
Educaterer India is an unique combination of passion driven into a hobby which makes an awesome profession. We carve the lives of enthusiastic candidates to a perfect professional who can impress upon the mindsets of the industry, while following the established traditions, can dare to set new standards to follow. We don't want you to be the part of the crowd, rather we like to make you the reason of the crowd.
Today's Effort For A Better Tomorrow
The following inforgraph gives a brief description about Node.JS and it's best practices.
Node.JS is the fastest growing and the most significant server side framework. It is built on Javascript to unify frontend and server side architectures.
Node.JS is ideal for high performance, for applications which require a highly scalable framework.
There are a lot of benefits of using Node.JS such as it works in JS language, good community support, backend used by companies like LINKEDIN, EBAY and many more.
This infograph also gives pointers about the best practices to be adopted while using Node.JS which are as follows:
Proper callback convention - Modules which expose an error-first callback interface.
Handle errors separately - divide errors into two parts, operational error and programming error.
Use a style guide - coding standards which are included are indent rules, variable naming and lots of other things.
Develop simpler modules - Develop modules that can be easily replicated.
Use RPC protocol - For real-time web apps.
and many more practices like Not reinventing the wheel, starting a project with Npm, use async patterns and practising test driven development.
These are the practices which are a necessity while using Node.JS as a framework.
The following infograph talks about UX and the techniques of UX which can be used by a user for building smarter products which is important for enhancing user satisfaction.
A user just cannot overlook experience design or UX while aiming to build smarter websites or applications.
What is Experience Design or UX?
UX design is the process of enhancing user satisfaction by improving usability, accessibility and pleasure emerging from the user and product interaction.
Here are the 10 techniques of UX for building smarter products-
Design real-time – Keeping in mind the micro interactions like content focused design, MAYA concepts etc.
Know your audience – Match the layout, font styles, overall design aesthetics with the audience’s expectations and personality.
Spontaneous Feedback – Use feedback messages to convey important information to users.
Keep it simple and consistent – Make navigation simple, interactive and easy to understand.
Design as per finger targets – While designing for small screens, give sufficient space to swipe and touch.
And many more pointers like Implementing a visual hierarchy, checking for fold, simplifying your forms, collaborating to succeed and avoiding multiple actions.
These are the 10 Pragmatic UX techniques for building smarter products like websites and applications which can help improve the user experience.
Swift- The future of iOS app development.
Since its evolution it has impacted the mobile app development industry drastically with modifications in the developers’ workflow.
77.6% developer around the globe have preferred Swift over Objective C for iOS app development.
This inforgraph includes a chart showing the key differences between Swift and Objective C like:
12 Key points which make Swift more effective than Objective C:
Paradigm- Objective C is class based object oriented but Swift is object oriented and functional.
Platform- Objective C is a basic editor whereas Swift is an interactive WYS/WYG editor.
Supported OS- Objective C is a cross- platform but Swift supports only iOS, OSx.
Execution time- Objective C needs more time as complete code is built every time whenever a change is made to the code but Swift takes less time as unchanged files aren’t recompiled.
Code Lengths - Objective C requires extensive coding whereas Swift requires comparatively smaller coding.
Code maintenance – In Objective C codes are difficult to maintain but in Swift codes are easy to maintain as it resembles the English language.
And many more points like Enuma, Readability, Type definition, Year of Advent etc are stated in the chart which prove that Swift is way more effective than Objective C and is also a more preferred language than Objective C.
Gulp is a front-end development tool.
It is basically a streaming build system which provides a way of doing automatic tasks that you have to do yourself again and again.
It's easy to use and very efficient. It all depends on plugins that are intended to only do one job each.
View the deck to know more about Gulp.
This tutorial is about Spring Boot.
The tutorial includes an introduction to Spring Boot, key features of Spring Boot, prototyping using CLI, managing profiles aka environment in Grails, using GORM and using GSP. The tutorial begins with a section which is an introduction to Spring Boot. It includes an introduction to Spring Boot, the benefits of using Spring Boot.
Following is a features section which includes the key features of Spring Boot like embedded servers, security, metrics etc. Next is a section about prototyping. It includes prototyping using CLI, getting started, the things that happen during prototyping, starter POMs and a demo, building Gradle, using plugin and adding dependencies, and hot reloading.
Consecutively there is a section about managing profiles. It includes managing profiles aka managing environment in Grails like binding properties and its examples, using spring data to add dependency. Moreover, there's also a section which includes using GORM for next level persistence and also includes server side view template libraries like JSP, velocity, tiles, GSP etc.
The last section of this tutorial is about GSP. It includes using GSP with Spring Boot as it has limited tags, adds dependency and helps in packaging executable JAR and WAR files.
This tutorial is an overview on elastic beanstalk. The tutorial includes an introduction to elastic beanstalk, working architecture, basic operation, console(demo) and a summary. Beginning of the tutorial is an introduction to elastic beanstalk. It includes an overview of elastic beanstalk and how it manages applications. It also includes the basic features of elastic beanstalk.
Following is a section of the working architecture. It involves the basic architecture and workflow of elastic beanstalk and explains it in detail. It also involves the benefits of using elastic beanstalk such as root access, easy configuration etc.
Moreover, it also includes the environments elastic beanstalk can work under such as docker, node.js etc. as well as the sample policies. The last section of the tutorial includes a demo of the console of elastic beanstalk and a summary as for the practices which take place "under the hood".
Content Migration involves migrating all the content assets to the new system. In this presentation, the fundamentals of migrating content to the AEM are covered. You can learn more about content migration here - http://insights.tothenew.com/cq-aem-migrating-content-to-aem
The tutorial includes principles, key difference between manual and automated, 5 steps to basic migration, 3 steps to an ETL cycle. The tutorial begins with a section on principles which includes principles of content migration to AEM.
Following is a section on key differences between manual and automated. It includes differences like approach, control over content, time taken, type of coding, times to be tested for migrating content to AEM.
In addition to this, is a section on steps to basic migration. It includes 5 keys steps to a basic content migration flow like obtaining, cleaning, organizing, ensuring URLs, uploading. The last section of this tutorial is on steps to an ETL cycle. It includes 3 key steps of an ETL cycle like extaction, transformation, loading. It also includes using sling posts, content loader as well as package manager.
AWS CodeDeploy is the new service announced at AWS re:Invent in Las Vegas!!!
AWS CodeDeploy is a fully managed, scalable deployment service that lets AWS certified developers and engineers quickly and simply automate the process of deploying and updating applications on Amazon EC2.
The presentation includes an introduction to Code Deploy, benefits of using Code Deploy, understanding various components and workflows of Code Deploy, ways to deploy an application, commands to create and push application using Code Deploy, steps to deploying code on instances, troubleshooting and limitations of Code Deploy. It begins with a section which gives a brief introduction to Code Deploy. The next section is about the benefits of using Code Deploy. It explains the benefits of using Code Deploy like automated deployments, centralized control etc. Specific to the benefits section comes components and workflows of Code Deploy. It briefly describes the components of Code Deploy like content, appsec file and also includes the steps to the workflow of Code Deploying. Then deploying an application which explains not just the steps to deploy an application but also answers what to deploy, how to deploy and where to deploy at the same time.
Then, comes a section about commands used to create and push application. It tells about the commands which are not just used to create an application to s3 but also push applications to s3. Then it covers the steps for deploying code on instances. It becomes really interesting as it explains the steps a user can use to deploy codes on instances by just creating an application and following the other steps.
The last section of this presentation is about the limitations and troubleshooting of Code Deploy. It tells about the troubleshooting which occurs while using Code Deploy and the troubleshooting which appears but also mentions the regions where Code Deploy is currently supported too.
IntelliGrape has in-depth experience in Big Data analytics, and help empowers customers with agile, scalable and cost-effective solutions. Our Big Data expertise includes Consulting, Implementation and Managed services.
Over recent years, JavaScript has increasingly gained popularity, partly due to libraries that are developed to make JavaScript apps/effects easier to create for those who may not have fully grasped the core language yet.
While in the past it was a common argument that JavaScript was a basic language and was very ‘slap dash’ with no real foundation; this is no longer the case, especially with the introduction of high scale web applications and ‘adaptations’ such as JSON (JavaScript Object Notation).
Many developers cast off JS as a suitable OOP language because they are so used to the class style of C# and Java. Many people don't realize that JavaScript supports inheritance. When you write object-oriented code it instantly gives you power; you can write code that can be re-used and that is encapsulated.
It includes functions and objects, prototype based programming, class based-prototype based, some hacks and exercises. The tutorial begins with a section about function and objects which includes a simple JS function, closures as one of the most powerful weapons for JS ninja, object as it is almost everything for a JS ninja, call and apply methods defined under functions. The function section is followed by the prototype section which includes a brief on class based vs prototype based.
After this comes the hack section. It includes some hacks like appending new array to another array, swap variable values and many more. The last section of this tutorial is on exercises which includes some basic exercises like implementing basic inheritance, add forEach method, implement a function.
The agenda of the slides are to discuss some basic and in-depth details of MongoDB and NoSQL.
A snapshot of the topics discussed:
- Introduction to NoSQL and MongoDB
- Installation
- Queries
- Indexing
- Schema modeling
- Aggregation
This tutorial is an introduction to MongoDB and NoSQL. The tutorial includes an introduction to MongoDb and NoSQL, installation, queries related to MongoDB and NoSQL, aggregation framework, indexing of MongoDB and NoSQL and schema modelling. The tutorial begins with a section on introduction. This section includes an introduction to NoSQL, its data models like document model, graph model, key value etc. It also includes an introduction to MongoDB and its data model.
The introduction section is then followed by the installation section. This section includes installing MongoDB, default directory, starting MongoDB server, starting Mongo shell and more steps. It also includes adding documents. The next section is about queries related to MongoDB and NoSQL. This section includes query collection which are selecting all documents, find by example, use OR condition, use AND condition, update query. It also includes removing documents.
Then comes a section about aggregation framework. This section includes a brief about aggregation framework process and its samples. The next section is about indexing. This section involves indexing for speeding up of search and sorting, types of indexes like single field, compound field, multiple index etc. The last section of the tutorial is about schema modelling. This section includes schema design factors like rich documents, no mongo joins, no constraints, atomic operation etc.
(AWS) Auto Scaling : Evening Session by Amazon and IntelliGrape SoftwareTO THE NEW | Technology
IntelliGrape Software in association with AWS presented an Evening Session on AWS CloudFront & Auto Scaling at Hyatt Regency, Delhi on 27th September. The event saw engagement from CEOs, CTOs and CIOs of e-commerce companies, start-ups and enterprises with a purpose to understand CloudFront and Auto Scaling better.
Some of the fundamental questions every digital business, especially the infrastructure teams within the business, ask is cost, scale, speed, flexibility and wastage reduction. Agenda of the session was to share views and discuss on how AWS CloudFront & Auto Scaling endeavors to address these questions.
The tutorial includes load scenarios, business scenarios, under/over provisioning, introduction to auto scaling, how auto works, points to remember, things to remember and snapshots. The tutorial begins with load scenario which includes the load scenarios of auto scaling like unpredicatable and predicable bursts. Following is a business scenario which includes different kinds of business scenarios. Alongside, there is a section about under/over provisioning. It includes over provisioning and under provisioning in respect to infrastructure and time.
Furthermore, there's an introduction to auto scaling which includes auto scaling as a cloud computing service and some features. The next section is on working of auto scaling. It includes a brief about how auto scaling works for users and servers. Moreover, there is also a section on points to remember. It includes point which should be kept in mind while using auto scaling before scaling it down or out. An addition to this is a section on things to remember which includes things like launching, differentiating, scaling and regions. The last section of this tutorial includes snapshots taken from a conference held by TO THE NEW.
Introduction
Benefits
Concepts
Templates
CLI Tool
Cloud Formation Demo
Cloud Former (Intro)
Questions
The tutorial includes an introduction to Cloud formation, benefits to Cloud formation, concepts of Cloud formation, CLI tool, Cloud formation demo, introduction to Cloud former. The tutorial begins with an introduction to Cloud formation subsequent to which, there is another section talking about the benefits of Cloud formation. It also includes the services which are used by Cloud formation.
The next section is based on the concepts of Cloud formation. This section is important as it explains the concepts of Cloud formation which are template and stack. The Template section includes the description, objects, sample template, parameters, resources, types of resources and also the steps to create a template. Whereas, the Stack section includes the collection of resources, resources which are created or deleted. Afterward comes the CLI Tool. This section includes the CLI tool called CFN.
The CLI tool section is then followed by a Cloud formation demo. It not only gives a demo of Cloud formation and which templates would be useful. But, it also includes the issues which are present in the Cloud formation demo. The last section includes an introduction to Cloud former. It provides the description of Cloud former as to which tool and architecture it uses and also the things which are possible while using Cloud former.
A quick Description about presentation:
• What is ElasticSearch and how it works.
• How ElasticSearch works to analyze data splitting a document into meaningful portions and indexing each of those portions separately. So whenever a new search request comes in, it knows what to find.
• Features and advantages of ElasticSearch like built in sharding defaults, maintaining fail-safe node clusters, automatically adding a new node without having to reboot and so on.
• Out of the box features for today’s applications like faceted search, reverse search using Percolators and pre-built Analyzers.
The tutorial includes big data search, contenders, intro to elasticsearch, more than just search, unchartered territory. Beginning is a brief detail about big data search which includes big data search in terms of rapid consumption and the challenges faced by big data search. Following is a section about contenders. It includes contenders like lucene, apache soir, sphinx and ElasticSearch itself.
Moreover, there is also an introduction section to ElasticSearch. It includes an introduction to ElasticSearch as a search server and it's features like push replication, node auto discovery, fail-safe. It also includes data analyzing and ways of indexing it right. Afterwards, there is a section on more than search which includes factors more than just search functions like facets, range facet, histogram facet, geo facet, percolator and ElasticSearch percolating.
The last section of this tutorial includes unchartered territory. It includes territories like ElasticSearch and NoSQL database, situations in cases of WHAT IF and references.
Know all the latest happenings in the world of Grails in JULY. All the information has been compiled and explained with proper redirection to know more about the same.
INtelligrape Provides agile tsolution to programming quesries. With its team of experienced software programmers, we are capablle of working on various languages.
Spock testing gives you the option of testing your grails application with accurate results.
The tutorial includes a Testing overview, understanding how unit Testing works, brief about Spock Unit Testing, Writing Unit test cases, Demo & exercise. The tutorial begins with a section which gives an overview on Testing. It includes the reason to test a program, a way of thinking about testing and also includes integral development through testing like unit testing, integration testing, functional testing, acceptance testing. The overview section is followed by the Understanding section. It includes understanding unit testing, disadvantages of unit testing like test cases, advantages of unit testing like facilitating changes, simplifying integration, evolving design etc.
Afterward comes a section about Spock Testing. It includes a brief about Spock Testing, basics about Spock Testing, specifications of Spock Testing. The next section is a brief about Unit test cases. It includes Writing Unit test cases like fields like declarations, fixture methods for setting up the environment, blocks like setup, expect, where, expert block and an example.
The last section of this tutorial is about the exercises on Testing. This section can also be called Data driven Testing and includes data tabes which are a feature method, data pipes which connect a data variable to a data provider, @unroll which has its iterations reported independently, exception conditions which tell us about when a block should throw an exception, mocking which is used for implementing objects, test mixins which enhance the behavior of a typical JUNIT, test for annotations which is a class under test, mock annotations which create a mock version of any collaborators, cardinality describes how often a method call is expected and at last stubbing which is an act to respond to the method calls.
Demo application available at https://github.com/hiteshBhatia/vertx-imagetransformation.git
It includes inroduction to VERTX, key advantages and concepts, internals and demos. It begins with an introduction to VERTX section which includes an introduction to VERTX and its features. It also includes reasons of using VertX. Following is a section on key advantages and concepts. It includes advantages of using VertX like nature, scalability etc. It also includes key concepts like verticle, event bus, event loop, worker thread, module and how VertX works on these concepts.
In addition to this, there is a section on internals and demos which includes open source projects, demo applications, architecture of these demo applications in form of producer, queue, consumers, workers, event bus. The last section of the tutorial covers up a summary section. It includes a brief summary of VertX and pointers to look something forward to like integration, language support, creation of modules etc.
In these series of slides, Bhagwat introduces us to Heroku, the PaaS which is redefining the way in which apps are deployed to the cloud.
The tutorial includes heroku and cloud computing, process model, dynos manifold, deployment stack, usage and billing, CLI. It begins with an introduction section which includes a brief on heoku and cloud computing, how heroku works, using GIT with Heroku.
Following is a section on process model. It includes the process model of heroku and the type as well as the web application. Afterward, comes a section on dynos. It includes the dynos manifold, composition, providing environment. In addition to this, is a section on deployment stack which includes base operating system, language runtime, associated libraries and add-on services of Heroku.
The last section of the tutorial is about usage and billing. It includes usage charges and a free trial. It also includes sample commands like GIT, config, sharing, process, add-ons, postgres commands and a postgres back up.
Elevating Tactical DDD Patterns Through Object CalisthenicsDorra BARTAGUIZ
After immersing yourself in the blue book and its red counterpart, attending DDD-focused conferences, and applying tactical patterns, you're left with a crucial question: How do I ensure my design is effective? Tactical patterns within Domain-Driven Design (DDD) serve as guiding principles for creating clear and manageable domain models. However, achieving success with these patterns requires additional guidance. Interestingly, we've observed that a set of constraints initially designed for training purposes remarkably aligns with effective pattern implementation, offering a more ‘mechanical’ approach. Let's explore together how Object Calisthenics can elevate the design of your tactical DDD patterns, offering concrete help for those venturing into DDD for the first time!
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.
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.
The Art of the Pitch: WordPress Relationships and SalesLaura Byrne
Clients don’t know what they don’t know. What web solutions are right for them? How does WordPress come into the picture? How do you make sure you understand scope and timeline? What do you do if sometime changes?
All these questions and more will be explored as we talk about matching clients’ needs with what your agency offers without pulling teeth or pulling your hair out. Practical tips, and strategies for successful relationship building that leads to closing the deal.
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/
Generating a custom Ruby SDK for your web service or Rails API using Smithyg2nightmarescribd
Have you ever wanted a Ruby client API to communicate with your web service? Smithy is a protocol-agnostic language for defining services and SDKs. Smithy Ruby is an implementation of Smithy that generates a Ruby SDK using a Smithy model. In this talk, we will explore Smithy and Smithy Ruby to learn how to generate custom feature-rich SDKs that can communicate with any web service, such as a Rails JSON API.
LF Energy Webinar: Electrical Grid Modelling and Simulation Through PowSyBl -...DanBrown980551
Do you want to learn how to model and simulate an electrical network from scratch in under an hour?
Then welcome to this PowSyBl workshop, hosted by Rte, the French Transmission System Operator (TSO)!
During the webinar, you will discover the PowSyBl ecosystem as well as handle and study an electrical network through an interactive Python notebook.
PowSyBl is an open source project hosted by LF Energy, which offers a comprehensive set of features for electrical grid modelling and simulation. Among other advanced features, PowSyBl provides:
- A fully editable and extendable library for grid component modelling;
- Visualization tools to display your network;
- Grid simulation tools, such as power flows, security analyses (with or without remedial actions) and sensitivity analyses;
The framework is mostly written in Java, with a Python binding so that Python developers can access PowSyBl functionalities as well.
What you will learn during the webinar:
- For beginners: discover PowSyBl's functionalities through a quick general presentation and the notebook, without needing any expert coding skills;
- For advanced developers: master the skills to efficiently apply PowSyBl functionalities to your real-world scenarios.
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/
Accelerate your Kubernetes clusters with Varnish CachingThijs Feryn
A presentation about the usage and availability of Varnish on Kubernetes. This talk explores the capabilities of Varnish caching and shows how to use the Varnish Helm chart to deploy it to Kubernetes.
This presentation was delivered at K8SUG Singapore. See https://feryn.eu/presentations/accelerate-your-kubernetes-clusters-with-varnish-caching-k8sug-singapore-28-2024 for more details.
Securing your Kubernetes cluster_ a step-by-step guide to success !KatiaHIMEUR1
Today, after several years of existence, an extremely active community and an ultra-dynamic ecosystem, Kubernetes has established itself as the de facto standard in container orchestration. Thanks to a wide range of managed services, it has never been so easy to set up a ready-to-use Kubernetes cluster.
However, this ease of use means that the subject of security in Kubernetes is often left for later, or even neglected. This exposes companies to significant risks.
In this talk, I'll show you step-by-step how to secure your Kubernetes cluster for greater peace of mind and reliability.
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.
Builder.ai Founder Sachin Dev Duggal's Strategic Approach to Create an Innova...Ramesh Iyer
In today's fast-changing business world, Companies that adapt and embrace new ideas often need help to keep up with the competition. However, fostering a culture of innovation takes much work. It takes vision, leadership and willingness to take risks in the right proportion. Sachin Dev Duggal, co-founder of Builder.ai, has perfected the art of this balance, creating a company culture where creativity and growth are nurtured at each stage.
3. 1. What’s wrong with the currentsystem?
2. History of Kanban
3. What isKanban?
4. Why Kanban?
5. Kanban Practices
6. Creating your firstboard
7. Kanban Principles
8. How is Scrum different fromKanban?
Agenda
4. − Burnout
− Frequent bugs on production
− Complaints about productivity
− Low throughput
− Leads to vaguesprint planning
− Too much work stuffed into one sprint
− Unidentified bottlenecks
What’s wrong with the current system?
6. − Developed by Taichi Ohno at Toyota in 1940's
− Designed after the shelf-stocking techniques used by supermarkets
− Demand controlled system where replenishment happened based on
market conditions
− Based on a pull based system rather than a push based one
− Use of visual signals was essential to the system
History of Kanban
7. − Scheduling system used in manufacturing to help companies improve
their production process
− Adopted by software co's for JITdelivery without burdening
developers
− “The Kanban Method” for software dev pioneered by David J.
Anderson
− WIP limited pull system which exposes system problemsthrough
visualization
What is Kanban?
8. − In its simplest form, a kanban system consists of a big board with story
cards
− Board represents the state of the project at any point
− Different from other visualizations –implements WIPlimits
− Tries to limit the amount of work at any stage
− Easy identification of bottlenecks in system through visual boards
− Aims atminimizing waste states
What is Kanban? (contd.)
10. … because …
− it helps in visualising the system and expose problems
− it allows us to evaluate the impacts of process changes
− it allows us to identify bottlenecks and alleviate them
− it allows us to establish trust in theprocess
− it helps us to maintain a sustainable pace with a sustainable
throughput
− you need to relax and Kanban advocates just that!
But why Kanban?
12. − Workflow is inherently invisible
− Visualization is core toKanban
− Enables people to take a quick look at the state of the workflow
− Use of story cards can be used
− Development process is dividedinto columns
− Each task is specified on a story card
− Essentially cards move along the board to show workflow
Visualize
13. − Apply limits on WIP in each phase of development
− Isthe basis for implementing a pull based system
− Work is pulled into the next phase once capacity is available
− Improves quality by giving greater focus to fewer tasks
− Also reduces lead time for work by reducing the number of concerns
for the developer
Limit WIP
14. − Because maximum utilization ofresources is not desirable contraryto
popular belief
− Brings in slack into the system –creates a more conducive work
process
− Get the most important things done, one by one, with a clear focus
− Things get done faster, better than before, leading to lesser rework
Limit WIP (contd.)
15. − Workflow should be closely monitored
− Measurements must be made to identify problems in the system
− Leads to better understanding of the system and helps inmaking
educated improvements
− Helps identify the positive and negative impact of changes
introduced in thesystem
Manage flow
16. − All policies related to workflow management should be explicit
− For eg. WIP limits, basic workflow, rejection/acceptance flow,
definition of donenessetc.
− Helps in providing a basis for process improvement based on statistics
− Allows for a more rational approach to process improvement by
logical reasoning
Make policies explicit
17. − Through the use of scientific models
− Popular models: Theory ofConstraints (TOC)
− Use of models allows a team to make predictions about a change
− The expected and actual result can then be used effectively to improve
the process
− This approach leads to learning both at individual and organizational
level
Improve Collaboratively
18. Thingsyou need:
− A board
− Lots of Post-it notes (preferably of different colors)
− And lots of commitment (very important)
− The next slides!
Getting Started
19. Importantterms:
− Lead Time –time taken from request of feature to its completion
− Cycle Time –time taken to finish the task
− Throughput –essentially refers to productivity. Defined as the amount
of work delivered in a time frame
− WIP Limit Value Stream –this refers essentially to yourdevelopment
process
− Swarm(ing) –collaboration on a problem
And some terms...
20. − Allows easy visualization of the
development process
− Each columnrepresents one
Fig.TheKanban Board
phase in yourexisting development process
− Numbers on top representWIP limits
− The number of tasks in each phase is limited by the WIP limits specified
The Board
21. − Keeps track offeatures/tasks
− Ismore of an XP related feature
− Includes informationregarding
transition of features on board
− Post-it notes can be used
− Different colored post-it notes can be used for different issue
types such as bugs, features, tasks, improvement etc
− TIP–Token, Inscription, Placement
Fig.StoryCard
Story Card
22. − Measurement tools to measure the effectiveness of the system
− Every time card ispushed/pulled on/off the board, charts start
changing
− Can be used to interpret various important metrics like average time
taken for a task to be completed
− Can be used to identify the flow of work
− Also useful to identify the state of tasks in each phase of development
− Control Charts & Cumulative Flow Diagrams
Charts
24. − Are used to measure the average time taken for a task to be
processed
− Lead time and cycle time is represented on a control chart
− Simplest charts that can be drawn
− The aim is to keep lead time and cycle time as low as possible
Control Chart
26. − Show relative amount of work for each stage
− Use of colored areas for each phase for easy identification of
bottlenecks
− Vertical distance of the chart shows how many tasks are on the board
and helps you set right WIP limits
− Horizontal distance allows you to monitor Cycle Time
− CFD should runsmoothly
− Large steps or horizontal lines indicate problems in flow
− Variations in gap/band indicate bottlenecks
− When the band gets too wide, it indicates problems in work finishing or
developers unable to handle amount of work
Cumulative Flow Diagrams
27. − Identifyyourdev process
− How are featuresdecided?
− What are the various steps involved in materializing it?
− Define startand end pointsforthe board
− Identify your boundaries
− Identify when a task enters the board
− Identify the end of its life cycle on the board
Let’s get started
28. − Agree
− Initial WIP limits and policies –can change later
− Prioritization and selectionpolicies
− Policies for different classes of service (expedite, standard, fixed
delivery date, intangible)
− Process review cycle time
Let’s get started (contd.)
32. − Do not prescribe any new roles or responsibilities to implement the
new system
− No such thing as “Kanban Software Development Process”
− Implement Kanban with existingsystem
-David Anderson
Start with what you do now!
33. − Optimize what alreadyexists
− Agree to continuous, incremental and evolutionary change to
improve the system
− Keep experimenting to understand the effects of changes on the
system
− Make small changes rather than huge process changes
-David Anderson
Agree to pursue incremental, evolutionary
change
34. − Do not remove existing roles and titles
− This will eliminate fears in introducing the new system in the
organization
− Will help you get broader support in introducing the new system
− Kanban was designed to reduce resistance to change
-David Anderson
Respect the current process, roles,
responsibilities
35. − Empower the workforce to bring about change
− Swarm on a bottleneck for faster resolution
− Hold frequent discussions and process improvements
− Include everyone in these discussions and do not disregard anyone’s
viewpoint
-David Anderson
Leadership at all levels
37. Splityour product
Splityourorganization
Large team spending a long timebuilding a huge thing
Smallteam spending a littletimebuilding a small thing
… but integrating regularly tosee the whole
Optimize yourprocess
Order the backlog
Splittime
43. − Emphasis should be on the goal and not the tool. Becoming/agile
lean is not thegoal
− Don’t be dogmatic about your process
− There is no good or bad tool. Only good or bad decisions
− Keep experimenting for understanding and not judgment
− Process isnot important, improvingthe process is important
Does it matter?
45. − David J Anderson, Kanban - Successful Evolutionary Change for your
Technology Business, 1st ed, Blue Hole Press,2010
− Henrik Kniberg, 2009, “Kanban and Scrum –Making the Most of
Both”, Online, Available: http://goo.gl/oiqPG
− Images from www.kanbantool.com/kanban-analytics-and-metrics
References
46. Thiswork islicensed under the Creative
Commons Attribution-Noncommercial-Share
Alike 3.0License
License
47. Contact us
Our Office
Client
Location
KANBAN practice is the
lifeline of any Software
development done at TO
THE NEW, explore our
Technology Services here:
Click Here To Know More!
Have more queries related to
TECHNOLOGY?
Talk To Our Experts