Droisys is an internationally recognized leader helping mankind advance and businesses grow through cost effective technology. Our focus is on creating secure applications to simplify people’s lives so they become raving fans
Droisys is an internationally recognized leader helping mankind advance and businesses grow through cost effective technology. Our focus is on creating secure applications to simplify people’s lives so they become raving fans.
DevOps is a culture that aims to harmonize people, processes, and technologies to enhance the ability of organizations to reliably release software faster and more frequently. Visual Studio Team Services is a cloud service that supports the DevOps process through features like Git source control, build management, release management, and testing. An effective continuous integration and continuous deployment pipeline uses automated builds to detect problems early and reliably releases software through environments like development, staging, and production.
Talk about Continuous Deployment at CartoDB, updated with more tooling and Ruby and JS specific concerns. Many thanks to Software Craftsmanship Madrid for inviting us!
A roadmap for securing containers and container orchestration systems like Kubernetes from development and image creation through to deployment and running in a production environment.
The Science of Compliance - Early Code to Secure your Node (11/6/19)judy (fink) johnson
We all know that the earlier in the software development process you start your development and test, the more money you save in the long run.
In this session, we will discuss methodologies for inserting/continuing compliance checking at various places in the development process - from the Operating System to the code, test, and development systems to various places in the CI process including code, unit test, integration test, and even continuous compliance checking while your code is running.
Compliance Superpowers - Ben Blair, ChicagoAWS Chicago
This document outlines best practices for AWS compliance presented by Ben Blair from Catalytic. It discusses establishing proper change management processes, organizing AWS accounts, implementing access controls, enabling comprehensive monitoring and logging, ensuring encryption, maintaining availability and durability, and addressing vulnerabilities and malware. Specific recommendations include using infrastructure as code, code reviews, testing environments, and continuous integration/deployment for changes. The talk also provides resources for CIS AWS benchmarks, CloudFormation templates, and concludes that compliance and agility are not mutually exclusive when following basic best practices and prioritizing change management.
Prise en compte de la dimension temporelle dans la modélisation des systèmes ...Pierre-Marie Delpech
La cartographie du programme Copernic que nous avons lancé à la DGFiP a développé une dimension originale, particulièrement novatrice pour l'état de l'art des outils d'urbanisation et cartographie des systèmes d'information, qui faisait cependant particulièrement défaut à la gouvernance des programme de transformation de SI: la dimension temporelle.
Il a s'agit d'introduire dans le méta-modèle classique d'urbanisation le concept de "palier", ainsi que les méta-relations nécessaires aux niveaux fonctionnel et applicatif, afin de permettre de spécifier l'ensemble des composants mis simultanément en production pour atteindre un nouvel état stable du SI le long de sa trajectoire de transformation (vers une architecture orientée service en l'occurrence).
Grace à quoi, cette trajectoire est aujourd'hui prise en compte dans la cartographie du SI. Alors que cette dernière se cantonnait auparavant à donner une vision stratégique, mais statique (carte = snapshop) des architectures existante et cible, elle donne désormais une vision dynamique du SI et offreau pilotage du programme de meilleures analyse d'impacts en cas d'aléas (retard de palier, par exemple).
This document reports on Remote Procedure Call (RPC) and distributed systems. It provides background on RPC, describing it as a technique that allows a program to execute a subroutine in another address space, such as on another computer, without explicitly coding message passing details. It then gives timelines and information flows for how RPC works. The document also discusses socket programming as an implementation of RPC, showing code examples of a socket server and client that demonstrate how sockets allow message passing between processes similarly to RPC.
Droisys is an internationally recognized leader helping mankind advance and businesses grow through cost effective technology. Our focus is on creating secure applications to simplify people’s lives so they become raving fans.
DevOps is a culture that aims to harmonize people, processes, and technologies to enhance the ability of organizations to reliably release software faster and more frequently. Visual Studio Team Services is a cloud service that supports the DevOps process through features like Git source control, build management, release management, and testing. An effective continuous integration and continuous deployment pipeline uses automated builds to detect problems early and reliably releases software through environments like development, staging, and production.
Talk about Continuous Deployment at CartoDB, updated with more tooling and Ruby and JS specific concerns. Many thanks to Software Craftsmanship Madrid for inviting us!
A roadmap for securing containers and container orchestration systems like Kubernetes from development and image creation through to deployment and running in a production environment.
The Science of Compliance - Early Code to Secure your Node (11/6/19)judy (fink) johnson
We all know that the earlier in the software development process you start your development and test, the more money you save in the long run.
In this session, we will discuss methodologies for inserting/continuing compliance checking at various places in the development process - from the Operating System to the code, test, and development systems to various places in the CI process including code, unit test, integration test, and even continuous compliance checking while your code is running.
Compliance Superpowers - Ben Blair, ChicagoAWS Chicago
This document outlines best practices for AWS compliance presented by Ben Blair from Catalytic. It discusses establishing proper change management processes, organizing AWS accounts, implementing access controls, enabling comprehensive monitoring and logging, ensuring encryption, maintaining availability and durability, and addressing vulnerabilities and malware. Specific recommendations include using infrastructure as code, code reviews, testing environments, and continuous integration/deployment for changes. The talk also provides resources for CIS AWS benchmarks, CloudFormation templates, and concludes that compliance and agility are not mutually exclusive when following basic best practices and prioritizing change management.
Prise en compte de la dimension temporelle dans la modélisation des systèmes ...Pierre-Marie Delpech
La cartographie du programme Copernic que nous avons lancé à la DGFiP a développé une dimension originale, particulièrement novatrice pour l'état de l'art des outils d'urbanisation et cartographie des systèmes d'information, qui faisait cependant particulièrement défaut à la gouvernance des programme de transformation de SI: la dimension temporelle.
Il a s'agit d'introduire dans le méta-modèle classique d'urbanisation le concept de "palier", ainsi que les méta-relations nécessaires aux niveaux fonctionnel et applicatif, afin de permettre de spécifier l'ensemble des composants mis simultanément en production pour atteindre un nouvel état stable du SI le long de sa trajectoire de transformation (vers une architecture orientée service en l'occurrence).
Grace à quoi, cette trajectoire est aujourd'hui prise en compte dans la cartographie du SI. Alors que cette dernière se cantonnait auparavant à donner une vision stratégique, mais statique (carte = snapshop) des architectures existante et cible, elle donne désormais une vision dynamique du SI et offreau pilotage du programme de meilleures analyse d'impacts en cas d'aléas (retard de palier, par exemple).
This document reports on Remote Procedure Call (RPC) and distributed systems. It provides background on RPC, describing it as a technique that allows a program to execute a subroutine in another address space, such as on another computer, without explicitly coding message passing details. It then gives timelines and information flows for how RPC works. The document also discusses socket programming as an implementation of RPC, showing code examples of a socket server and client that demonstrate how sockets allow message passing between processes similarly to RPC.
Mobile, social, big data, and cloud computing represent a new style of IT that can transform industries. An IT roadmap using this new style of IT can enable businesses by providing flexible and scalable solutions. Hewlett-Packard's strategic solution architect Pierre-Marie Delpech discusses how the new technologies can help businesses transform using an IT roadmap.
The document provides an overview of enterprise architecture (EA), including what it is, why it's useful, and how to approach EA using common frameworks. It discusses EA as both a process and product to guide organizational change. The TOGAF framework and Archimate modeling language are presented as standard tools, with Archi as a free modeling tool. An example EA project is described to identify duplicative business processes using these EA methods and tools.
The document describes a .NET template solution architecture that is flexible, maintainable, sustainable, understandable, testable, and allows for easy addition of new features. It recommends layering the solution into projects for the frontend, services, data access, entities/DTOs, repositories, view models, inversion of control, and mapping entities to view models. Each layer has specific responsibilities and dependencies designed to separate concerns and enable loose coupling between layers.
The document discusses the Visual Studio Scrum v1.0 template which maps the Scrum framework to work item types, queries, and reports in Visual Studio Team Foundation Server. It describes Scrum concepts like product backlog items, sprints, and impediments that are represented by work item types in the template. The template supports Scrum activities through standard queries and reports for tracking progress. A demonstration of the template configuration and customization is also outlined.
This document discusses job training methods and processes at an IT firm. It begins by introducing the importance of training for employees and businesses. It then provides background on the growth of the IT sector in India and the increased need for training and skills development. The rest of the document discusses various training models, domains, methods, and essential aspects of training in the IT industry. It also includes surveys on effective training delivery methods and the variation of trainer salaries with experience in the IT sector.
This document discusses using Scrum and Visual Studio 2010 for agile software development. It provides an overview of how to plan a Scrum project using Visual Studio templates, including organizing product backlogs, sprints, daily scrums, and sprint reviews. It also lists common agile practices like test-driven development, continuous integration, and refactoring that can be applied.
This document provides reviews of 3 research papers on distributed systems. The reviews were created by following a structured format including the paper title, authors, main idea, results, impact, evidence, prior work, and ideas for future work. For the first paper, the summary discusses analyzing the cost and resource optimization of running real-life applications on an open source cloud. The second paper proposes a software testing framework called IVRIDIO to provide test-first performance as a cloud service. The third paper presents a formal approach to developing fault tolerant distributed systems using refinement techniques.
This document discusses applying agile principles and practices to TOGAF architecture projects. It outlines the goals of mapping agile approaches to the TOGAF Architecture Development Method (ADM). Key aspects covered include mapping agile values, principles, practices and roles to the TOGAF ADM phases. Specific techniques like story cards, planning boards and retrospectives are described. The workshop aims to provide guidance on an agile enterprise architecture approach and get feedback to inform future standards.
The document discusses how service-oriented architecture (SOA) can help enterprise architecture (EA) practices. It proposes a service-oriented enterprise architecture (SOEA) model that represents architectures in a modular, layered manner using loosely coupled services. Applying SOA principles can help address common EA challenges by simplifying modeling, increasing stakeholder participation, and enabling flexible architecture maintenance and governance.
Team Foundation Server Process Templates For Effective Project ManagementAaron Bjork
An introduction to process templates, an overview of the Microsoft Process Template, and new process template features shipping in Team Foundation Server 2010.
This document discusses deadlock detection in distributed systems. It begins with defining deadlock and providing an example of a deadlock situation. It then explains that deadlock detection is more challenging in distributed systems due to factors like message loss and lack of shared memory. The document outlines three strategies for deadlock handling - detection and recovery, prevention, and avoidance. It proposes two approaches for deadlock detection in distributed systems: 1) using a central coordinator to merge wait-for graphs or 2) having all machines broadcast their wait-for graphs to detect deadlocks in a distributed way. Both approaches have drawbacks like single point of failure or overhead.
Agile project management with visual studio tfs 2013 - My presentation at Reg...Om Prakash Bang
This presentation is to give overview of Agile Planning for continuous delivery for value, Agile Project Management dashboard, Sprint Planning, Burn Down Charts. Distributed project team collaborate using Team Room, Task board update for all work and used during Daily Stand Up meeting.
Out of box (OOB) template for CMMI, Agile and Scrum. The main distinctions between the three default process templates are in the work item types they provide for planning and tracking work. Visual Studio Scrum is the most light-weight and MSF for Capability Maturity Model Integration (CMMI) provides the most support for formal processes and change management.
1. Microsoft Visual Studio Scrum 2013 - Choose Visual Studio Scrum if your team manages bugs along with product backlog items during sprint planning.
2. MSF for Agile Software Development 2013 - Choose Agile if your organization triages bugs separately from the product backlog and resolves work items before closing them. Also, choose Agile if your team allocates time for bugs with each sprint.
3. MSF for CMMI Process Improvement 2013 - Choose CMMI if your organization triages bugs separately from the product backlog, resolves work items before closing them, and tracks changes to requirements formally. The CMMI template is designed to support formal change management processes.
EA Intensive Course "Building Enterprise Architecture" by mr.danairatSoftware Park Thailand
This document outlines the agenda for a two-day course on building enterprise architecture. Day one covers introductions, current architecture challenges, the need for enterprise architecture, definitions of enterprise architecture, reference architecture frameworks, and group workshops. Day two covers maturity models, technology platforms, the TOGAF standard, cloud computing roadmaps, governance, and building a target architecture.
The Open Group Architecture Framework (TOGAF) is an enterprise architecture framework developed and maintained by The Open Group. TOGAF provides a method and set of supporting tools for developing enterprise architecture and transitioning enterprises to a target architecture. It includes the Architecture Development Method which is a step-by-step approach to developing an enterprise architecture. TOGAF also includes an architecture content framework for structuring and categorizing architecture artifacts. The framework helps optimize business and IT alignment, reduce costs, and minimize implementation risks.
Computer Graphics 471 Project Report FinalAli Ahmed
This document is a project report for a 3D bowling game created by a team of students for a computer graphics course. It includes sections on the team's methodology, implementation details of the game engine, modeling, visual effects, and results. Key elements developed include a modular game engine, procedural modeling of the ball and pins with textures, shadows, reflections, collision detection, and animation sequences. The report discusses completed and uncompleted elements, and includes screenshots showcasing the results.
Enterprise architecture provides four main values: 1) It secures alignment between IT and business strategies by using a common language of business processes. 2) It supports long-term transformation by providing a map to ensure steps go in the right direction towards shared goals. 3) It identifies optimization opportunities by providing indicators on process costs and complexity. 4) It supports business continuity by documenting key IT assets so the business does not lose them if experts leave.
This document provides an overview of Scrum and its key concepts. It introduces Scrum as an Agile methodology used to manage product development. The document outlines the Scrum process including sprints, daily stand-ups, sprint planning and reviews. It describes Scrum roles like Product Owner and Scrum Master and artifacts like the product and sprint backlogs. Charts are presented to track work like burndowns and velocity. The document aims to explain how Scrum can help teams adapt to change and deliver working software frequently.
Mobile, social, big data, and cloud computing represent a new style of IT that can transform industries. An IT roadmap using this new style of IT can enable businesses by providing flexible and scalable solutions. Hewlett-Packard's strategic solution architect Pierre-Marie Delpech discusses how the new technologies can help businesses transform using an IT roadmap.
The document provides an overview of enterprise architecture (EA), including what it is, why it's useful, and how to approach EA using common frameworks. It discusses EA as both a process and product to guide organizational change. The TOGAF framework and Archimate modeling language are presented as standard tools, with Archi as a free modeling tool. An example EA project is described to identify duplicative business processes using these EA methods and tools.
The document describes a .NET template solution architecture that is flexible, maintainable, sustainable, understandable, testable, and allows for easy addition of new features. It recommends layering the solution into projects for the frontend, services, data access, entities/DTOs, repositories, view models, inversion of control, and mapping entities to view models. Each layer has specific responsibilities and dependencies designed to separate concerns and enable loose coupling between layers.
The document discusses the Visual Studio Scrum v1.0 template which maps the Scrum framework to work item types, queries, and reports in Visual Studio Team Foundation Server. It describes Scrum concepts like product backlog items, sprints, and impediments that are represented by work item types in the template. The template supports Scrum activities through standard queries and reports for tracking progress. A demonstration of the template configuration and customization is also outlined.
This document discusses job training methods and processes at an IT firm. It begins by introducing the importance of training for employees and businesses. It then provides background on the growth of the IT sector in India and the increased need for training and skills development. The rest of the document discusses various training models, domains, methods, and essential aspects of training in the IT industry. It also includes surveys on effective training delivery methods and the variation of trainer salaries with experience in the IT sector.
This document discusses using Scrum and Visual Studio 2010 for agile software development. It provides an overview of how to plan a Scrum project using Visual Studio templates, including organizing product backlogs, sprints, daily scrums, and sprint reviews. It also lists common agile practices like test-driven development, continuous integration, and refactoring that can be applied.
This document provides reviews of 3 research papers on distributed systems. The reviews were created by following a structured format including the paper title, authors, main idea, results, impact, evidence, prior work, and ideas for future work. For the first paper, the summary discusses analyzing the cost and resource optimization of running real-life applications on an open source cloud. The second paper proposes a software testing framework called IVRIDIO to provide test-first performance as a cloud service. The third paper presents a formal approach to developing fault tolerant distributed systems using refinement techniques.
This document discusses applying agile principles and practices to TOGAF architecture projects. It outlines the goals of mapping agile approaches to the TOGAF Architecture Development Method (ADM). Key aspects covered include mapping agile values, principles, practices and roles to the TOGAF ADM phases. Specific techniques like story cards, planning boards and retrospectives are described. The workshop aims to provide guidance on an agile enterprise architecture approach and get feedback to inform future standards.
The document discusses how service-oriented architecture (SOA) can help enterprise architecture (EA) practices. It proposes a service-oriented enterprise architecture (SOEA) model that represents architectures in a modular, layered manner using loosely coupled services. Applying SOA principles can help address common EA challenges by simplifying modeling, increasing stakeholder participation, and enabling flexible architecture maintenance and governance.
Team Foundation Server Process Templates For Effective Project ManagementAaron Bjork
An introduction to process templates, an overview of the Microsoft Process Template, and new process template features shipping in Team Foundation Server 2010.
This document discusses deadlock detection in distributed systems. It begins with defining deadlock and providing an example of a deadlock situation. It then explains that deadlock detection is more challenging in distributed systems due to factors like message loss and lack of shared memory. The document outlines three strategies for deadlock handling - detection and recovery, prevention, and avoidance. It proposes two approaches for deadlock detection in distributed systems: 1) using a central coordinator to merge wait-for graphs or 2) having all machines broadcast their wait-for graphs to detect deadlocks in a distributed way. Both approaches have drawbacks like single point of failure or overhead.
Agile project management with visual studio tfs 2013 - My presentation at Reg...Om Prakash Bang
This presentation is to give overview of Agile Planning for continuous delivery for value, Agile Project Management dashboard, Sprint Planning, Burn Down Charts. Distributed project team collaborate using Team Room, Task board update for all work and used during Daily Stand Up meeting.
Out of box (OOB) template for CMMI, Agile and Scrum. The main distinctions between the three default process templates are in the work item types they provide for planning and tracking work. Visual Studio Scrum is the most light-weight and MSF for Capability Maturity Model Integration (CMMI) provides the most support for formal processes and change management.
1. Microsoft Visual Studio Scrum 2013 - Choose Visual Studio Scrum if your team manages bugs along with product backlog items during sprint planning.
2. MSF for Agile Software Development 2013 - Choose Agile if your organization triages bugs separately from the product backlog and resolves work items before closing them. Also, choose Agile if your team allocates time for bugs with each sprint.
3. MSF for CMMI Process Improvement 2013 - Choose CMMI if your organization triages bugs separately from the product backlog, resolves work items before closing them, and tracks changes to requirements formally. The CMMI template is designed to support formal change management processes.
EA Intensive Course "Building Enterprise Architecture" by mr.danairatSoftware Park Thailand
This document outlines the agenda for a two-day course on building enterprise architecture. Day one covers introductions, current architecture challenges, the need for enterprise architecture, definitions of enterprise architecture, reference architecture frameworks, and group workshops. Day two covers maturity models, technology platforms, the TOGAF standard, cloud computing roadmaps, governance, and building a target architecture.
The Open Group Architecture Framework (TOGAF) is an enterprise architecture framework developed and maintained by The Open Group. TOGAF provides a method and set of supporting tools for developing enterprise architecture and transitioning enterprises to a target architecture. It includes the Architecture Development Method which is a step-by-step approach to developing an enterprise architecture. TOGAF also includes an architecture content framework for structuring and categorizing architecture artifacts. The framework helps optimize business and IT alignment, reduce costs, and minimize implementation risks.
Computer Graphics 471 Project Report FinalAli Ahmed
This document is a project report for a 3D bowling game created by a team of students for a computer graphics course. It includes sections on the team's methodology, implementation details of the game engine, modeling, visual effects, and results. Key elements developed include a modular game engine, procedural modeling of the ball and pins with textures, shadows, reflections, collision detection, and animation sequences. The report discusses completed and uncompleted elements, and includes screenshots showcasing the results.
Enterprise architecture provides four main values: 1) It secures alignment between IT and business strategies by using a common language of business processes. 2) It supports long-term transformation by providing a map to ensure steps go in the right direction towards shared goals. 3) It identifies optimization opportunities by providing indicators on process costs and complexity. 4) It supports business continuity by documenting key IT assets so the business does not lose them if experts leave.
This document provides an overview of Scrum and its key concepts. It introduces Scrum as an Agile methodology used to manage product development. The document outlines the Scrum process including sprints, daily stand-ups, sprint planning and reviews. It describes Scrum roles like Product Owner and Scrum Master and artifacts like the product and sprint backlogs. Charts are presented to track work like burndowns and velocity. The document aims to explain how Scrum can help teams adapt to change and deliver working software frequently.
Solving Agile Project Management Challenges with TeamPulseAbhishek Kant
This document provides an overview and agenda for a webinar on agile development with Telerik TeamPulse. The agenda covers Scrum planning in Sprint 0, an introduction to agile and Scrum in Sprint 1, the Scrum process in Sprint 2, Scrum metrics in Sprint 3, and a summary and Q&A in Sprints 4 and 5. The webinar discusses setting up a project in TeamPulse, capturing requirements, sprint and release planning, daily stand-ups, time tracking, testing, and reviews.
The company releases software to production every week, with 46 releases in the past year and only 1 rollback. The team consists of 9 developers, 1 product manager, 1 graphic designer, and 1 tester. They use practices like continuous integration, automated testing, daily standups, weekly demos, test environments that mirror production, zero-downtime deployments, incremental rollouts, nightly database backups, and single feature releases to deploy code quickly and reliably.
The document discusses the practices and processes used by the author's company to release software to production on a weekly basis, averaging about one release per week. Key aspects include continuous integration, automated testing and deployment, monitoring of releases in production, zero-downtime database migrations, and leveraging production data for testing. The goal is to surface issues early and keep problems out of production through a sustainable development cycle.
This document provides an introduction to the Scrum framework for agile software development. It describes Scrum roles like the Product Owner, Scrum Master, and self-organizing team. It outlines Scrum ceremonies like sprint planning, daily stand-ups, sprint reviews, and retrospectives. It also discusses the product and sprint backlogs and how teams work in sprints to deliver working software increments every 2-4 weeks using the Scrum framework.
The document discusses Scrum practices at Nucleus, a company following Agile principles. It describes how Nucleus uses Scrum ceremonies like daily standups and sprints. It notes the benefits of using tools to support continuous integration, tracking metrics, and managing backlogs and defects. However, it also discusses potential risks if quality practices like testing are not properly implemented. The presentation aims to showcase Nucleus' Agile practices and tools while also highlighting areas that require attention to fully achieve Agile principles.
Scrum is an agile framework for managing projects. It utilizes short development cycles called sprints to incrementally deliver working software. Key aspects of Scrum include sprint planning meetings, daily stand-up meetings, product backlogs prioritized by business value, and sprint reviews and retrospectives. The framework defines roles of the Product Owner, Scrum Master, and Development Team.
In this presentation we explain how we use Watir, Ruby, Cumcumber and other supporting technologies to allow end to end testing in MyHeritage.
These are the links to resource mentioned in the presentation:
Ruby - https://www.ruby-lang.org/en/
Watir - http://watirwebdriver.com/
page-object - https://github.com/cheezy/page-object
Selenium Grid - https://github.com/SeleniumHQ/selenium/wiki/Grid2
Selenium-Grid-Extras - https://github.com/groupon/Selenium-Grid-Extras
Jenkins - https://jenkins-ci.org/
We also explain how QA automation engineers are an integral part of the Continuous Deployment process at MyHeritage
The document provides an overview of the Agile Scrum process. It describes traditional waterfall methodologies and how Agile and Scrum differ by being more iterative, collaborative with stakeholders, and able to adapt to changes. The Scrum framework involves three main roles - Product Owner, Scrum Master, and Team. It also describes the four main Scrum ceremonies - Sprint Planning Meeting, Daily Standup, Sprint Review, and Sprint Retrospective - as well as the typical artifacts like Product Backlog and Sprint Backlog.
This document provides an overview of scrum, an agile project management framework. It defines key scrum roles like the product owner, scrum master, and scrum team. It also outlines the scrum process which involves sprint planning meetings, daily stand-up meetings, and working in 2-4 week sprints to develop incremental deliverables. The document notes major companies that use scrum and the advantages of increased flexibility, quality, and clear project status, while also acknowledging potential disadvantages like lack of a final plan and challenges in change management.
This document provides an overview of managing scope, time, cost, and team in Agile frameworks like Scrum. It discusses key Scrum concepts like artifacts, roles, ceremonies and how they relate to traditional project management. Scope, time and team are fixed within sprints in Scrum, unlike the waterfall model where scope is fixed upfront. Cost is estimated and budgets are determined, with value-driven development. Self-organizing cross-functional teams work in short sprints to deliver working software frequently using practices that enhance responding to change over rigid plans.
This document discusses customizing the Scrum process for a startup company. It describes the author's experience being assigned the Product Owner and Scrum Master roles without previous Scrum experience. The author learned Scrum and implemented it in their own way for their company. The document then provides an overview of key Scrum concepts like sprints, product backlogs, daily standups, sprint reviews, and retrospectives. It also discusses tools that can be used to support the Scrum process.
The document summarizes findings from a survey on continuous delivery practices. The survey found that while 81% of organizations practiced some form of continuous delivery for their code, only around 50% did so for their databases. Key challenges included a lack of database version control, manual scripting processes prone to errors, and a lack of trust and communication between developers and database administrators. Adopting database version control, automated deployments informed by version control data, and making DBAs responsible for continuous delivery processes could help address these challenges and barriers to fully implementing continuous delivery for databases.
The document discusses how support.com uses Agile methodologies like Scrum to manage product development across teams located in different countries. Key aspects that help make Scrum work globally include having local product managers and QA resources, weekly Scrum of Scrums video calls, periodic in-person meetings, common tools for requirements and source control, and 4-week Sprint cycles with mid-Sprint planning to accommodate changes across time zones. CEO support is also critical to avoid overrides after Sprints are planned.
Scaling Kanban in the Enterprise with GreenHopperDavid Jellison
Presentation delivered @Atlassian Summit 2012. Balancing the coordination of many Agile product delivery teams on the same major release cycle -- and still allowing these teams to self-organise -- is a craft Agile Enterprises must master. JIRA, GreenHopper and Confluence provide a rich platform that accommodates cross team co-ordination and the flexibility required for teams to self-organise. In this talk, David will walk the audience through the process of breaking down a Kanban value chain into steps and transitions, mapping out compatible workflows, and building the combined board. David will also share details of how Constant Contact provides visibility into the progress of teams and the release cycle. Constant Contact was able to deliver 15% more often in 2011 than prior years by refining their Agile practices.
Scrum is an agile project management framework that focuses on iterative development, self-organizing teams, and frequent inspection points. The key aspects of Scrum include roles like the product owner, Scrum master, and self-organizing development team. Events in Scrum include sprint planning meetings, daily stand-ups, sprint reviews, and retrospectives. Artifacts include the product backlog, sprint backlog, and definition of done. Scrum aims to deliver working software frequently through short iterations called sprints.
This document summarizes a presentation by Gerard Beckerleg on using Scrum with Team Foundation Server (TFS) 2012. The presentation covers Agile and Scrum theory, walks through a sample project using manual Scrum processes, and demonstrates how to use TFS 2012 and its Scrum template. It discusses the history of Scrum at SSW, an overview of Scrum roles, artifacts, and events, and how to implement the core Scrum processes like sprint planning, daily standups, reviews, and retrospectives.
This document provides an overview of key project management concepts and processes. It discusses what defines a project, factors that lead to project success or failure, and the main areas of project management including scope, cost, quality, communication, and risk management. It also outlines the requirement gathering, development, and QA processes, and includes a QMS audit checklist of typical project artifacts and documentation. The presentation concludes with time for questions.
As a software product engineering specialist, Droisys understands the significance of hiring people with the right talent and passion for technology. Our hiring methods have been designed keeping this in mind.
Droisys Provides highly interactive courses, develop and publish the courses to both HTML5 for mobile browsers and Flash for desktop browsers at the same time and develop interactive games and lessons upon customer’s request.
Sanjiv Goyal is the founder and CEO of Droisys, an offshore digital learning company based in India that partners with clients in the US to develop online training programs. Droisys uses an agile scrum model where an account manager oversees each client project, a project manager leads a creative team of designers, programmers and testers, and a client coordinator acts as the liaison to gather requirements and provide feedback. Droisys creates a variety of online courses covering topics such as business, technology, healthcare and more using interactive simulations, videos, quizzes and other eLearning elements.
The document outlines Droisys' process for developing online training programs for clients. Droisys assigns an account manager and project manager to oversee each client project. They work with the client's project coordinator to understand requirements which are then passed to Droisys' creative team to develop interactive modules, simulations, quizzes and assessments. The training programs cover various topics and are hosted online for the client to share with employees through social media and email.
Process Implementation - The Project Begin with the definitional of Process and the organizational framework. In this case, it is possible to provide very concrete instructions, as this project phase allows itself to be extensively standardized. Project Management is the application of skills, knowledge, tools and techniques to meet the needs and expectations of stakeholders for a project.
The document provides information on the resource profile, competency center, recruitment process, performance management, and training and development process of Droisys, a software company. It details the department-wise and role-wise distribution of Droisys' 62 employees. It also outlines the competency requirements for each role and the multi-stage recruitment process, including interviews and tests. Performance is managed through goal-setting, appraisals, and training. A structured training needs analysis and calendar guide skill development.
Have you ever been confused by the myriad of choices offered by AWS for hosting a website or an API?
Lambda, Elastic Beanstalk, Lightsail, Amplify, S3 (and more!) can each host websites + APIs. But which one should we choose?
Which one is cheapest? Which one is fastest? Which one will scale to meet our needs?
Join me in this session as we dive into each AWS hosting service to determine which one is best for your scenario and explain why!
Skybuffer AI: Advanced Conversational and Generative AI Solution on SAP Busin...Tatiana Kojar
Skybuffer AI, built on the robust SAP Business Technology Platform (SAP BTP), is the latest and most advanced version of our AI development, reaffirming our commitment to delivering top-tier AI solutions. Skybuffer AI harnesses all the innovative capabilities of the SAP BTP in the AI domain, from Conversational AI to cutting-edge Generative AI and Retrieval-Augmented Generation (RAG). It also helps SAP customers safeguard their investments into SAP Conversational AI and ensure a seamless, one-click transition to SAP Business AI.
With Skybuffer AI, various AI models can be integrated into a single communication channel such as Microsoft Teams. This integration empowers business users with insights drawn from SAP backend systems, enterprise documents, and the expansive knowledge of Generative AI. And the best part of it is that it is all managed through our intuitive no-code Action Server interface, requiring no extensive coding knowledge and making the advanced AI accessible to more users.
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-und-domino-lizenzkostenreduzierung-in-der-welt-von-dlau/
DLAU und die Lizenzen nach dem CCB- und CCX-Modell sind für viele in der HCL-Community seit letztem Jahr ein heißes Thema. Als Notes- oder Domino-Kunde haben Sie vielleicht mit unerwartet hohen Benutzerzahlen und Lizenzgebühren zu kämpfen. Sie fragen sich vielleicht, wie diese neue Art der Lizenzierung funktioniert und welchen Nutzen sie Ihnen bringt. Vor allem wollen Sie sicherlich Ihr Budget einhalten und Kosten sparen, wo immer möglich. Das verstehen wir und wir möchten Ihnen dabei helfen!
Wir erklären Ihnen, wie Sie häufige Konfigurationsprobleme lösen können, die dazu führen können, dass mehr Benutzer gezählt werden als nötig, und wie Sie überflüssige oder ungenutzte Konten identifizieren und entfernen können, um Geld zu sparen. Es gibt auch einige Ansätze, die zu unnötigen Ausgaben führen können, z. B. wenn ein Personendokument anstelle eines Mail-Ins für geteilte Mailboxen verwendet wird. Wir zeigen Ihnen solche Fälle und deren Lösungen. Und natürlich erklären wir Ihnen das neue Lizenzmodell.
Nehmen Sie an diesem Webinar teil, bei dem HCL-Ambassador Marc Thomas und Gastredner Franz Walder Ihnen diese neue Welt näherbringen. Es vermittelt Ihnen die Tools und das Know-how, um den Überblick zu bewahren. Sie werden in der Lage sein, Ihre Kosten durch eine optimierte Domino-Konfiguration zu reduzieren und auch in Zukunft gering zu halten.
Diese Themen werden behandelt
- Reduzierung der Lizenzkosten durch Auffinden und Beheben von Fehlkonfigurationen und überflüssigen Konten
- Wie funktionieren CCB- und CCX-Lizenzen wirklich?
- Verstehen des DLAU-Tools und wie man es am besten nutzt
- Tipps für häufige Problembereiche, wie z. B. Team-Postfächer, Funktions-/Testbenutzer usw.
- Praxisbeispiele und Best Practices zum sofortigen Umsetzen
Ocean lotus Threat actors project by John Sitima 2024 (1).pptxSitimaJohn
Ocean Lotus cyber threat actors represent a sophisticated, persistent, and politically motivated group that poses a significant risk to organizations and individuals in the Southeast Asian region. Their continuous evolution and adaptability underscore the need for robust cybersecurity measures and international cooperation to identify and mitigate the threats posed by such advanced persistent threat groups.
Your One-Stop Shop for Python Success: Top 10 US Python Development Providersakankshawande
Simplify your search for a reliable Python development partner! This list presents the top 10 trusted US providers offering comprehensive Python development services, ensuring your project's success from conception to completion.
Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on integration of Salesforce with Bonterra Impact Management.
Interested in deploying an integration with Salesforce for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
Programming Foundation Models with DSPy - Meetup SlidesZilliz
Prompting language models is hard, while programming language models is easy. In this talk, I will discuss the state-of-the-art framework DSPy for programming foundation models with its powerful optimizers and runtime constraint system.
Trusted Execution Environment for Decentralized Process MiningLucaBarbaro3
Presentation of the paper "Trusted Execution Environment for Decentralized Process Mining" given during the CAiSE 2024 Conference in Cyprus on June 7, 2024.
Dive into the realm of operating systems (OS) with Pravash Chandra Das, a seasoned Digital Forensic Analyst, as your guide. 🚀 This comprehensive presentation illuminates the core concepts, types, and evolution of OS, essential for understanding modern computing landscapes.
Beginning with the foundational definition, Das clarifies the pivotal role of OS as system software orchestrating hardware resources, software applications, and user interactions. Through succinct descriptions, he delineates the diverse types of OS, from single-user, single-task environments like early MS-DOS iterations, to multi-user, multi-tasking systems exemplified by modern Linux distributions.
Crucial components like the kernel and shell are dissected, highlighting their indispensable functions in resource management and user interface interaction. Das elucidates how the kernel acts as the central nervous system, orchestrating process scheduling, memory allocation, and device management. Meanwhile, the shell serves as the gateway for user commands, bridging the gap between human input and machine execution. 💻
The narrative then shifts to a captivating exploration of prominent desktop OSs, Windows, macOS, and Linux. Windows, with its globally ubiquitous presence and user-friendly interface, emerges as a cornerstone in personal computing history. macOS, lauded for its sleek design and seamless integration with Apple's ecosystem, stands as a beacon of stability and creativity. Linux, an open-source marvel, offers unparalleled flexibility and security, revolutionizing the computing landscape. 🖥️
Moving to the realm of mobile devices, Das unravels the dominance of Android and iOS. Android's open-source ethos fosters a vibrant ecosystem of customization and innovation, while iOS boasts a seamless user experience and robust security infrastructure. Meanwhile, discontinued platforms like Symbian and Palm OS evoke nostalgia for their pioneering roles in the smartphone revolution.
The journey concludes with a reflection on the ever-evolving landscape of OS, underscored by the emergence of real-time operating systems (RTOS) and the persistent quest for innovation and efficiency. As technology continues to shape our world, understanding the foundations and evolution of operating systems remains paramount. Join Pravash Chandra Das on this illuminating journey through the heart of computing. 🌟
Taking AI to the Next Level in Manufacturing.pdfssuserfac0301
Read Taking AI to the Next Level in Manufacturing to gain insights on AI adoption in the manufacturing industry, such as:
1. How quickly AI is being implemented in manufacturing.
2. Which barriers stand in the way of AI adoption.
3. How data quality and governance form the backbone of AI.
4. Organizational processes and structures that may inhibit effective AI adoption.
6. Ideas and approaches to help build your organization's AI strategy.
Fueling AI with Great Data with Airbyte WebinarZilliz
This talk will focus on how to collect data from a variety of sources, leveraging this data for RAG and other GenAI use cases, and finally charting your course to productionalization.
How to Interpret Trends in the Kalyan Rajdhani Mix Chart.pdfChart Kalyan
A Mix Chart displays historical data of numbers in a graphical or tabular form. The Kalyan Rajdhani Mix Chart specifically shows the results of a sequence of numbers over different periods.
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slackshyamraj55
Discover the seamless integration of RPA (Robotic Process Automation), COMPOSER, and APM with AWS IDP enhanced with Slack notifications. Explore how these technologies converge to streamline workflows, optimize performance, and ensure secure access, all while leveraging the power of AWS IDP and real-time communication via Slack notifications.
4. Definitions
Product Backlog
• User requirements ( stories )
• Prioritized by product owner
Sprint
• 1 to 4 weeks iterations
Sprint Backlog
• list of tasks that to be completed in a sprint
Sprint Planning Meeting
• Meet before every Sprint
• Break down stories into tasks
Daily Scrum Meeting
• Scrum Team Member meeting
• 15 minutes
4
7. Benefits
Scrum allows for better communication
Scrum helps with transparency
Scrum helps for quality
Scrum exposes existing problems and surfaces new problems as soon as they
come up.
Scrum helps to learn from the past
7
8. QA Process
Project Bug / issue tracker
Issues priority
Issues Status
15
10
Closed
5
Fix Not Confirmed
0
Open
High
Medium
Low
Critical
8
9. QA Process
Requirement gathering template
Requirement validation template
Code review process
Coding Guidelines and Standards
Configuration management tool
Unit test checklist
Casual analysis for quality improvement
Release note
Change request template
Etc.
9
10. Droisys Business continuity plan
• Work Locations
• Hardware & Software
• Configuration Management
• Resources
• Process Management and Auditing
• IT Security
1
0
11. Droisys Server’s and Version control system
• Win server (windows 2003 R2 Server )
Active directory
• Hyper-V (windows hyper-v 2008)
Alfresco & Bugzilla
SVN Backup server
Ubuntu server- OpenERP
• Firewall mgmt (Server 2003 R2)
• Symantec (Windows server 2008)
• Intranet App (Ubuntu server 8.04)
• SharePoint (Windows Server 2003 R2 )
• Buffalo NAS (Network Storage )
• Firewall (Sonic Wall)
1
1