Home
Search results “Agile principles c”
The Difference Between Lean and Agile
 
02:52
Subscribe to our YouTube channel to stay up to date on all of our world-class products and exciting updates: https://goo.gl/YhZF9h Though often considered to be contradictory principles, Lean and Agile are very complementary and when paired together guide teams to better results. Agile Management solutions from CA help teams use both principles in tandem to achieve success.
Views: 55336 CA Technologies
The S.O.L.I.D. Principles of OO and Agile Design - by Uncle Bob Martin
 
01:12:12
READ FIRST: UB doesn't talk about -all- 5 SOLID principals, only a couple. This video is more valuable that just "another SOLID talk". And it's a meetup, not a course. If you want a more in-depth training on it, UB has that on his CleanCoders.com site. Very good vids there...very in depth on coding techniques and he codes a lot there. If anyone wants to challenge whether UB is right or wrong about OO concepts, or bitch because he doesn't cover all 5 principles in this 1 hour casual meetup talk, I'll immediately delete your comment. He knows his shit and I get tired of this kind of bitching which happens a lot. This talk is still very entertaining and informative so sit back, relax, and enjoy! Sometimes it's good for us to learn and understand the past, so that we do not make the same mistakes that have been made over and over again in this profession. https://www.CleanCoders.com - ton of vids by UB, very in depth technically http://www.WeDoTDD.com/interviews/companies/16 https://twitter.com/unclebobmartin http://blog.cleancoder.com https://blog.8thlight.com/uncle-bob/archive.html Source: This presentation was given by Uncle Bob on Feb 4, 2015 at the Arlington Lakes Golf Club in Arlington Heights, IL. Schaumburg Microsoft .NET Technologies Meetup http://bit.ly/1hAO2ln Be sure to change the video to 1080p when watching it Recorded with my IPhone 6+ 1080p (60fps) Side Note: UB talks little about SR and DI toward the end, but it's more a talk around business and more top level tech talk around around decoupling code and history of coding (where the idea of decoupling stemmed from, how objects came into existence and why, and how programming languages were affected by it ended up providing polymorphism... and a lot of other interesting things around the importance of plug-in software....all indirectly related to the topic of SOLID itself as a whole. The S.O.L.I.D. Principles of OO and Agile Design What happens to software? Why does is rot over time? How does an Agile Development team prevent this rot, and prevent good designs from becoming legacy code? How can we be sure our designs are good in the first place? This talk presents the agile S.O.L.I.D. principles for designing object oriented class structures. These principles govern the structure and inter dependencies between classes in large object oriented systems. The principles include: The Open Closed Principle, The Liskov Substitution Principle, and the Dependency Inversion Principle, among others. About "Uncle Bob" Martin: Robert C. Martin has been a software professional since 1970. In the last 35 years, he has worked in various capacities on literally hundreds of software projects. He has authored "landmark" books on Agile Programming, Extreme Programming, UML, Object-Oriented Programming, and C++ Programming. He has published dozens of articles in various trade journals. Today, He is one of the software industry's leading authorities on Agile software development and is a regular speaker at international conferences and trade shows. He is a former editor of the C++ Report and currently writes a monthly Craftsman column for Software Development magazine. Mr. Martin is the founder, CEO, and president of Object Mentor Incorporated. Object Mentor is a sister company to Object Mentor International. Like OMI, Object Mentor is comprised of highly experienced software professionals who provide process improvement consulting, object-oriented software design consulting , training, and development services to major corporations around the world.
Views: 135157 TDD TV
What is Agile?
 
15:22
In this video we will talk about What Agile is and why to use it. We will also see : What is waterfall model Problems with waterfall model Why and when to use Agile 4 Values and 12 principles of Agile Trainer: Navin Reddy Editing Monitors : https://amzn.to/2RfKWgL https://amzn.to/2Q665JW https://amzn.to/2OUP21a. Check out our website: http://www.telusko.com Follow Telusko on Twitter: https://twitter.com/navinreddy20 Follow on Facebook: Telusko : https://www.facebook.com/teluskolearn... Navin Reddy : https://www.facebook.com/navintelusko Follow Navin Reddy on Instagram: https://www.instagram.com/navinreddy20 Subscribe to our other channel: Navin Reddy : https://www.youtube.com/channel/UCxmk... Telusko Hindi : https://www.youtube.com/channel/UCitz... Donation: PayPal Id : navinreddy20 Patreon : navinreddy20 http://www.telusko.com/contactus Subscribe to the channel and learn Programming in easy way. Java Tutorial : https://goo.gl/p10QfB REST Tutorial : https://goo.gl/3mosnz Kotlin Tutorial : https://goo.gl/JedEzX Scala Tutorials for Java Developers : https://goo.gl/8H1aE5 C Tutorial Playlist : https://goo.gl/8v92pu Android Tutorial : https://goo.gl/MzlIUJ XML Tutorial : https://goo.gl/Eo79do Design Patterns in Java : https://goo.gl/Kd2MWE Socket Programming in Java : https://goo.gl/jlMEbg Spring MVC Tutorial : https://goo.gl/9ubbG2 OpenShift Tutorial for Beginners : https://goo.gl/s58BQH Spring Framework with Maven : https://goo.gl/MaEluO Sql Tutorial for Beginners : https://goo.gl/x3PrTg String Handling in Java : https://goo.gl/zUdPwa Array in Java : https://goo.gl/uXTaUy Java Servlet : https://goo.gl/R5nHp8 Exception Handling in Java : https://goo.gl/N4NbAW
Views: 160696 Telusko
Agile Approaches
 
01:21
Agile Approaches There are a number of specific agile approaches, as well as a generic agile style of working. Extreme Programming is a software development methodology, containing mainly programming practices such as Test Driven Development, Pair programming and Continuous Integration, but little management. Lean, which came from the manufacturing environment, is all about efficient processes. The focus is on eliminating waste from the production line and thereby reducing cost. Scrum is a very simple agile process, designed for delivering software in small chunks, taken from a backlog of work to be done. The strength of Scrum is that it is very simple. But this is also a weakness because there is no concept of a 'project' that is managing delivery of a finite piece of work, with a process containing a beginning, middle and end. Scrum, Lean and Extreme Programming are lightweight approaches with minimal structure and guidance. DSDM Atern and Agile Unified process are stronger but are still agile. The strength of DSDM Atern lies in it being designed to deliver projects in an agile way. As you have just seen, there are many different Agile approaches. Most agile methods provide little or no guidance on how to manage a project in an agile way, DSDM Atern is the exception. Extracts from Agile Passport, An accredited eLearning for Agile Project Management. www.spoce.com DSDM®, DSDM logo, Atern® & AgilePM® are registered trademarks of the Dynamic Systems Development Method Ltd. AgilePM and the 'APMG-International Agile Project Management and Swirl Device logo' are trade marks of The APM Group Limited.
Views: 1060 spocePM
Agile approaches in 1 minute
 
01:06
http://pyxis-tech.com - Agile approaches allow to deliver quality software faster and frequently. However, this implies a change in working methods in order to gain real benefits. Adopting Agile methods is first and foremost a human challenge. The adoption of Agile methods affects the organizational culture of the company, from processes to human resources to technology. And you, how would you explain Agile approaches?
Views: 1725 PyxisTechnologies
I Need Agile Methodology
 
04:17
Agile Methodology Parody of iPhone VS Evo Very funny! Check out 'Evil Agile Man'
Views: 179446 Msplqaokws
A Principle Centered Approach to Distributed Agile
 
18:53
The challenges in distributed agile can be seen under three broad categories viz., a) Communication and Coordination, b) Time Zone Differences and c) Issues related to People, Culture and Leadership Style. Successful teams consciously adhere to certain principles and it is their principle-centered approach that helps them face such challenges and deliver the best. Steven Covey wrote: "Principles always have natural consequences attached to them. There are positive consequences when we live in harmony with the principles. There are negative consequences when we ignore them. But because these principles apply to everyone, whether or not they are aware, this limitation is universal. And the more we know of correct principles, the greater is our personal freedom to act wisely." This is true in all situations of life and it includes application of agile methods in geographically distributed teams too. This session is to present the ten principles and elaborate 3-4 principles learned through experience in working with project teams and interactions with industry experts, and applied for more than a decade. These ten principles are above and beyond agile manifesto and agile principles. These are related to areas such as context-specific methodology, tools for productivity improvement, infrastructure for communication and coordination, knowledge management, focus on quality, inclusion, collaborative governance, automation, technical debt management, iteration progression and ensuring early success. Speakers: Raja Bavani, Mindtree
Views: 185 ConfEngine
13 PRINCE2 Agile Principles
 
