Introductie slides Agile Coaching door het Nederlands Instituut voor de Software Industrie
•Download as PPTX, PDF•
1 like•805 views
Dit zijn de slides voor de cursus Agile Coaching, die wordt verzorgd door het Nederlands Instituut voor de Software Industrie. Voor meer informatie over het Nederlands Instituut voor de Software Industrie, kijk dan op www.nisi.nl
Report
Share
Report
Share
Recommended
Introductie slides Agile Software Architecture
De introductie slides voor de cursus Agile Software Architecture, die gegeven wordt door het Nederlands Instituut voor de Software Industrie.
Voor meer informatie, kijk op http://nisi.nl/cursussen/agile-software-architecture
Introductie slides Continuous Delivery 3.0
This document provides an overview of the Continuous Delivery 3.0 course organized by the Netherlands Institute for the Software Industry (NISI). The course aims to help companies implement Continuous Delivery practices to enable fast software delivery. It covers topics like continuous integration, testing, deployment, tracking, and planning. The course teaches how to build, test, and release software frequently using modern DevOps tooling and cloud technologies. Upon completion, participants will be certified in Continuous Delivery 3.0 through the International Software Product Management Association.
Introductie slides Advanced Agile Product Ownership door het Nederlands Insti...
Dit zijn de slides voor de cursus Advanced Agile Product Ownership, die wordt verzorgd door het Nederlands Instituut voor de Software Industrie.
Voor meer informatie over het Nederlands Instituut voor de Software Industrie, kijk dan op www.nisi.nl
Introductie slides Software Product Management door het Nederlands Instituut ...
Dit zijn de slides voor de cursus Software Product Management, die wordt verzorgd door het Nederlands Instituut voor de Software Industrie en de Universiteit Utrecht.
Voor meer informatie over het Nederlands Instituut voor de Software Industrie, kijk dan op www.nisi.nl
UX @ Harvard's IQSS (Elizabeth Quigley)
On November 12, 2014, Elizabeth Quigley gave a talk titled "UX @ Harvard's IQSS."
Details of the talk appear below.
---------------------------------------------
When: November 12th @ 3:30-5:00pm
Title: UX @ IQSS
Who: Elizabeth Quigley, Usability Specialist, Data Science Team, Institute of Quantitative Social Science
Where: Harvard University, Lamont Library, Forum Room
Description: Over the past year and a half, the Institute for Quantitative Social Science (IQSS) has integrated multiple user experience methods into their product development cycle to enhance the user experience for multiple products and websites developed at IQSS.
Elizabeth Quigley, Usability Specialist at IQSS, will outline how to start a user experience program for your products and/or websites, demonstrate the UX methods she uses, and show examples of how the UX of IQSS products and websites has been enhanced through these methods. If you have ever wondered how to start a user experience program, this is the talk for you.
Bio: Elizabeth has an M.S. in Library and Information Science from the School of Library and Information Science at Simmons College. She has conducted user research on the collaborative processes and profiles of undergraduates interacting with a Microsoft surface table, academic portals, the use of a library website by faculty members as well as the products and websites developed at the Institute for Quantitative Social Science.
Agile Development – Why requirements matter by Fariz Saracevic
The clear benefits of agile development is a better collaboration, incremental delivery, early error detection and the elimination of unnecessary work—have made it the default approach for many teams. Some developers have questioned whether requirements fall into the category of unnecessary work, and can be cut down or even completely eliminated. Meanwhile, teams developing complex products, systems and regulated IT continue to have requirements-driven legacy processes.
So how does requirements management fit in an agile world? This meetup will take a look at requirements management and how it can bring significant value to agile development in regulated IT and complex product development projects, and sets out the characteristics of an effective requirements management approach in an agile environment.
Design your own BPM Program Strategy with Alfresco Process Services
This session is aimed to show how to design your process strategy following international best practices (ISO and AIIM) using the futuristic Alfresco Process Services Platform.
We will see how to survive to the requirements gathering caos in order to avoid the typical issues when you start to implement a new BPM platform.
ACT-IAC Partners #GovDevOps: PTO - agile - and DevOps
This document discusses Agile, DevOps, and their implementation at USPTO. It provides background on Agile being a lightweight framework based on the Agile Manifesto. DevOps aims to improve collaboration between development and operations teams through practices like automation. USPTO adopted DevOps to enable continuous rapid development through continuous rapid deployment, overcoming barriers of legacy production processes. The document outlines USPTO's DevOps journey, including adopting practices like a deployment pipeline and production monitoring. It also discusses top challenges to DevOps adoption like fear of failure and bureaucracy, and how to start small and show value to gain support.
Recommended
Introductie slides Agile Software Architecture
De introductie slides voor de cursus Agile Software Architecture, die gegeven wordt door het Nederlands Instituut voor de Software Industrie.
Voor meer informatie, kijk op http://nisi.nl/cursussen/agile-software-architecture
Introductie slides Continuous Delivery 3.0
This document provides an overview of the Continuous Delivery 3.0 course organized by the Netherlands Institute for the Software Industry (NISI). The course aims to help companies implement Continuous Delivery practices to enable fast software delivery. It covers topics like continuous integration, testing, deployment, tracking, and planning. The course teaches how to build, test, and release software frequently using modern DevOps tooling and cloud technologies. Upon completion, participants will be certified in Continuous Delivery 3.0 through the International Software Product Management Association.
Introductie slides Advanced Agile Product Ownership door het Nederlands Insti...
Dit zijn de slides voor de cursus Advanced Agile Product Ownership, die wordt verzorgd door het Nederlands Instituut voor de Software Industrie.
Voor meer informatie over het Nederlands Instituut voor de Software Industrie, kijk dan op www.nisi.nl
Introductie slides Software Product Management door het Nederlands Instituut ...
Dit zijn de slides voor de cursus Software Product Management, die wordt verzorgd door het Nederlands Instituut voor de Software Industrie en de Universiteit Utrecht.
Voor meer informatie over het Nederlands Instituut voor de Software Industrie, kijk dan op www.nisi.nl
UX @ Harvard's IQSS (Elizabeth Quigley)
On November 12, 2014, Elizabeth Quigley gave a talk titled "UX @ Harvard's IQSS."
Details of the talk appear below.
---------------------------------------------
When: November 12th @ 3:30-5:00pm
Title: UX @ IQSS
Who: Elizabeth Quigley, Usability Specialist, Data Science Team, Institute of Quantitative Social Science
Where: Harvard University, Lamont Library, Forum Room
Description: Over the past year and a half, the Institute for Quantitative Social Science (IQSS) has integrated multiple user experience methods into their product development cycle to enhance the user experience for multiple products and websites developed at IQSS.
Elizabeth Quigley, Usability Specialist at IQSS, will outline how to start a user experience program for your products and/or websites, demonstrate the UX methods she uses, and show examples of how the UX of IQSS products and websites has been enhanced through these methods. If you have ever wondered how to start a user experience program, this is the talk for you.
Bio: Elizabeth has an M.S. in Library and Information Science from the School of Library and Information Science at Simmons College. She has conducted user research on the collaborative processes and profiles of undergraduates interacting with a Microsoft surface table, academic portals, the use of a library website by faculty members as well as the products and websites developed at the Institute for Quantitative Social Science.
Agile Development – Why requirements matter by Fariz Saracevic
The clear benefits of agile development is a better collaboration, incremental delivery, early error detection and the elimination of unnecessary work—have made it the default approach for many teams. Some developers have questioned whether requirements fall into the category of unnecessary work, and can be cut down or even completely eliminated. Meanwhile, teams developing complex products, systems and regulated IT continue to have requirements-driven legacy processes.
So how does requirements management fit in an agile world? This meetup will take a look at requirements management and how it can bring significant value to agile development in regulated IT and complex product development projects, and sets out the characteristics of an effective requirements management approach in an agile environment.
Design your own BPM Program Strategy with Alfresco Process Services
This session is aimed to show how to design your process strategy following international best practices (ISO and AIIM) using the futuristic Alfresco Process Services Platform.
We will see how to survive to the requirements gathering caos in order to avoid the typical issues when you start to implement a new BPM platform.
ACT-IAC Partners #GovDevOps: PTO - agile - and DevOps
This document discusses Agile, DevOps, and their implementation at USPTO. It provides background on Agile being a lightweight framework based on the Agile Manifesto. DevOps aims to improve collaboration between development and operations teams through practices like automation. USPTO adopted DevOps to enable continuous rapid development through continuous rapid deployment, overcoming barriers of legacy production processes. The document outlines USPTO's DevOps journey, including adopting practices like a deployment pipeline and production monitoring. It also discusses top challenges to DevOps adoption like fear of failure and bureaucracy, and how to start small and show value to gain support.
Building a Great Team in Open Source - Open Agile 2011
Lessons I learned over the last 2 years as an open source contributor at The Apache Software Foundation.
How_to_survive
1) Businesses require faster development speed while maintaining operational stability, but continuous development without proper implementation often leads to continuous failures.
2) Development and operations teams have different goals, with development wanting change and operations wanting stability, creating a paradox.
3) People, processes, tools, and organizational structures often differ between development and operations, exacerbating conflicts between the two.
Smart Alfresco ECM Program Strategy for Your New Success Story
This presentation includes hints, best practices and international standards to simplify your ECM gathering requirement process before and during the implementation phase.
The ECM Program Strategy should be written before starting to implement and it should contain a set of documents describing the vision of your project containing also all the stakeholders goals in terms of functionalities and UX needs.
Why Experience Design is a Key Skill in the Digital Era
Presented by Mr Frederic Giron, Vice President & Research Director, Forrester Research, at NUS-ISS Digital Leadership & Innovation Conference 2015 on 20 Nov 2015.
Prototyping - Get the right tools and workflow
Prototyping is an important part of the design process that allows designers to test concepts and assumptions through iterative refinement. There are different types of prototypes that serve different purposes, from low-fidelity paper prototypes for collaboration to high-fidelity digital prototypes for detailed user testing. Choosing the right prototyping tool depends on factors like the intended audience, required level of detail, need for interactivity, and integration with other tools. Evaluating tools based on their learning curve, speed, affordability, and ability to support iterations is key to finding the best fit for each prototyping task.
2018 State Of DevOps Report Key Findings
Sally Reade, Partner Manager, Puppet
Puppet's State of DevOps report is the most comprehensive study in the field, making it a must-read for practitioners and technological leaders alike. Sally Reade distills key takeaways, including practical tips like "start with the practices that are closest to production; then address processes that happen earlier in the software delivery cycle." Why do C-suite have too rosy a view of DevOps on the ground?
Agile software development methodology
This presentation is about Agile software development it's history and how it is related to e-learning.
Software Development Life Cycle
The document discusses different software development life cycle (SDLC) methodologies, including the waterfall model and agile model.
The waterfall model is the oldest and simplest linear sequential model where each phase must be completed before the next begins. Its advantages are its simplicity and ease of management, while its disadvantages include difficulty making changes and high risks.
The agile model is iterative with work done in short cycles (sprints) to iteratively develop working software. Its advantages include continuous improvement and adaptability, while potential disadvantages include lack of documentation and processes.
For scaling up Facebook in 2006, an agile model would be chosen to allow for rapid iterations and incorporation of user feedback as the platform grows. Depart
DOES15 - Heather Mickman & Ross Clanton - (Re)building an Engineering Culture...
Heather Mickman, Senior Group Manager, Target
Ross Clanton, Director, Target
This talk will largely be a reflection on the DevOps journey at Target and the focus on (re)building an engineering culture at Target. In the DevOps community you hear a lot of talk about whether you should drive DevOps in to an organization tops down or bottoms up. Well, we did a hybrid of both. It definitely started at Target as a grass roots movement in a few small teams and started to gain broader grassroots momentum when we kicked off our first internal DevOps Days in February 2014. This enabled us to start engaging a community, finding out who had passion for this across our IT organization, and providing them a forum to connect, share, and learn about DevOps awesomeness. We fostered and grew this community by leveraging social media and guerilla marketing to start driving the conversation across our organization as well as demonstrating the success that teams were having. We then leveraged some of this early energy to engage more leader champions to start building the tops down support for DevOps. Now, having completed four DevOps Days conferences at Target, we will share more details on our approach, results, speakers, and topics.
We did much more than just hosting DevOps Days. We tapped in to that growing community to start testing and learning some different approaches and we have lots to share, both in terms of results we’ve achieved and how we’re focusing on changing culture and mindsets. From a technology perspective, we will discuss how we rapidly drove momentum on our automation toolchain across our IT organization. Our vision was to enable and empower all technologists to automate the things that they were accountable for. We pursued this vision in many ways, including Automation hackathons, establishing an embedding/coaching model for our deep SMEs to help teach, open labs, community based support, and even schemed some creative work models that we will share.
The end result of these various activities is driving full stack ownership that will ultimately enable the expansion of CI/CD across our Enterprise. This is the overarching theme and next step in our enterprise transformation. It is through this foundation we are building around culture, tooling, collaborative and flexible work models that will enable our acceleration in 2015. Moving forward, we are leveraging these learnings to shift to more of a full-stack product model for our technology delivery and management. We’re also transforming infrastructure from a model based on technology silos to an end to end infrastructure service model focused on enabling business agility.
These changes haven’t been easy. In fact, we’ve already had a lot of learnings on our journey. We will share some of those key challenges and lessons learned, specifically on talent, culture, and leadership.
UNIwise Presentation @ Educate 2017
UNIwise is a digital exam and assessment platform spun out of Aarhus University that delivers WISEflow, a cloud-based end-to-end platform. WISEflow uses Learnosity's APIs to provide advanced MCQ authoring, delivery, assessment, and reporting capabilities. UNIwise is presenting their use of Learnosity's APIs to assess MCQs and their newest points-based assessment functionality, which allows for fully automated assessment from points to grades. They also discussed future plans to implement rubric-based assessment through a series of weighted question types scored by assessors.
Dc scrum agile_eng_20130923
Scrum and Agile Engineering Practices - What every ScrumMaster needs to know
Some Agile teams fail to figure out or implement technical practices that are necessary for long term success. Practices like automated builds, automated tests, automated deployments, continuous integration, and continuous delivery are now considered essential for the success of any software development project. Join us for a tour of software engineering best practices. We'll discuss what these practices are and their impact on scope, schedule, cost, resources and quality. We'll also share some ideas on how to start adopting these practices and how to incrementally introduce them and gradually improve your team's software development process.
C1 speaker series_talk
This document discusses using a project-based approach to finding and attracting data engineers. It recommends that companies encourage their teams to contribute to open source projects, which can engage teams and attract qualified applicants. It also suggests using project-based challenges for candidates and having teams build projects unrelated to the core product. Projects allow candidates to demonstrate their skills and knowledge, and companies benefit from experience with new technologies. This approach led to a 40% increase in qualified applicants for the Insight Fellows Program.
Accept innovation jam pcamp 2011
An innovation jam is a short, focused period where employees think creatively and work collaboratively outside normal processes. The company held a week-long innovation jam where employees proposed and voted on ideas, then teams spent a weekend developing top ideas using new technologies. While teams made progress prototyping ideas, fully developing products requires more time. However, the jam was a success in testing ideas, motivating employees with new technologies, and giving the company opportunities to contribute to product progress. The company plans to hold more innovation jams going forward.
Continuous Integration
The document discusses continuous integration practices. It describes some key rules and prerequisites for continuous integration, including maintaining a code repository, automating builds, ensuring builds are self-testing, and committing code changes frequently. It also discusses source code management best practices for continuous integration like tagging releases and using branching strategies. Additionally, it covers the need for automated build tools, a continuous integration server, and quality analysis/reporting tools to enable continuous integration.
2016.06 ACT-IAC Partners breakfast: GSA's 18F on DevOps delivery
The document discusses DevOps and its application in government agencies. It provides examples of how two agencies - the Federal Election Commission (FEC) and Nuclear Regulatory Commission (NRC) - have begun their DevOps journeys. It also outlines key characteristics of DevOps, such as automating processes, measuring outcomes, and creating a collaborative culture. Finally, it discusses how DevOps may evolve in government in the future through greater standardization, automation, measurement practices, and an emphasis on lean and adaptable organizations.
DevOpsDays Houston 2019 - Sagar Karmarkar - Organic DevOps - DevOps from with...
Most senior executives in large enterprises believe DevOps and CI/CD are interchangeable. If I have a CI/CD pipeline, I am “doing DevOps”, right? Not exactly. The dilemma that these executives have is that they don’t believe DevOps can be with the people they have. It can be done. I’ll show you how!
Working with software architects - advice to project managers
This document provides advice to project managers on working with software architects. It defines what software architecture is and discusses different styles such as big design up front, emerging architecture, and good enough architecture. It also covers what architects do including technical oversight, standards enforcement, and long term technical visioning. The document advises involving architects early and regularly throughout the project lifecycle from initiation and planning through execution, monitoring, and closing. Architects are positioned as key partners to project managers.
Epm seminar presentation
This document provides an overview of Enterprise Project Management (EPM). It defines EPM as taking a holistic view of all project management activities across an organization to support business goals and strategy. EPM is supported by software that provides visibility and management of all projects from demand to reporting. When selecting EPM software, organizations should consider factors like cost, features, methodology support, reporting capabilities, and maintenance/support. EPM software can help align work, enable collaboration, and provide insights to improve project execution across an enterprise.
PhuNguyeAgileStudyReport201506
This document summarizes four popular Agile methodologies: Scrum, Extreme Programming (XP), Lean, and Kanban. Scrum is an Agile methodology for project management that relies on self-organization and collective commitment. It uses sprints, daily stand-ups, and retrospectives. XP focuses on simple designs, testing, pair programming, and frequent integration. Lean promotes eliminating waste. Kanban uses visual boards and limits work-in-progress to focus on continuous flow. Agile practices can help teams achieve better results than traditional methods if they embrace the mindsets behind each methodology.
Is There Room For Project Managers In An Agile Like Environment Such As Scrum1
Agile methodologies like Scrum use iterative development between self-organizing cross-functional teams. Scrum consists of roles, ceremonies, and artifacts to facilitate incremental product development by teams of 6-7 people. While Scrum does not require project managers, it allows room for project managers by training them in Scrum practices and having them serve as Scrum masters to coordinate teams. Project managers can benefit Agile teams by learning Scrum and applying its principles without trying to change the framework.
PFCongres - Test Improvement 4 Agile
When we want to improve, for some reason we usually start to question testing. But what are the right questions to ask in an Agile context? Current TPI models have proven to be a mismatch when assessing and improving the test process in this context. So what is missing in the current models and how can we help companies improve their testing in an Agile context? It seems that it is significantly harder to describe how to become more flexible than it is to describe how to become more structured.
Jeroen will introduce a stepwise approach to improve the testing in Agile software development. The Agile Manifesto, the SCRUM process and the field experience of numerous testers form the basis for this new model. In an interactive session he will show new key areas to consider and introduce good practices that will help to improve testing in an Agile context. Some key areas of the current TPI models are changed to fit the Agile context. All other key areas are specifically aimed at the Agile context. Examples of new key areas are “People”, “Teamwork” and “Regression & E2E testing”. You will see that the development process is part of the model as well, since testing and development are completely integrated. The Agile Manifesto tells us to value people and interactions over processes and tools. Therefore the assessment and improvement model includes key areas and checkpoints that are directed at people and interactions. Last but not least, it is a test improvement model… So the model will still be focused on testing aspects. The complete model is fit for purpose and fit for Agile, in wording, terminology and the ideas behind it.
You will leave this tutorial with more knowledge on how to fit testing within Agile as well as on how to improve testing. Additionally you will take away a set of good practices that add value to your testing immediately.
Agile and-scrum
#Agile software development is based on principles de fined by the Agile Manifesto;
a disciplined project management outline that is conducive to dynamic inspection
and adaptation. Agile methods include many product development frameworks
such as Scrum and XP (eXtreme Programming) which allow for rapid delivery of
software. The Scrum framework uses simple iterative practices for team collaboration
on complex projects.
More Related Content
What's hot
Building a Great Team in Open Source - Open Agile 2011
Lessons I learned over the last 2 years as an open source contributor at The Apache Software Foundation.
How_to_survive
1) Businesses require faster development speed while maintaining operational stability, but continuous development without proper implementation often leads to continuous failures.
2) Development and operations teams have different goals, with development wanting change and operations wanting stability, creating a paradox.
3) People, processes, tools, and organizational structures often differ between development and operations, exacerbating conflicts between the two.
Smart Alfresco ECM Program Strategy for Your New Success Story
This presentation includes hints, best practices and international standards to simplify your ECM gathering requirement process before and during the implementation phase.
The ECM Program Strategy should be written before starting to implement and it should contain a set of documents describing the vision of your project containing also all the stakeholders goals in terms of functionalities and UX needs.
Why Experience Design is a Key Skill in the Digital Era
Presented by Mr Frederic Giron, Vice President & Research Director, Forrester Research, at NUS-ISS Digital Leadership & Innovation Conference 2015 on 20 Nov 2015.
Prototyping - Get the right tools and workflow
Prototyping is an important part of the design process that allows designers to test concepts and assumptions through iterative refinement. There are different types of prototypes that serve different purposes, from low-fidelity paper prototypes for collaboration to high-fidelity digital prototypes for detailed user testing. Choosing the right prototyping tool depends on factors like the intended audience, required level of detail, need for interactivity, and integration with other tools. Evaluating tools based on their learning curve, speed, affordability, and ability to support iterations is key to finding the best fit for each prototyping task.
2018 State Of DevOps Report Key Findings
Sally Reade, Partner Manager, Puppet
Puppet's State of DevOps report is the most comprehensive study in the field, making it a must-read for practitioners and technological leaders alike. Sally Reade distills key takeaways, including practical tips like "start with the practices that are closest to production; then address processes that happen earlier in the software delivery cycle." Why do C-suite have too rosy a view of DevOps on the ground?
Agile software development methodology
This presentation is about Agile software development it's history and how it is related to e-learning.
Software Development Life Cycle
The document discusses different software development life cycle (SDLC) methodologies, including the waterfall model and agile model.
The waterfall model is the oldest and simplest linear sequential model where each phase must be completed before the next begins. Its advantages are its simplicity and ease of management, while its disadvantages include difficulty making changes and high risks.
The agile model is iterative with work done in short cycles (sprints) to iteratively develop working software. Its advantages include continuous improvement and adaptability, while potential disadvantages include lack of documentation and processes.
For scaling up Facebook in 2006, an agile model would be chosen to allow for rapid iterations and incorporation of user feedback as the platform grows. Depart
DOES15 - Heather Mickman & Ross Clanton - (Re)building an Engineering Culture...
Heather Mickman, Senior Group Manager, Target
Ross Clanton, Director, Target
This talk will largely be a reflection on the DevOps journey at Target and the focus on (re)building an engineering culture at Target. In the DevOps community you hear a lot of talk about whether you should drive DevOps in to an organization tops down or bottoms up. Well, we did a hybrid of both. It definitely started at Target as a grass roots movement in a few small teams and started to gain broader grassroots momentum when we kicked off our first internal DevOps Days in February 2014. This enabled us to start engaging a community, finding out who had passion for this across our IT organization, and providing them a forum to connect, share, and learn about DevOps awesomeness. We fostered and grew this community by leveraging social media and guerilla marketing to start driving the conversation across our organization as well as demonstrating the success that teams were having. We then leveraged some of this early energy to engage more leader champions to start building the tops down support for DevOps. Now, having completed four DevOps Days conferences at Target, we will share more details on our approach, results, speakers, and topics.
We did much more than just hosting DevOps Days. We tapped in to that growing community to start testing and learning some different approaches and we have lots to share, both in terms of results we’ve achieved and how we’re focusing on changing culture and mindsets. From a technology perspective, we will discuss how we rapidly drove momentum on our automation toolchain across our IT organization. Our vision was to enable and empower all technologists to automate the things that they were accountable for. We pursued this vision in many ways, including Automation hackathons, establishing an embedding/coaching model for our deep SMEs to help teach, open labs, community based support, and even schemed some creative work models that we will share.
The end result of these various activities is driving full stack ownership that will ultimately enable the expansion of CI/CD across our Enterprise. This is the overarching theme and next step in our enterprise transformation. It is through this foundation we are building around culture, tooling, collaborative and flexible work models that will enable our acceleration in 2015. Moving forward, we are leveraging these learnings to shift to more of a full-stack product model for our technology delivery and management. We’re also transforming infrastructure from a model based on technology silos to an end to end infrastructure service model focused on enabling business agility.
These changes haven’t been easy. In fact, we’ve already had a lot of learnings on our journey. We will share some of those key challenges and lessons learned, specifically on talent, culture, and leadership.
UNIwise Presentation @ Educate 2017
UNIwise is a digital exam and assessment platform spun out of Aarhus University that delivers WISEflow, a cloud-based end-to-end platform. WISEflow uses Learnosity's APIs to provide advanced MCQ authoring, delivery, assessment, and reporting capabilities. UNIwise is presenting their use of Learnosity's APIs to assess MCQs and their newest points-based assessment functionality, which allows for fully automated assessment from points to grades. They also discussed future plans to implement rubric-based assessment through a series of weighted question types scored by assessors.
Dc scrum agile_eng_20130923
Scrum and Agile Engineering Practices - What every ScrumMaster needs to know
Some Agile teams fail to figure out or implement technical practices that are necessary for long term success. Practices like automated builds, automated tests, automated deployments, continuous integration, and continuous delivery are now considered essential for the success of any software development project. Join us for a tour of software engineering best practices. We'll discuss what these practices are and their impact on scope, schedule, cost, resources and quality. We'll also share some ideas on how to start adopting these practices and how to incrementally introduce them and gradually improve your team's software development process.
C1 speaker series_talk
This document discusses using a project-based approach to finding and attracting data engineers. It recommends that companies encourage their teams to contribute to open source projects, which can engage teams and attract qualified applicants. It also suggests using project-based challenges for candidates and having teams build projects unrelated to the core product. Projects allow candidates to demonstrate their skills and knowledge, and companies benefit from experience with new technologies. This approach led to a 40% increase in qualified applicants for the Insight Fellows Program.
Accept innovation jam pcamp 2011
An innovation jam is a short, focused period where employees think creatively and work collaboratively outside normal processes. The company held a week-long innovation jam where employees proposed and voted on ideas, then teams spent a weekend developing top ideas using new technologies. While teams made progress prototyping ideas, fully developing products requires more time. However, the jam was a success in testing ideas, motivating employees with new technologies, and giving the company opportunities to contribute to product progress. The company plans to hold more innovation jams going forward.
Continuous Integration
The document discusses continuous integration practices. It describes some key rules and prerequisites for continuous integration, including maintaining a code repository, automating builds, ensuring builds are self-testing, and committing code changes frequently. It also discusses source code management best practices for continuous integration like tagging releases and using branching strategies. Additionally, it covers the need for automated build tools, a continuous integration server, and quality analysis/reporting tools to enable continuous integration.
2016.06 ACT-IAC Partners breakfast: GSA's 18F on DevOps delivery
The document discusses DevOps and its application in government agencies. It provides examples of how two agencies - the Federal Election Commission (FEC) and Nuclear Regulatory Commission (NRC) - have begun their DevOps journeys. It also outlines key characteristics of DevOps, such as automating processes, measuring outcomes, and creating a collaborative culture. Finally, it discusses how DevOps may evolve in government in the future through greater standardization, automation, measurement practices, and an emphasis on lean and adaptable organizations.
DevOpsDays Houston 2019 - Sagar Karmarkar - Organic DevOps - DevOps from with...
Most senior executives in large enterprises believe DevOps and CI/CD are interchangeable. If I have a CI/CD pipeline, I am “doing DevOps”, right? Not exactly. The dilemma that these executives have is that they don’t believe DevOps can be with the people they have. It can be done. I’ll show you how!
Working with software architects - advice to project managers
This document provides advice to project managers on working with software architects. It defines what software architecture is and discusses different styles such as big design up front, emerging architecture, and good enough architecture. It also covers what architects do including technical oversight, standards enforcement, and long term technical visioning. The document advises involving architects early and regularly throughout the project lifecycle from initiation and planning through execution, monitoring, and closing. Architects are positioned as key partners to project managers.
What's hot (17)
Building a Great Team in Open Source - Open Agile 2011
Building a Great Team in Open Source - Open Agile 2011
Smart Alfresco ECM Program Strategy for Your New Success Story
Smart Alfresco ECM Program Strategy for Your New Success Story
Why Experience Design is a Key Skill in the Digital Era
Why Experience Design is a Key Skill in the Digital Era
DOES15 - Heather Mickman & Ross Clanton - (Re)building an Engineering Culture...
DOES15 - Heather Mickman & Ross Clanton - (Re)building an Engineering Culture...
2016.06 ACT-IAC Partners breakfast: GSA's 18F on DevOps delivery
2016.06 ACT-IAC Partners breakfast: GSA's 18F on DevOps delivery
DevOpsDays Houston 2019 - Sagar Karmarkar - Organic DevOps - DevOps from with...
DevOpsDays Houston 2019 - Sagar Karmarkar - Organic DevOps - DevOps from with...
Working with software architects - advice to project managers
Working with software architects - advice to project managers
Similar to Introductie slides Agile Coaching door het Nederlands Instituut voor de Software Industrie
Epm seminar presentation
This document provides an overview of Enterprise Project Management (EPM). It defines EPM as taking a holistic view of all project management activities across an organization to support business goals and strategy. EPM is supported by software that provides visibility and management of all projects from demand to reporting. When selecting EPM software, organizations should consider factors like cost, features, methodology support, reporting capabilities, and maintenance/support. EPM software can help align work, enable collaboration, and provide insights to improve project execution across an enterprise.
PhuNguyeAgileStudyReport201506
This document summarizes four popular Agile methodologies: Scrum, Extreme Programming (XP), Lean, and Kanban. Scrum is an Agile methodology for project management that relies on self-organization and collective commitment. It uses sprints, daily stand-ups, and retrospectives. XP focuses on simple designs, testing, pair programming, and frequent integration. Lean promotes eliminating waste. Kanban uses visual boards and limits work-in-progress to focus on continuous flow. Agile practices can help teams achieve better results than traditional methods if they embrace the mindsets behind each methodology.
Is There Room For Project Managers In An Agile Like Environment Such As Scrum1
Agile methodologies like Scrum use iterative development between self-organizing cross-functional teams. Scrum consists of roles, ceremonies, and artifacts to facilitate incremental product development by teams of 6-7 people. While Scrum does not require project managers, it allows room for project managers by training them in Scrum practices and having them serve as Scrum masters to coordinate teams. Project managers can benefit Agile teams by learning Scrum and applying its principles without trying to change the framework.
PFCongres - Test Improvement 4 Agile
When we want to improve, for some reason we usually start to question testing. But what are the right questions to ask in an Agile context? Current TPI models have proven to be a mismatch when assessing and improving the test process in this context. So what is missing in the current models and how can we help companies improve their testing in an Agile context? It seems that it is significantly harder to describe how to become more flexible than it is to describe how to become more structured.
Jeroen will introduce a stepwise approach to improve the testing in Agile software development. The Agile Manifesto, the SCRUM process and the field experience of numerous testers form the basis for this new model. In an interactive session he will show new key areas to consider and introduce good practices that will help to improve testing in an Agile context. Some key areas of the current TPI models are changed to fit the Agile context. All other key areas are specifically aimed at the Agile context. Examples of new key areas are “People”, “Teamwork” and “Regression & E2E testing”. You will see that the development process is part of the model as well, since testing and development are completely integrated. The Agile Manifesto tells us to value people and interactions over processes and tools. Therefore the assessment and improvement model includes key areas and checkpoints that are directed at people and interactions. Last but not least, it is a test improvement model… So the model will still be focused on testing aspects. The complete model is fit for purpose and fit for Agile, in wording, terminology and the ideas behind it.
You will leave this tutorial with more knowledge on how to fit testing within Agile as well as on how to improve testing. Additionally you will take away a set of good practices that add value to your testing immediately.
Agile and-scrum
#Agile software development is based on principles de fined by the Agile Manifesto;
a disciplined project management outline that is conducive to dynamic inspection
and adaptation. Agile methods include many product development frameworks
such as Scrum and XP (eXtreme Programming) which allow for rapid delivery of
software. The Scrum framework uses simple iterative practices for team collaboration
on complex projects.
The Agile Method and AGILE ISD; how to use each to improve your training program
The document discusses how Agile development methods and AGILE instructional design can be used together to improve training programs. It describes how Agile was created to make software development more flexible and rapid, and how AGILE was created for the same reasons for instructional design. While they have different focuses, Agile on software tactics and AGILE on comprehensive learning, they are complementary. The document advocates using Agile values, Scrum framework, and iterative development with AGILE instructional design and the ADDIE model to create both formal training and structured performance support. This holistic approach aims to better link learning to job performance.
Agile and its impact to Project Management 022218.pptx
This document provides an introduction to Agile project management. It discusses the history and evolution of Agile, including the Agile Manifesto. It then describes several common Agile methodologies like Scrum, Kanban, and Extreme Programming. The document also introduces key Agile concepts like iterative development, user stories, and velocity. It discusses how project scheduling, cost estimation, and DevOps relate to Agile. Finally, it provides an overview of the Scaled Agile Framework (SAFe) for implementing Agile at an enterprise level.
Scrum
This document summarizes a presentation about using Scrum for agile software development. It begins by describing problems with the traditional waterfall method. It then discusses the origins and principles of agile methodology and the Scrum framework. Key aspects of Scrum are explained, including roles, the product backlog, sprints, and ceremonies. The presentation concludes by providing examples of how the Wisconsin Department of Public Instruction has implemented Scrum successfully and offers advice for other organizations adopting Scrum.
Professional Project Manager Should Be Proficient in Agile
This document discusses the benefits of being proficient in Agile project management. It begins with an introduction of the presenter and their experience in IT projects. It then contrasts the Waterfall and Agile approaches. Waterfall involves detailed upfront planning while Agile values adaptability and frequent delivery of working software. The document emphasizes that due to global competition, it is not enough to simply complete a project but to exceed expectations and adapt quickly. It provides examples of how companies like Nitor have seen success through Agile methods and discusses key Agile principles like small batch sizes and effective communication.
Agile and semat v0.91
Today, as always, there are many different initiatives underway to help improve the way we develop software. The most popular and prevalent of which is the Agile Movement. One of the new kids on the block is the SEMAT initiative. As with any new initiative people are struggling to see how it fits into the world and how it relates to all the other things going on. For example does it improve or replace their current ways of working. Is it something like lean that supports and furthers the aims of the Agile Movement, or is it something like waterfall planning that is in opposition to an agile approach?
The good news is that both Agile and SEMAT promote non-prescriptive value-based philosophies that encourage software development teams to select and use whatever practices best fit their context and, most importantly, continuously inspect, adapt and improve their way of working. In this keynote we will look at how these two initiatives complement one another, providing the perfect foundation for teams that want to master the art of software development.
Agile and semat v0.91
Today, as always, there are many different initiatives underway to help improve the way we develop software. The most popular and prevalent of which is the Agile Movement. One of the new kids on the block is the SEMAT initiative. As with any new initiative people are struggling to see how it fits into the world and how it relates to all the other things going on. For example does it improve or replace their current ways of working. Is it something like lean that supports and furthers the aims of the Agile Movement, or is it something like waterfall planning that is in opposition to an agile approach?
The good news is that both Agile and SEMAT promote non-prescriptive value-based philosophies that encourage software development teams to select and use whatever practices best fit their context and, most importantly, continuously inspect, adapt and improve their way of working. In this keynote we will look at how these two initiatives complement one another, providing the perfect foundation for teams that want to master the art of software development.
Improving success with Distributed Teams
This document discusses techniques for improving collaboration and success with distributed agile teams. It provides three case studies of distributed teams and the challenges they faced with collaboration. Techniques discussed to improve collaboration include establishing overlapping work hours, frequent video conferencing, pairing programmers remotely, site visits between locations, and using tools like wikis and shared backlogs to facilitate communication and coordination across sites.
Scrum basics
EHS Conducted SCRUM Overview Session for a Corporate Company in Lahore covering Basics i.e. What is Agile & Scrum, Why to use Scrum, Benefits, Values, Artifacts, Events, Scrum Teams & Roles...
The_Role_of_the_Product_Owner_in_Scrum-comparison_.pdf
The document discusses the role of the product owner in Scrum projects based on a study comparing the theoretical role to actual practices. It finds that while Scrum is commonly used for software development, product owners' understanding of their responsibilities differs between organizations and does not always align with the official Scrum method. In some cases, projects have two product owners - one for business aspects and another for technical. The study aimed to shed light on how Scrum is applied in practice regarding the product owner's role.
PMI-ACP Exam Prep Course Preview
Awarded by Project Management Institute (PMI), the Agile Certified Practitioner (PMI-ACP) credential is recognized by companies all around the world. With the education imparted in the certification training course, which is accredited by PMI.
PMI Agile Certified Practitioner certification is one of the most industry-recognized Agile project management certifications for project managers and project practitioners all across the world.
To know more about PMI Agile Certified Practitioner Certification trainings worldwide, please contact us at -
Email :support@invensislearning.com
Phone - US +1-910-726-3695,
Website : https://www.invensislearning.com
AGILE SPM_Week 1.pptx
This document provides an overview of project management, agile software development, and Scrum. It discusses the differences between traditional project management and agile approaches. Key points include:
- Agile methods like Scrum aim to deliver working software frequently through short iterations, collaboration, and responding to change over rigid plans.
- Scrum uses short "sprints" to iteratively develop products in an adaptive manner, emphasizing working software over documentation.
- By developing in rapid iterations with customer feedback, Scrum helps deliver large solutions more quickly than traditional "waterfall" approaches.
scrum-talk
Nopparat and Samatchaya gave a presentation on Scrum and Agile. They discussed key concepts like the Agile Manifesto, Scrum roles, the Scrum process, and their experiences implementing Scrum. As an Agile coach, Nopparat helps teams build an environment for self-organization and continuous improvement through training, coaching, and ensuring stakeholder support for Agile goals. The presentation included games to illustrate Scrum concepts and a case study on challenges of creating an Agile culture.
software engineering agile development notes.pptx
Extreme Programming (XP) is an agile software development methodology that focuses on customer satisfaction and rapid feedback. It utilizes practices like pair programming, simple design, small releases, and testing. Scrum is another agile methodology using a product backlog, sprints, and daily stand-ups. Development teams are self-organizing and work in sprints to deliver working software. Other methodologies discussed include Dynamic Systems Development Method (DSDM), Feature-Driven Development (FDD), Crystal, and Lean Software Development (LSD).
Agile project management using scrum
Overview of Agile Project Management Using SCRUM and How to Pass PMI-ACP Certification Exam in a Month
PMINEO_2013_04_Agile_Panel
The document summarizes an event where a panel of experts discussed their experiences with adopting Agile methodologies. The panelists represented different industries and levels of Agile experience. They discussed topics such as how to get started with Agile, best practices, and challenges to consider. The event also provided information on Scrum processes, a combination approach to Agile and waterfall methods, and PMI certification in Agile practices. The panelists then answered questions from the audience.
Similar to Introductie slides Agile Coaching door het Nederlands Instituut voor de Software Industrie (20)
Is There Room For Project Managers In An Agile Like Environment Such As Scrum1
Is There Room For Project Managers In An Agile Like Environment Such As Scrum1
The Agile Method and AGILE ISD; how to use each to improve your training program
The Agile Method and AGILE ISD; how to use each to improve your training program
Agile and its impact to Project Management 022218.pptx
Agile and its impact to Project Management 022218.pptx
Professional Project Manager Should Be Proficient in Agile
Professional Project Manager Should Be Proficient in Agile
The_Role_of_the_Product_Owner_in_Scrum-comparison_.pdf
The_Role_of_the_Product_Owner_in_Scrum-comparison_.pdf
Recently uploaded
Modelling Up - DDDEurope 2024 - Amsterdam
What to do when you have a perfect model for your software but you are constrained by an imperfect business model?
This talk explores the challenges of bringing modelling rigour to the business and strategy levels, and talking to your non-technical counterparts in the process.
Oracle 23c New Features For DBAs and Developers.pptx
Most important New features of Oracle 23c for DBAs and Developers. You can get more idea from my youtube channel video from https://youtu.be/XvL5WtaC20A
Webinar On-Demand: Using Flutter for Embedded
Flutter is a popular open source, cross-platform framework developed by Google. In this webinar we'll explore Flutter and its architecture, delve into the Flutter Embedder and Flutter’s Dart language, discover how to leverage Flutter for embedded device development, learn about Automotive Grade Linux (AGL) and its consortium and understand the rationale behind AGL's choice of Flutter for next-gen IVI systems. Don’t miss this opportunity to discover whether Flutter is right for your project.
Enums On Steroids - let's look at sealed classes !
These are slides for my session"Enums On Steroids - let's look at sealed classes !" - delivered among others, on Devoxx UK 2024 conference
Preparing Non - Technical Founders for Engaging a Tech Agency
Preparing non-technical founders before engaging a tech agency is crucial for the success of their projects. It starts with clearly defining their vision and goals, conducting thorough market research, and gaining a basic understanding of relevant technologies. Setting realistic expectations and preparing a detailed project brief are essential steps. Founders should select a tech agency with a proven track record and establish clear communication channels. Additionally, addressing legal and contractual considerations and planning for post-launch support are vital to ensure a smooth and successful collaboration. This preparation empowers non-technical founders to effectively communicate their needs and work seamlessly with their chosen tech agency.Visit our site to get more details about this. Contact us today www.ishtechnologies.com.au
What’s New in Odoo 17 – A Complete Roadmap
Odoo releases a new update every year. The latest version, Odoo 17, came out in October 2023. It brought many improvements to the user interface and user experience, along with new features in modules like accounting, marketing, manufacturing, websites, and more.
The Odoo 17 update has been a hot topic among startups, mid-sized businesses, large enterprises, and Odoo developers aiming to grow their businesses. Since it is now already the first quarter of 2024, you must have a clear idea of what Odoo 17 entails and what it can offer your business if you are still not aware of it.
This blog covers the features and functionalities. Explore the entire blog and get in touch with expert Odoo ERP consultants to leverage Odoo 17 and its features for your business too.
An Overview of Odoo ERP
Odoo ERP was first released as OpenERP software in February 2005. It is a suite of business applications used for ERP, CRM, eCommerce, websites, and project management. Ten years ago, the Odoo Enterprise edition was launched to help fund the Odoo Community version.
When you compare Odoo Community and Enterprise, the Enterprise edition offers exclusive features like mobile app access, Odoo Studio customisation, Odoo hosting, and unlimited functional support.
Today, Odoo is a well-known name used by companies of all sizes across various industries, including manufacturing, retail, accounting, marketing, healthcare, IT consulting, and R&D.
The latest version, Odoo 17, has been available since October 2023. Key highlights of this update include:
Enhanced user experience with improvements to the command bar, faster backend page loading, and multiple dashboard views.
Instant report generation, credit limit alerts for sales and invoices, separate OCR settings for invoice creation, and an auto-complete feature for forms in the accounting module.
Improved image handling and global attribute changes for mailing lists in email marketing.
A default auto-signature option and a refuse-to-sign option in HR modules.
Options to divide and merge manufacturing orders, track the status of manufacturing orders, and more in the MRP module.
Dark mode in Odoo 17.
Now that the Odoo 17 announcement is official, let’s look at what’s new in Odoo 17!
What is Odoo ERP 17?
Odoo 17 is the latest version of one of the world’s leading open-source enterprise ERPs. This version has come up with significant improvements explained here in this blog. Also, this new version aims to introduce features that enhance time-saving, efficiency, and productivity for users across various organisations.
Odoo 17, released at the Odoo Experience 2023, brought notable improvements to the user interface and added new functionalities with enhancements in performance, accessibility, data analysis, and management, further expanding its reach in the market.
Malibou Pitch Deck For Its €3M Seed Round
French start-up Malibou raised a €3 million Seed Round to develop its payroll and human resources
management platform for VSEs and SMEs. The financing round was led by investors Breega, Y Combinator, and FCVC.
ppt on the brain chip neuralink.pptx
A neural network is a machine learning program, or model, that makes decisions in a manner similar to the human brain, by using processes that mimic the way biological neurons work together to identify phenomena, weigh options and arrive at conclusions.
Why Apache Kafka Clusters Are Like Galaxies (And Other Cosmic Kafka Quandarie...
Closing talk for the Performance Engineering track at Community Over Code EU (Bratislava, Slovakia, June 5 2024) https://eu.communityovercode.org/sessions/2024/why-apache-kafka-clusters-are-like-galaxies-and-other-cosmic-kafka-quandaries-explored/ Instaclustr (now part of NetApp) manages 100s of Apache Kafka clusters of many different sizes, for a variety of use cases and customers. For the last 7 years I’ve been focused outwardly on exploring Kafka application development challenges, but recently I decided to look inward and see what I could discover about the performance, scalability and resource characteristics of the Kafka clusters themselves. Using a suite of Performance Engineering techniques, I will reveal some surprising discoveries about cosmic Kafka mysteries in our data centres, related to: cluster sizes and distribution (using Zipf’s Law), horizontal vs. vertical scalability, and predicting Kafka performance using metrics, modelling and regression techniques. These insights are relevant to Kafka developers and operators.
ACE - Team 24 Wrapup event at ahmedabad.
Atlassian Team 24 event wrap-up Ahmedabad. Recap of Atlassian team24 event.
Microservice Teams - How the cloud changes the way we work
A lot of technical challenges and complexity come with building a cloud-native and distributed architecture. The way we develop backend software has fundamentally changed in the last ten years. Managing a microservices architecture demands a lot of us to ensure observability and operational resiliency. But did you also change the way you run your development teams?
Sven will talk about Atlassian’s journey from a monolith to a multi-tenanted architecture and how it affected the way the engineering teams work. You will learn how we shifted to service ownership, moved to more autonomous teams (and its challenges), and established platform and enablement teams.
All you need to know about Spring Boot and GraalVM
All you need to know about Spring Boot and GraalVM 🐰
Safelyio Toolbox Talk Softwate & App (How To Digitize Safety Meetings)
Consistent toolbox talks are critical for maintaining workplace safety, as they provide regular opportunities to address specific hazards and reinforce safe practices.
These brief, focused sessions ensure that safety is a continual conversation rather than a one-time event, which helps keep safety protocols fresh in employees' minds. Studies have shown that shorter, more frequent training sessions are more effective for retention and behavior change compared to longer, infrequent sessions.
Engaging workers regularly, toolbox talks promote a culture of safety, empower employees to voice concerns, and ultimately reduce the likelihood of accidents and injuries on site.
The traditional method of conducting safety talks with paper documents and lengthy meetings is not only time-consuming but also less effective. Manual tracking of attendance and compliance is prone to errors and inconsistencies, leading to gaps in safety communication and potential non-compliance with OSHA regulations. Switching to a digital solution like Safelyio offers significant advantages.
Safelyio automates the delivery and documentation of safety talks, ensuring consistency and accessibility. The microlearning approach breaks down complex safety protocols into manageable, bite-sized pieces, making it easier for employees to absorb and retain information.
This method minimizes disruptions to work schedules, eliminates the hassle of paperwork, and ensures that all safety communications are tracked and recorded accurately. Ultimately, using a digital platform like Safelyio enhances engagement, compliance, and overall safety performance on site. https://safelyio.com/
一比一原版(UMN毕业证)明尼苏达大学毕业证如何办理
UMN硕士毕业证成绩单【微信95270640】购买（明尼苏达大学毕业证成绩单硕士学历）Q微信95270640代办UMN学历认证留信网伪造明尼苏达大学学位证书精仿明尼苏达大学本科/硕士文凭证书补办明尼苏达大学 diplomaoffer,Transcript购买明尼苏达大学毕业证成绩单购买UMN假毕业证学位证书购买伪造明尼苏达大学文凭证书学位证书,专业办理雅思、托福成绩单，学生ID卡，在读证明，海外各大学offer录取通知书，毕业证书，成绩单，文凭等材料:1:1完美还原毕业证、offer录取通知书、学生卡等各种在读或毕业材料的防伪工艺（包括 烫金、烫银、钢印、底纹、凹凸版、水印、防伪光标、热敏防伪、文字图案浮雕，激光镭射，紫外荧光，温感光标）学校原版上有的工艺我们一样不会少，不论是老版本还是最新版本，都能保证最高程度还原，力争完美以求让所有同学都能享受到完美的品质服务。
#毕业证成绩单 #毕业証 #成绩单 #學生卡 #OFFER录取通知书 #雅思#托福等……
国外大学明尼苏达大学明尼苏达大学毕业证offer制作方法（一对一专业服务）
1客户提供办理信息：姓名生日专业学位毕业时间等（如信息不确定可以咨询顾问：我们有专业老师帮你查询）；
2开始安排制作毕业证成绩单电子图；
3毕业证成绩单电子版做好以后发送给您确认；
4毕业证成绩单电子版您确认信息无误之后安排制作成品；
5成品做好拍照或者视频给您确认；
6快递给客户（国内顺丰国外DHLUPS等快读邮寄）
— — 制作工艺 【高仿真】— —
凭借多年的制作经验本公司制作明尼苏达大学明尼苏达大学毕业证offer《激光》《水印》《钢印》《烫金》《紫外线》凹凸版uv版等防伪技术一流高精仿度几乎跟学校100%相同！让您绝对满意。
— — -公司理念 【诚信为主】— — —
我們以質量求生存.以服务求发展有雄厚的实力专业的团队咨询顾问为您细心解答可详谈是真是假眼见为实让您真正放心平凡人生,尽我所能助您一臂之力让我們携手圆您梦想!
此贴长年有效【贴心专线/微-信: 95270640】敬请保留此联系方式以备用！如有不在线请给我们留言！我们将在第一时间给您回复!上散发着一抹抹的光晕而这每处自然形成的细节融合在一起浑然天成的美实在令人心生愉悦小道的周边无秩序的生长着几株艳丽的野花红的粉的紫的虽混乱无章却给这幅美景更增添一份性感夹杂着一份纯洁的妖娆毫无违和感实在给人带来一份悠然幸福的心情如果说现在的审美已经断然拒绝了无声的话那么在树林间飞掠而过的小鸟叽叽咋咋的叫声是否就是这最后的点睛之笔悠然走在林间的小路上宁静与清香一丝丝的盛夏气息吸入身体昔日生活里的繁忙多
UI5con 2024 - Keynote: Latest News about UI5 and it’s Ecosystem
Learn about the latest innovations in and around OpenUI5/SAPUI5: UI5 Tooling, UI5 linter, UI5 Web Components, Web Components Integration, UI5 2.x, UI5 GenAI.
Recording:
https://www.youtube.com/live/MSdGLG2zLy8?si=INxBHTqkwHhxV5Ta&t=0
14 th Edition of International conference on computer vision
About the event
14th Edition of International conference on computer vision
Computer conferences organized by ScienceFather group. ScienceFather takes the privilege to invite speakers participants students delegates and exhibitors from across the globe to its International Conference on computer conferences to be held in the Various Beautiful cites of the world. computer conferences are a discussion of common Inventions-related issues and additionally trade information share proof thoughts and insight into advanced developments in the science inventions service system. New technology may create many materials and devices with a vast range of applications such as in Science medicine electronics biomaterials energy production and consumer products.
Nomination are Open!! Don't Miss it
Visit: computer.scifat.com
Award Nomination: https://x-i.me/ishnom
Conference Submission: https://x-i.me/anicon
For Enquiry: Computer@scifat.com
Baha Majid WCA4Z IBM Z Customer Council Boston June 2024.pdf
IBM watsonx Code Assistant for Z, our latest Generative AI-assisted mainframe application modernization solution. Mainframe (IBM Z) application modernization is a topic that every mainframe client is addressing to various degrees today, driven largely from digital transformation. With generative AI comes the opportunity to reimagine the mainframe application modernization experience. Infusing generative AI will enable speed and trust, help de-risk, and lower total costs associated with heavy-lifting application modernization initiatives. This document provides an overview of the IBM watsonx Code Assistant for Z which uses the power of generative AI to make it easier for developers to selectively modernize COBOL business services while maintaining mainframe qualities of service.
Kubernetes at Scale: Going Multi-Cluster with Istio
Divine Odazie and Jubril Oyetunji share tips on Going Multi-Cluster with Istio Service Mesh at DevOpsDays Houston.
The Rising Future of CPaaS in the Middle East 2024
Explore "The Rising Future of CPaaS in the Middle East in 2024" with this comprehensive PPT presentation. Discover how Communication Platforms as a Service (CPaaS) is transforming communication across various sectors in the Middle East.
8 Best Automated Android App Testing Tool and Framework in 2024.pdf
Regarding mobile operating systems, two major players dominate our thoughts: Android and iPhone. With Android leading the market, software development companies are focused on delivering apps compatible with this OS. Ensuring an app's functionality across various Android devices, OS versions, and hardware specifications is critical, making Android app testing essential.
Recently uploaded (20)
Oracle 23c New Features For DBAs and Developers.pptx
Oracle 23c New Features For DBAs and Developers.pptx
Enums On Steroids - let's look at sealed classes !
Enums On Steroids - let's look at sealed classes !
Preparing Non - Technical Founders for Engaging a Tech Agency
Preparing Non - Technical Founders for Engaging a Tech Agency
Why Apache Kafka Clusters Are Like Galaxies (And Other Cosmic Kafka Quandarie...
Why Apache Kafka Clusters Are Like Galaxies (And Other Cosmic Kafka Quandarie...
Microservice Teams - How the cloud changes the way we work
Microservice Teams - How the cloud changes the way we work
All you need to know about Spring Boot and GraalVM
All you need to know about Spring Boot and GraalVM
Safelyio Toolbox Talk Softwate & App (How To Digitize Safety Meetings)
Safelyio Toolbox Talk Softwate & App (How To Digitize Safety Meetings)
UI5con 2024 - Keynote: Latest News about UI5 and it’s Ecosystem
UI5con 2024 - Keynote: Latest News about UI5 and it’s Ecosystem
14 th Edition of International conference on computer vision
14 th Edition of International conference on computer vision
Baha Majid WCA4Z IBM Z Customer Council Boston June 2024.pdf
Baha Majid WCA4Z IBM Z Customer Council Boston June 2024.pdf
Kubernetes at Scale: Going Multi-Cluster with Istio
Kubernetes at Scale: Going Multi-Cluster with Istio
The Rising Future of CPaaS in the Middle East 2024
The Rising Future of CPaaS in the Middle East 2024
8 Best Automated Android App Testing Tool and Framework in 2024.pdf
8 Best Automated Android App Testing Tool and Framework in 2024.pdf
Introductie slides Agile Coaching door het Nederlands Instituut voor de Software Industrie
- 1. 1 Scrum Master training (PSM1) Agile Culture: “We are uncovering better ways of developing software by doing it and helping others do it.”, Agile Manifesto Session 1: Introduction 2017 Q2-Q3 Jan Wognum
- 2. Scrum Master training (PSM1) • Introduction Agile Scrum Coaching • Organized by: – Utrecht University - www.uu.nl – Netherlands Institute for the Software Industry - nisi.nl • In collaboration with: – NederlandICT - www.nederlandict.nl – Software VOC – Scrum.org • Powered by: – Search4Solutions – www.search4solutions.nl 2
- 3. • Course is part of the Netherlands Institute for the Software Industry • NISI is a spin-off of Utrecht University • Mission: provide (scientific) knowledge in practical courses to advance the software industry in the Netherlands • With the results we fund new scientific research 3 NISI
- 4. 4 NISI core team Dr. Jan Vlietland has a doctorate in Agile eco- systems, is co-founder and head of NISI, and has been working in the software industry for over 20 years. Prof. Sjaak Brinkkemper is head of the faculty of Information and Computer Science and professor at Utrecht University, and NISI initiator. Dr. Slinger Jansen is assistant professor at the faculty of Information and Computer Science of Utrecht University, and heads research at large software companies. Garm Lucassen performs PhD research about User Stories.
- 5. 5 Practice Agile Scrum Coaching • Sjaak Brinkkemper • Garm Lucassen • Fabiano Dalpiaz • Slinger Jansen • Maikel Meeuwse • Jan Vlietland • Tiemen Schut • Jan Wognum 5
- 6. • Theme: Agility of software companies • Research themes –Agility & Agile scaling –Continuous Delivery –Software & Social ecosystems 6 Research Agenda
- 7. Course Objectives • Help companies to cope with fast moving markets • Advance participants knowledge about Agile Scrum • Help participants to implement Agility in their organizations • Knowledge sharing between Agile Scrum Coaches of different companies 7
- 8. Possible routes Day part 1-3 • PSM1 (Scrum Master) track – PSM1 (Or similar training is expected as basis for Agile coach training – PSM1 examination training (Day part 3) Daypart 4 up to 8 • Agile Scrum Coaching Day part PSM1 training Certification PSM1 Agile Coaching 1-8 4-8
- 9. PSM1 – SCRUM MASTER TRAINING Dayparts 1-3: Scrum Master training
- 11. Agenda dayparts 1-3 • Exponential change • Unpredictability • The Agile Philosophy • The Scrum framework • Waterfall versus Scrum • Scrum roles • The Scrum process • Complexity & Agile Leadership & Management styles • Scrum Master role • Scrum Master characteristics • Role Scrum Master linked to the Scrum events 11
- 12. Het Ontstaan van agile werken en Agile principes 12
- 13. 13 Agile Manifesto Source: http://agilemanifesto.org Manifesto for Agile Software Development We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more
- 17. Agile/Scrum Process DAILY SCRUM / DAILY WORK SPRINT REVIEW SPRINT RETROSPECTIVE BACKLOG REFINEMENT SPRINT PLANNING MEETING • Business case & funding • Contractual agreement • Vision • Initial product backlog • Initial release plan • Stakeholder buy-in • Assemble team SPRINT BACKLOG SPRINT BACKLOG BURNDOWN IMPEDI- MENT LIST PRODUCT BACKLOG PRODUCT BACKLOG BURNDOWN PREPARATION SCRUM- PROCESS RELEASE n SCRUM MASTER PRODUCT OWNER DEVELOP- MENT TEAM USERS STAKE- HOLDERS SCRUM ARTIFACTS STAKE- HOLDERS Definition of Done
- 18. • A stable team (Tuckman) • 6 +/- 3 members (Wittenberg) • Full-time utilization • Multi-disciplinary • Shared focused Goal • Transparent execution • Delivers each 2-4 weeks • Pro-active and guts • Respect and trust • Emotionally safe 18 Agile/Scrum framework
- 19. PSM1 – CERTIFICATION TRAINING Daypart 3: Certification training (PSM1 – Scrum.Org)
- 20. Wil je de rest van de Agile Scrum Coaching slides ontvangen? Meld je dan aan bij het Nederlands Instituut voor de Software Industrie! 20 Aanmelden