36:44
Complete Playlist: http://bit.do/prince2-agile-playlist Full PRINCE2 Agile Course: http://bit.do/prince2-agile-course More PRINCE2 Training: http://bit.do/mplaza-home-page Have any questions? Send it to [email protected] PRINCE2 Agile Principles PRINCE2 Agile is the latest standard from AXELOS. It’s a tailored version of PRINCE2, ready to be combined with Agile delivery methods such as Scrum. This combination provides you with both the flexibility of Agile systems, and the governance of PRINCE2. Mature medium to large companies would benefit most from this new standard. This Short video will teach you the Principles of PRINCE2 Agile. New: You can now take the PRINCE2 Agile Practitioner exam when you have PRINCE2 Foundation, PMP, CAPM, or any of the IPMA certificates. The PRINCE2 Practitioner certificate is not a prerequisite for this exam any more.
Views: 9581 Mplaza
Extreme Programming (XP) - Georgia Tech - Software Development Process
 
02:16
Watch on Udacity: https://www.udacity.com/course/viewer#!/c-ud805/l-1771718546/m-439898982 Check out the full Advanced Operating Systems course for free at: https://www.udacity.com/course/ud805 Georgia Tech online Master's program: https://www.udacity.com/georgia-tech
Views: 87463 Udacity
The Death of Agile (Allen Holub)
 
36:18
Keynote from Software Architect 2014 At the very top of the Agile Manifesto is the statement "Individuals and interactions over processes and tools." Nonetheless, the word "agile" has come to mean rigid adherence to both process and the tools that support that process. Moreover, many of these processes are incomplete or ineffective. Scrum is particularly problematic. This talk looks at how "Agile" has moved away from the basic principles of agility, and at what we need to do to fix things (or get off on the right foot if you're just starting the journey). #DeathOfAgile Allen Holub (http://holub.com)
Views: 28247 Allen Holub
Agile Software Development - Georgia Tech - Software Development Process
 
02:03
Watch on Udacity: https://www.udacity.com/course/viewer#!/c-ud805/l-1771718546/m-439898981 Check out the full Advanced Operating Systems course for free at: https://www.udacity.com/course/ud805 Georgia Tech online Master's program: https://www.udacity.com/georgia-tech
Views: 3307 Udacity
SOLID Design Principles Introduction
 
06:14
In this video we will discuss 1. SOLID Acronym and Introduction 2. SOLID design principles 3. Why SOLID SOLID Introduction 1. SOLID principles are the design principles that enable us manage most of the software design problems 2. The term SOLID is an acronym for five design principles intended to make software designs more understandable, flexible and maintainable 3. The principles are a subset of many principles promoted by Robert C. Martin 4. The SOLID acronym was first introduced by Michael Feathers SOLID Acronym S : Single Responsibility Principle (SRP) O : Open closed Principle (OSP) L : Liskov substitution Principle (LSP) I : Interface Segregation Principle (ISP) D : Dependency Inversion Principle (DIP) Single Responsibility Principle 1. Robert C. Martin expresses the principle as, "A class should have only one reason to change” 2.Every module or class should have responsibility over a single part of the functionality provided by the software, and that responsibility should be entirely encapsulated by the class Liskov Substitution Principle 1. Introduced by Barbara Liskov state that “objects in a program should be replaceable with instances of their sub-types without altering the correctness of that program” 2. If a program module is using a Base class, then the reference to the Base class can be replaced with a Derived class without affecting the functionality of the program module 3. We can also state that Derived types must be substitutable for their base types Open/Closed Principle 1. “Software entities should be open for extension, but closed for modification” 2. The design and writing of the code should be done in a way that new functionality should be added with minimum changes in the existing code 3. The design should be done in a way to allow the adding of new functionality as new classes, keeping as much as possible existing code unchanged Interface Segregation Principle 1. “Many client-specific interfaces are better than one general-purpose interface” 2.We should not enforce clients to implement interfaces that they don't use. Instead of creating one big interface we can break down it to smaller interfaces Dependency Inversion Principle 1. One should “depend upon abstractions, [not] concretions" 2. Abstractions should not depend on the details whereas the details should depend on abstractions 3. High-level modules should not depend on low level modules If we don’t follow SOLID Principles we 1. End up with tight or strong coupling of the code with many other modules/applications 2. Tight coupling causes time to implement any new requirement, features or any bug fixes and some times it creates unknown issues 3. End up with a code which is not testable 4. End up with duplication of code 5. End up creating new bugs by fixing another bug 6. End up with many unknown issues in the application development cycle Following SOLID Principles helps us to 1. Achieve reduction in complexity of code 2. Increase readability, extensibility and maintenance 3. Reduce error and implement Reusability 4. Achieve Better testability 5. Reduce tight coupling Solution to develop a successful application depends on Architecture : choosing an architecture is the first step in designing application based on the requirements. Example : MVC, WEBAPI, MVVM..etc Design Principles : Application development process need to follow the design principles Design Patterns : We need to choose correct design patterns to build the software If you are confused on how we can apply these design principles in the application development? Don’t worry as we are going to take a look at them in greater details in the upcoming videos. In the next video we will discuss single responsibility principle in detail with a sample example. Text version of the video http://csharp-video-tutorials.blogspot.com/2017/11/solid-design-principles-introduction.html Slides http://csharp-video-tutorials.blogspot.com/2017/11/solid-design-principles-introduction_20.html SOLID Design Principles Tutorial https://www.youtube.com/watch?v=HLFbeC78YlU&list=PL6n9fhu94yhXjG1w2blMXUzyDrZ_eyOme SOLID Design Principles Text Articles & Slides http://csharp-video-tutorials.blogspot.com/2018/01/solid-design-principles.html All Dot Net and SQL Server Tutorials in English https://www.youtube.com/user/kudvenkat/playlists?view=1&sort=dd All Dot Net and SQL Server Tutorials in Arabic https://www.youtube.com/c/KudvenkatArabic/playlists
Views: 120788 kudvenkat
Robert C. Martin - The Land that Scrum Forgot
 
45:42
Scrum is the most popular of all the Agile methods. Tens of thousands of people have been certified as Scrum Masters. Thousands of projects have use Scrum to get great work done. But there's a problem. Some of those projects fail, and fail badly. The reason they fail is that Scrum forgot something. Scrum forgot to incorporate the technical disciplines that make Agile work. Disciplines like Test Driven Development, Continuous Integration, Simple Design, Refactoring, and Pair Programming. In this talk Uncle Bob will describe those missing disciplines, and tell you how to rescue your Scrum projects from failure by adopting those disciplines. Robert C. Martin has been a software professional since 1970. In the last 35 years, he has worked in various capacities on literally hundreds of software projects. Source: http://www.ndc2011.no/agenda.aspx?cat=1071&id=-1&day=3727
Views: 64601 Tomás Augusto Müller
The Principles of Clean Architecture by Uncle Bob Martin
 
01:13:24
The Principles of Clean Architecture by Uncle Bob Martin (@unclebobmartin) Robert C. Martin, aka, Uncle Bob has been a software professional since 1970 and an international software consultant since 1990. In the last 40 years, he has worked in various capacities on literally hundreds of software projects. In 2001, he initiated the meeting of the group that created Agile Software Development from Extreme Programming techniques and served as the first chairman of the Agile Alliance. He is also a leading member of the Worldwide Software Craftsmanship Movement - Clean Code. He has authored "landmark" books on Agile Programming, Extreme Programming, UML, Object-Oriented Programming, C++ Programming and most recently Clean Code and Clean Coder. He has published dozens of articles in various trade journals.He has written, directed and produced numerous "Code Casts" videos for software professionals.Bob is a regular speaker at international conferences and trade shows.Mr. Martin is the founder, CEO, and president of Uncle Bob Consulting, LLC and Object Mentor Incorporated. Uncle Bob has published dozens of articles in various trade journals, and is a regular speaker at international conferences and trade shows. Mr. Martin has authored and edited many books including: • The Clean Coder • Clean Code • Agile Software Development: Principles, Patterns, and Practices. • Designing Object Oriented C++ Applications using the Booch Method • Agile Principles Patterns and Practices in C# • Patterns Languages of Program Design 3 • More C++ Gems • Extreme Programming in Practice • UML for Java Programmers http://www.meetup.com/Norfolk-Developers-NorDev/events/223533655/
Views: 301383 NorfolkDevelopers
Agile Architecture with SAFe
 
39:53
Presentation - Evolving architecture in a scaled environment, Jan Grape, Crisp.
Views: 2765 crispagileacademy
Agile Principles | PMI-ACP | ProplanX
 
04:06
The 12 Agile Principles are explained in simple words. (Extracted from ProplanX's PMI-ACP Exam Prep Course) Course on SALE! Enjoy a 25% Discount! Pay only $75* for 21 PDUs (contact hours)! Visit us for a FREE trial at http://www.ProplanX.com Check out our other videos at http://youtu.be/ePFxNQJrQGY * For limited time only
Views: 213 ProplanX
Scrum Artifacts
 
16:46
Understand Scrum Artifacts and Definations Facebook Page https://www.facebook.com/agiledigest/ You tube channel https://www.youtube.com/c/agiledigest LinkedIn https://www.linkedin.com/company/agiledigest/ Article Repository : https://agiledigest.com
Views: 416 Agile Digest
Agile User Stories
 
06:52
Learn how to write good user stories for Agile teams. If you'd like a free book on this topic, please see below... I've published a book called "Starting Agile" that is designed to help you start your team's Agile journey out right. You can buy a copy from Amazon, but I'm giving free copies away to my subscribers from YouTube. You can signup for a copy at this link: https://mailchi.mp/326ba47ba2e8/agile-list
Views: 115162 Mark Shead
Scaled Agile Framework (SAFe) Version 4 : Introduction
 
26:50
If we look around we see organizations trying to implement agile based approaches at an enterprise level, when organizations see results of agile based approaches in small teams they start thinking how can we make it work with big teams. Scaled Agile Framework (SAFe) is one of the most known scaling framework, SAFe framework itself is an adaptive framework and the current version 4 provides comprehensive approach for scaling agile.
Agile Principles and Testing
 
15:49
Let me start all over again today I will presenting software testing in agile methodology and as I said that the agile methodology is one of the most important methodology in software testing right now because it is rapid, it is quick, and it is the team base and with this we are actually helping customers as well as quickly building good software and delivering that the best project work.
Views: 111 TechGig
The Three Laws of TDD (Featuring Kotlin)
 
01:06:09
0:00 Introduction into the three laws of Test Driven Development 24:10 A hand-on demo of Test Driven Development using the Kotlin language 43:16 Questions and answers In this talk, Uncle Bob describes the three laws of Test Driven Development, and demonstrates the discipline using the Kotlin language.
Views: 100954 IntelliJ IDEA
iCertify | SPOC | Chap: 1 | Agile and Scrum Overview | Video: 3 | Principles of Agile Manifesto
 
05:06
These videos are part of iCertify’s Scrum Product Owner Certification – SPOC™ online training and certification program: http://icertifytraining.com/project/scrum_product_owner_certification_online_training TO REGISTER FOR FREE WEBINARS, RESOURCES, AND CAREER OPPORTUNITIES http://eepurl.com/bXTCOf Scrum Product Owner Certification – SPOC™ course helps participants attain skills required for a Product owner role including creating project vision, identifying and creating user personas, prioritizing product backlog items, provides practical knowledge of dealing with the Project Stakeholders and take care of the business/value side of things. This course offers a comprehensive training for the SPOC™ examination. Applicants will be awarded the Scrum Product Owner Certified (SPOC™) certificate by SCRUMstudy upon successfully passing the certification exam. About iCertify: iCertify Training, a NY based authorized trainer partner for SCRUMStudy, offers online self-paced training and certification for their Scrum Product Owner Certified (SAMC™) program. SCRUMstudy is the global accreditation body for Scrum and Agile certifications. It has authored the SBOK™ Guide as a comprehensive guide to deliver successful projects using Scrum. Website: www.iCertifytraining.com Email: [email protected]
Views: 399 Icertify Training
Agile Architecture and design with Robert C Martin
 
04:25
The Agile Principles, Patterns, and Practices for creating Robust System Architectures. (SOLID PPP) This course is a deep dive into the well--known SOLID principles of Agile and Object Oriented Design. Students will learn the characteristics of sound Object--Oriented designs and architecture, and patterns and practices that create them. Principles include: The Single Responsibility Principle, The Open Closed Principle, The Liskov Substitution Principle, The Interface Segregation Principle, The Dependency Inversion Principle, and many others. Special attention is paid to Component oriented design, and the principles and patterns of large--scale component architecture. The course is designed for developers with all levels of experience using the Java, C# or C++ programming language.. Beginners will obtain a firm grounding in the principles, patterns and practices, while experienced developers will be able to sharpen and refine their skills by learning how to apply the concepts more effectively. Objectives By the end of this course, you will know how to: Understand and apply the principles of object--oriented design and dependency management Learn professional practices that make projects succeed Learn important design patterns and how and when to apply them Be able to apply Test--Driven Development in the context of Object--Oriented Design Principles and Patterns Coding for Readability and Maintainability The Problems The Objectives Forms of Software Rot Attributes of a Good Design Clean Code Qualities Professional Responsibilities Automated testing, TDD and Refactoring Practices Review Refactoring Dependency Inversion Principle Problems with Procedural Programming Object--Oriented Programming Problem addressed by DIP The Dependency Inversion Principle Dependency Inversion Heuristics When is DIP appropriate⁄inappropriate Example design violating DIP Example designs conforming to DIP Open⁄Closed Principle Problem addressed by OCP The Open⁄Closed Principle When is OCP appropriate⁄inappropriate Several Example designs violating OCP Several example designs conforming to OCP Liskov Substitution Principle Problem addressed by LSP The Liskov Substitution Principle Example designs violating LSP Example designs conforming to LSP Relationship OCP⁄LSP When is "instance of is" not an LSP problem Interface Segregation Problem addressed by ISP The Interface Segregation Principle Example designs violating ISP Example designs conforming to ISP When is ISP appropriate⁄inappropriate Law of Demeter Problem addressed by LoD Example design violating LoD Example designs conforming to LoD When is LoD appropriate⁄inappropriate Pro⁄Con discussion Practices That Support the Principles Simple Design Automated Testing Test--Driven Development Refactoring Teamwork Pair Programming Collective Ownership Quick Design Sessions Continuous Integration Code⁄Design Reviews Summary Clean code Professional Responsibilities SOLID Principles Packaging Principles About the instructor Robert C. Martin has been a software professional since 1970. In the last 35 years, he has worked in various capacities on literally hundreds of software projects. He has authored "landmark" books on Agile Programming, Extreme Programming, UML, Object--Oriented Programming, and C++ Programming. He has published dozens of articles in various trade journals. Today, he is one of the software industrys leading authorities on Agile software development and is a regular speaker at international conferences and trade shows. He is a former editor of the C++ Report and currently writes a monthly Craftsman column for Software Development magazine.
Views: 6025 hjemmesidefilm
SOLID Principles: Understanding and Using
 
01:41:17
2:37 О появлении SOLID 14:19 Симптомы плохого проектирования 23:34 Dependency Inversion 44:37 Open\Closed Principle 1:00:27 ООП объединяет данные с операциями над ними. Плохо ли это? 1:17:27 Liskov Substitution 1:26:24 Single Responsibility 1:33:54 Interface Segregation Слайды: https://www.slideshare.net/korotenkoartem/solid-principles-136793489 Ссылки: 1) Оригинальная статья Р. Мартина Design Principles And Patterns http://www.cvc.uab.es/shared/teach/a21291/temes/object_oriented_design/materials_adicionals/principles_and_patterns.pdf 2) Книга Agile Practices and Principles in C# (пиратить не призываю, но при желании гуглится) https://www.amazon.com.br/Agile-Principles-Patterns-Practices-C/dp/0131857258 3) Иллюстрированные примеры https://medium.com/@trekhleb/solid-principles-around-you-6db2f0e12139 4) Барбаре Лисков - автор абстрактных типов https://medium.com/a-computer-of-ones-own/barbara-liskov-inventor-of-abstract-data-types-9f8908fdcf86
Views: 531 Artem Korotenko
Dependency Inversion Principle Introduction
 
05:06
In this video we will discuss 1. Dependency Inversion Principle Introduction 2. Understand the intention of DIP usage In the first video of SOLID Introduction we have understood that D in SOLID stands for Dependency Inversion Principle which is also known as DIP The Dependency Inversion Principle introduced by Robert C Martin states that High-level modules should not depend on low-level modules. Both should depend on abstractions. AND Abstractions should not depend on details. Details should depend on abstractions. To simplify this we can state that while designing the interaction between a high-level module and a low-level one, the interaction should be thought of as an abstract interaction between them. Usage Intention : Before understanding the intention of usage, let’s try to understand a traditional application architecture implementation. During the process of the application design, lower-level components are designed to be consumed by higher-level components which enable increasingly complex systems to be built. In this Process of Composition, higher-level components depend directly upon lower-level components to achieve some task. Text version of the video http://csharp-video-tutorials.blogspot.com/2018/01/dependency-inversion-principle.html Slides http://csharp-video-tutorials.blogspot.com/2018/01/dependency-inversion-principle_23.html SOLID Design Principles Tutorial https://www.youtube.com/watch?v=HLFbeC78YlU&list=PL6n9fhu94yhXjG1w2blMXUzyDrZ_eyOme SOLID Design Principles Text Articles & Slides http://csharp-video-tutorials.blogspot.com/2018/01/solid-design-principles.html All Dot Net and SQL Server Tutorials in English https://www.youtube.com/user/kudvenkat/playlists?view=1&sort=dd All Dot Net and SQL Server Tutorials in Arabic https://www.youtube.com/c/KudvenkatArabic/playlists
Views: 46493 kudvenkat
Agile Summit Greece - Opening Keynote by Robert C.Martin (Uncle Bob)
 
01:03:02
Agile Summit Greece - Opening Keynote by Robert C.Martin (Uncle Bob) - Programmer's OAuth
Views: 2763 Agile Greece Summit
Introducing PRINCE2 Agile™
 
02:17
Find out more about PRINCE2 Agile from AXELOS at http://www.axelos.com/PRINCE2Agile. PRINCE2 Agile is a new project management solution from AXELOS which combines the governance and direction of PRINCE2 with the flexibility of agile concepts. Watch our short video introducing the new best practice solution and find out more about how it can help you or your organization. PRINCE2 Agile has been built collaboratively with industry experts from both the PRINCE2 and Agile domain to bring together the best of both worlds. PRINCE2 Agile shows you how to integrate agile frameworks, concepts and behaviours so you can tailor PRINCE2 to any agile concept. PRINCE2 Agile covers frameworks including Scrum, Kanban, Lean Startup and Cynefin and also builds on the principles of PRINCE2 with five key behaviours. PRINCE2 Agile represents the next phase in project management best practice.
Interview with Arie van Bennekum (1/2) | Author of Agile Manifesto
 
06:52
"An agilist that says "I know it all" is not an agilist." - Arie van Bennekum, author of the Agile Manifesto and Agile Thoughtleader at Wemanity, gives an overview of Agility's development through the years, of its ecosystem and mindset. _________________________________________________________________ Check out more at https://www.wemanity.com/ Follow Wemanity on Twitter: https://twitter.com/wemanity Follow Wemanity on Linkedin: https://www.linkedin.com/company/wemanity Like Wemanity on Facebook: https://www.facebook.com/Wemanity/ Subscribe to our channel: youtube.com/c/Wemanity
Views: 161 Wemanity
Software Design Patterns and Principles (quick overview)
 
11:24
Ex-Google Tech Lead the TheTECHLEAD teaches the tech of technical software & systems design patterns and principles on how to avoid over-engineering your project into garbage. This is a serious video. Because it is important. 👇 SUBSCRIBE TO MY YOUTUBE CHANNEL 👇 http://youtube.com/techlead?sub_confirmation=1 http://instagram.com/patrickshyu/ http://twitter.com/patrickshyu/ ‣ TechLead: Season 1 Complete HD available for purchase. https://www.youtube.com/watch?v=_wbKUHBPkh4 Here's my tech setup (★★★★★): My Desk Lamp: https://amzn.to/2xDguWy My Mouse: https://amzn.to/2DrGuJD My Keyboard: https://amzn.to/2xEOaTy My Camera: https://amzn.to/2W5dm0k My Macbook: https://amzn.to/2OuKJFj My Headphones: https://amzn.to/2phsWqj My Multitool: https://amzn.to/2xwf9zJ My Monitor: https://amzn.to/2RdlDzD Listen to audiobooks to save time on your drive, here's a free book coupon: http://audibletrial.com/techlead Video explanations of popular interview questions: http://algoexpert.io/techlead (use code "techlead" for a discount)
Views: 126005 TechLead
What is Agile Development (Part 1): What is Agile Development?
 
04:28
“What is agile development?” It’s always been surprisingly hard to get a simple answer to this question. There are esoteric and convoluted descriptions of agile all over the web, complete with concentric circles meant to sum it all up into a simple concept, and yet that simple answer eludes us. To be fair, agile development methodology isn’t a simple thing. Sourceseek is a free service that handpicks software developers for your exact project needs. Get started here: https://www.sourceseek.com/get-started/ We’ll start with wikipedia’s agile methodology definition: From Wikipedia: Agile software development is a group of software development methods based on iterative and incremental development, where requirements and solutions evolve through collaboration between self-organizing, cross-functional teams. It promotes adaptive planning, evolutionary development and delivery, a time-boxed iterative approach, and encourages rapid and flexible response to change. It is a conceptual framework that promotes foreseen interactions throughout the development cycle. The first sentence starts by saying that agile development is a software development methodology. A software development methodology is a set of practices and procedures that help a team get organized and build software. It’s not the software itself, it’s the rule-book for organizing the team. That first sentence goes on to describe an iterative and incremental development approach. This is a key concept, and if you only take away one thing about agile this is the one to take away. In agile, we do iterations (circles) where we plan, execute, then review the results so that we can refine the plan and start all over again. We love change, and we want as many iterations and feedback loops as possible during the project. At the end of that first sentence, wikipedia describes collaboration: This really just means that we emphasize partnership and collaboration, with each member of the team serving a specific role but everyone expected to be flexible and to work together. In agile, we love teamwork. The second sentence brings in the concepts of adaptive planning, evolutionary development and delivery, a time-boxed iterative approach, and rapid and flexible response to change. In this part of the definition, we see how it all comes together! I interpret this sentence like this: ● We are adaptive. We don’t plan it all at the beginning and then stop planning. We do iterations and we are adjusting the plan all the time. This is why agile is so good for product development, we change and improve as we learn. ● We love evolutionary development. This is essentially the same thing, we learn as we go and we adjust, refine, improve... ● Time-boxing. This basically means that we manage our project using set blocks of time, like days or weeks, and we try to get as much done in those time-boxes as possible. This is the reverse of managing features. We consider what features we can build next week rather than looking at a list of features and asking how long it will take to build them. ● Rapid and flexible response to change: this is critical, and along with ‘iterations’ is the core answer to the question ‘what is agile development?’. We move fast, we are flexible, and we are truly ‘agile’! This is our mantra - fast and flexible - say it again and again!! What is agile development? ● Agile is a way of managing software projects. ● Agile is iterative, and goes in repeated cycles instead of in a long list of steps.. ● Agile is super collaborative and team-oriented. ● Agile is adaptive, constantly changing and refining plans, and moves fast! In almost every project, the client has a harder time expressing what they want at the beginning, and it gets gradually clearer towards the end. The can be a frustrating experience as mid-project changes are pretty disruptive. Let’s try it in agile. 1) Client hires developers by the hour, day, or week. 2) Client describes what they want to the developers 3) Developers start making designs and programming the theme based on what they client thinks they want. 4) Developers show their progress to the client constantly, even every day, to make sure they are on track. 5) The client makes frequent changes and tweaks, always refining the plan and improving the result. The developer also has input and suggestions. 6) The team keeps going until the project is done.. It all sounds very good, and it can be, but the reality is that the agile development methodology requires a solid team of smart people who know what they are doing or it can be a train wreck. It also requires that the entire team (client included) be committed to an honest, forthcoming approach that emphasizes success for the client. SourceSeek is free for clients; we find you the best teams and the perfect match. It's that simple. SUBSCRIBE NOW FOR MORE OUTSOURCING VIDEO TIPS AND NEWS! https://www.youtube.com/subscription_...
Views: 277690 SourceSeek
Open Closed Principle
 
10:11
In this video we will learn 1. Open Closed Principle 2. Implementation guidelines of Open closed Principle 3. And will implement this Principle with a simple example In the first video of SOLID Introduction we have understood that O in the SOLID is acronym for “Open/Closed Principle” also known as OCP Definition: In object-oriented programming, the open/closed principle states that "software entities such as classes, modules, functions, etc. should be open for extension, but closed for modification" 1. Which means, any new functionality should be implemented by adding new classes, attributes and methods, instead of changing the current ones or existing ones. 2. Bertrand Meyer is generally credited for having originated the term open/closed principle and This Principle is considered by Bob Martin as “the most important principle of object-oriented design”. Implementation guidelines 1. The simplest way to apply OCP is to implement the new functionality on new derived (sub) classes that inherit the original class implementation. 2. Another way is to allow client to access the original class with an abstract interface, 3. So, at any given point of time when there is a requirement change instead of touching the existing functionality it’s always suggested to create new classes and leave the original implementation untouched. Pit falls of Not following OCP What if I do not follow Open closed principle during a requirement enhancement in the development process. In that case, we end up with the following disadvantages 1. If a class or a function always allows the addition of new logic, as a developer we end up testing the entire functionality along with the requirement. 2. Also, as a developer we need to ensure to communicate the scope of the changes to the Quality Assurance team in advance so that they can gear up for enhanced regression testing along with the feature testing. 3. Step 2 above is a costly process to adapt for any organization 4. Not following the Open Closed Principle breaks the SRP since the class or function might end up doing multiple tasks. 5. Also, if the changes are implemented on the same class, Maintenance of the class becomes difficult since the code of the class increases by thousands of unorganized lines. Hope the above counter facts helps in understanding on why we need to follow the open closed principle. You can find the code used in the demo at the following link http://csharp-video-tutorials.blogspot.com/2018/01/open-closed-principle.html Also, we strongly recommend you to refer to our design pattern tutorial for more details on creational design patterns I believe this session has given you a good idea on how we can implement Open closed principle. In the next session we will focus on Liskov substitution principle. Till then, thank you and have a great day Text version of the video http://csharp-video-tutorials.blogspot.com/2018/01/open-closed-principle.html Slides http://csharp-video-tutorials.blogspot.com/2018/01/open-closed-principle-slides.html SOLID Design Principles Tutorial https://www.youtube.com/watch?v=HLFbeC78YlU&list=PL6n9fhu94yhXjG1w2blMXUzyDrZ_eyOme SOLID Design Principles Text Articles & Slides http://csharp-video-tutorials.blogspot.com/2018/01/solid-design-principles.html All Dot Net and SQL Server Tutorials in English https://www.youtube.com/user/kudvenkat/playlists?view=1&sort=dd All Dot Net and SQL Server Tutorials in Arabic https://www.youtube.com/c/KudvenkatArabic/playlists
Views: 43426 kudvenkat
SOLID Design Patterns
 
57:18
In this episode, Robert is joined by Phil Japikse for a chat about design patterns. Software design patterns have been around long before the MVC Framework gained momentum. Phil starts with a review of Robert C. Martin's (Uncle Bob) SOLID macronym. After building the proper foundation,he reviews several design patterns, their C# implementation and when and how they should be used in modern software development. Get the code samples here: http://www.skimedic.com/samples/Japikse_SolidPatterns.zip
Views: 113734 Microsoft Visual Studio
Agile Project Management: Agile Principles - Part 3 of 5
 
02:37
Some agile principles I find handy when working with a distributed team. This content is from the session I gave at Content World 2009 entitled "Put Users First with Agile Project Management". The audio is from that session, the visuals are from the presentation I put together with Prezi.
Views: 2809 Amanda Holtstrom
IMO Episode 10 - Interview With Uncle Bob (Robert) C. Martin
 
01:12:06
In this IMO (In My Opinion) video, software developer Steve Bishop will be talking to industry icon Robert C. Martin, better known as Uncle Bob. Uncle Bob is one of the original authors of the Agile Manifesto, and the Software Craftsmanship Manifesto. Uncle Bob has also written several books including "Agile Software Development, Principles, Patterns, and Practices", "Agile Principles, Patterns, and Practices in C#", "Clean Code: A Handbook of Agile Software Craftsmanship", "The Clean Coder: A Code of Conduct for Professional Programmers", and coming out next year "Clean Architecture". Robert Martin is also widely known as the creator of the SOLID principles, a advocate of Test Driven Development, and the Craftsmanship Movement. You can ask your questions in the live chat and if we have time we'll ask them of Uncle Bob. Gartman Technical Services: http://http://gartmantechnical.com/ Programming Made EZ: http://ProgrammingMadeEZ.com Clean Coders Website: https://cleancoders.com/ Uncle Bob's Blog (Clean Coder Blog): http://blog.cleancoder.com/ Clean Architecture (Amazon): https://www.amazon.com/Clean-Architecture-Robert-C-Martin/dp/0134494164/ref=sr_1_2?ie=UTF8&qid=1479503189&sr=8-2
Views: 4664 Programming
"Uncle" Bob Martin - "The Future of Programming"
 
01:18:21
How did our industry start, what paths did it take to get to where we are, and where is it going. What big problems did programmers encounter in the past? How were they solved? And how do those solutions impact our future? What mistakes have we made as a profession; and how are we going to correct them. In this talk, Uncle Bob describes the history of software, from it’s beginnings in 1948 up through the current day; and then beyond. By looking at our past trajectory, we try to plot out where our profession is headed, and what challenges we’ll face along the way. Robert C. Martin (Uncle Bob) has been a programmer since 1970. He is the Master Craftsman at 8th Light inc, an acclaimed speaker at conferences worldwide, and the author of many books including: The Clean Coder, Clean Code, Agile Software Development: Principles, Patterns, and Practices, and UML for Java Programmers.
Views: 750533 Expert Talks Mobile
S.O.L.I.D. Principles of Object-Oriented Design - A Tutorial on Object-Oriented Design
 
10:04
Learn more advanced front-end and full-stack development at: https://www.fullstackacademy.com In this tutorial, we give an overview of the S.O.L.I.D. Principles of Object-Oriented Design, a concept introduced by Robert C. Martin in 1995. These rules are designed to help a programmer develop software that is easy to maintain and extend. Watch this video to learn: - Three major signs of bad code - How coding with S.O.L.I.D. in mind can help you avoid these pitfalls - How S.O.L.I.D. can apply when coding in JavaScript
Views: 33647 Grace Hopper Academy
2017 BSA375 Agile#3
 
01:55
Download BSA/375 Week 1 Tutorials NOW @ http://UOP-Tutorials.info/bsa375.html BSA/375 Week 1 Everything listed for Week 1 is Included in purchase! A+ Work!! Individual: Agile Principles Option #1 included: 10 Slides with Speaker Notes, Handouts, & Plagiarism Check Option #2 included: 10 Slides with Speaker Notes, Handouts, & Plagiarism Check Option #3 included: 12 Slides with Speaker Notes, Handouts, & Plagirarism Check Resource: Principles behind the Agile Manifesto Create an 8- to 12-slide Microsoft PowerPoint presentation that summarizes the Agile Manifesto. Include speaker notes. Present at least two points of praise (i.e. Agile principles you believe are positive/productive). Present at least two points of criticism (i.e. Agile principles you believe are negative/counterproductive). Contrast the Agile methodology with the typical software development practices found in the traditional Waterfall methodology. Investigate and describe recent professional or academic research regarding the effectiveness of the Agile methodology. Incorporate additional research or academic information to support your presentation and include citations. Format your PowerPoint speaker notes according to APA guidelines and include references. Create a Handout file. Submit the Handout file to the Center for Writing Excellence Plagiarism checker and post the results with your assignment. I realize that it may take several hours to obtain the results so you can submit this file a day after you submit your assignment. Submit your presentation as a Microsoft PowerPoint file and the results from the Plagiarism checkerto the Assignment Files tab. Supporting Activity: Development Methodologies Write a short answer to the following: Review the agile and waterfall methodologies in Systems Development Life Cycle (SDLC) in your readings and in the podcast for this week. Explain the main differences between the agile and waterfall methodologies. What types of software application development projects would be better suited for each methodology and why? Supporting Activity: Systems Analyst Write a short answer to the following question: Why is the role of the systems analyst so critical in a systems development project? What skills and knowledge are required to be effective? Explain the role that systems analysts play in determining feasibility of a systems development project.
Views: 5 Sharon Reynolds
Agile Manifesto - Values
 
04:37
Agile Manifesto PMP® / PRINCE2 ® /Agile and Scrum Certification Training:  www.pmexpertinc.com www.pmexpertgroup.com For more updates on courses and tips follow us on:- Facebook :https://www.facebook.com/pmexpertinc/ http://www.pankajpmp.com/ You Tube Channel - https://www.youtube.com/c/PankajSharmaPMP
Views: 3693 Pankaj Sharma
Robert C. Martin (Uncle Bob) - Demanding Professionalism in Software Development
 
45:04
Provided by Elapse Technologies - http://www.elapsetech.com Robert C. Martin explains in his own unique style why professionalism is so important for software development teams and their managers. This event has been recorded live at an event co-hosted by Agile Quebec City and Elapse Technologies in Septembre 2012. --- Bob Martin présente dans un style bien à lui pourquoi le professionnalisme au sein des équipes de développement logiciel est un enjeu incontournable pour les gestionnaires et les équipiers. Cette conférence a été enregistrée lors d'un évènement organisé par Agile Québec et Elapse Technologies en septembre 2012.
Views: 68386 ElapseTechnologies
Clean Code Book Review |  A Handbook of Agile Software Craftsmanship | Ask a Dev
 
10:14
Clean Code Book Review | A Handbook of Agile Software Craftsmanship | Ask a Dev » Clean Code https://amzn.to/2JIjOrz ► MY COURSES My Courses with huge discounts: » 100 Algorithms Challenge: How to Ace Your Next JavaScript Interview https://www.udemy.com/100-algorithms-challenge/?couponCode=CODINGGOD » JavaScript 360: part 1 https://www.udemy.com/javascript-360/?couponCode=CODINGGOD » Angular 360: Part 1 Personal Portfolio https://www.udemy.com/learn-angular-by-projects-part-1/?couponCode=CODINGGOD » Angular 360: Part 2 Top 100 Cryptos https://www.udemy.com/angular-2-360-part-2/?couponCode=CODINGGOD ► MY MERCH My Coding Merch - Shirts, Mugs etc. » "Bro, do you even code?" https://teespring.com/stores/coding-tutorials-360 ► BOOK RECOMMENDATIONS » The Complete Software Developer's Career Guide: http://amzn.to/2BNciX2 » The Total Money Makeover https://amzn.to/2sBHIKs » Clean Code https://amzn.to/2JIjOrz ► AFFILIATE LINKS FOR PRODUCTS I LOVE: » Check out items I love on Amazon https://www.amazon.com/shop/codingtutorials360 » Humble Bundle (Low price games, books, courses etc.) https://www.humblebundle.com/?partner=coding360 » Robinhood - Trade Stocks App (Sign up and get 1 share of stock valued between 5 and 200 dollars) http://share.robinhood.com/dylani10 » Acorns - Easy Investment Portfolio (Sign up with my link and get $5 when you deposit) https://acorns.com/invite/52psvn ► DONATE & SUPPORT » Paypal https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=GYQ3PXFZM5554 ► MENTORING » Tutoring, Mentoring and Course Walkthroughs available: http://www.codingtutorials360.com/tutor.html ► SOCIAL MEDIA » Patreon https://www.patreon.com/CodingTutorials360 » Code, Tech and Caffeine Facebook Group https://www.facebook.com/groups/190277791450732/ » Twitter https://www.twitter.com/PizzaPokerGuy » Website http://www.codingtutorials360.com » Instagram https://www.instagram.com/dylansphotos87
Views: 4344 Dylan Israel
How It Works: Design Thinking
 
05:52
Trying to solve a problem or find better ways of getting work done? Get familiar with IBM Design Thinking and Agile. For more information on IBM Design Thinking, please visit: http://www.ibm.com/design IBMers -- learn more about Security Intelligence on Think Academy (internal site): https://ibm.biz/IBMThinkAcademy
Views: 649364 IBM Think Academy
Single Responsibility Principle
 
10:24
In this video we will discuss 1. What is Single Responsibility 2. Single Responsibility Example In our previous video we discussed S in the SOLID is acronym for Single Responsibility Principle (SRP) As per the single responsibility principle 1. A class should have only one reason to change 2. Which means, every module or class should have responsibility over a single part of the functionality provided by the software, and that responsibility should be entirely encapsulated by the class. Encapsulation is one of the fundamentals of OOP. At this moment, understanding more about encapsulation is out of scope of this session. However, we strongly recommend you to refer to the C# tutorial playlist for more details on Object oriented principles. Now you might be wondering what do we achieve with the Single Responsibility Principle or rather with the SOLID Design Principles. Let's first understand the motivation behind the usage of SOLID Principles In any enterprise software application development when we design and develop software systems, we need to account the below factors during the development cycle. Maintainability : Maintainable systems are very important to the organisations. Testability : Test driven development (TDD) is required when we design and develop large scale systems Flexibility and Extensibility : Flexibility and extensibility is a very much desirable factor of enterprise applications.Hence we should design the application to make it flexible so that it can be adapt to work in different ways and extensible so that we can add new features easily. Parallel Development : It is one of the key features in the application development as it is not practical to have the entire development team working simultaneously on the same feature or component. Loose Coupling : We can address many of the requirements listed above by ensuring that our design results in an application that loosely couples many parts that makes up the application. SOLID Principles and Design Patterns plays a key role in achieving all of the above points. In Single Responsibility Principle 1. Each class and module should focus on a single task at a time 2. Everything in the class should be related to that single purpose 3. There can be many members in the class as long as they related to the single responsibility 4. With SRP, classes become smaller and cleaner 5. Code is less fragile Hence we can say that Single Responsibility Principle achieves the motivation points that we have just discussed. Below code demonstrates how we can achieve Single Responsibility Principle Code before Single Responsibility Segregation using System; using System.Collections.Generic; using System.Linq; using System.Text; using System.Threading.Tasks; namespace SRPDemo { interface IUser { bool Login(string username, string password); bool Register(string username, string password, string email); void LogError(string error); bool SendEmail(string emailContent); } } Code after Single Responsibility Segregation using System; using System.Collections.Generic; using System.Linq; using System.Text; using System.Threading.Tasks; namespace SRPDemo { interface IUser { bool Login(string username, string password); bool Register(string username, string password, string email); } interface ILogger { void LogError(string error); } interface IEmail { bool SendEmail(string emailContent); } } Now that we have segregated the single responsibility principle in these multiple interfaces the next step is to implement these interfaces with object creation mechanisms. GOF has defined many design patterns on object creations based on the requirements. Hence we strongly recommend you to refer to our design pattern tutorial for more details on creational design patterns. I believe this session has given you a good idea on how we can implement Single responsibility principle. In the next video we will discuss Interface Segregation Principle. Text version of the video http://csharp-video-tutorials.blogspot.com/2017/11/single-responsibility-principle.html Slides http://csharp-video-tutorials.blogspot.com/2017/11/single-responsibility-principle-slides.html SOLID Design Principles Tutorial https://www.youtube.com/watch?v=HLFbeC78YlU&list=PL6n9fhu94yhXjG1w2blMXUzyDrZ_eyOme SOLID Design Principles Text Articles & Slides http://csharp-video-tutorials.blogspot.com/2018/01/solid-design-principles.html All Dot Net and SQL Server Tutorials in English https://www.youtube.com/user/kudvenkat/playlists?view=1&sort=dd All Dot Net and SQL Server Tutorials in Arabic https://www.youtube.com/c/KudvenkatArabic/playlists
Views: 63164 kudvenkat