This rubric evaluates Popplet projects on content, technology skills, and collaboration. For content, students must include key facts, issues, justification, and decisions to receive full points. For technology, students are scored on layout, use of multimedia, and organization of information. Regarding collaboration, students receive higher marks for contributing equally from multiple devices and demonstrating a thorough understanding of the topic.
The document provides evaluation criteria for assessing student work on saving coral reefs across six areas: challenges, underlying problem, solutions, criteria/analysis of solutions, action plan, and collaboration. The criteria are rated on a scale from unsatisfactory to advanced. Proficient performance involves including key elements like what/why for challenges and who/what/how/why for solutions. Advanced performance provides additional details, research support, and goes beyond expectations.
The document introduces Ron Guttman as a speaker, trainer, and entertainer with over 35 years of experience in business and 20 years as a magician. It provides an overview of Ron's background and expertise in areas such as project management, critical thinking, memory techniques, team building, and presentation skills. The document also describes some of Ron's entertainment offerings, which incorporate mentalism, illusions, and audience participation.
This document discusses the challenges of adopting DevOps practices and containerization with Docker. It notes that while Docker and containers are useful technologies, they often recreate issues if culture and collaboration between development and operations teams does not change. Several "un" problems are outlined, such as code that is unbuildable, unpackageable, undeployable etc. due to a lack of automation, configuration management, or operations involvement in the development process. The document stresses that tools are not the most important factor - it is about cultural change, collaboration, shared goals and ensuring development outputs can be supported in production environments.
Turning an idea into a profitable finished productHani Gamal
Turning an idea into a profitable finished product lecture's presentation pitched at Moataz Al-Alfi Hall of the AUC new Cairo Campus to the favor of Fekrety EIP competition, 3rd of July, 2012
The document discusses tools and techniques for managing remote projects. It recommends using Scrum techniques like daily stand-ups and weekly planning to keep communication lines open. It also provides examples of project management tools like Google Docs, Basecamp, Pivotal Tracker, and Unfuddle and when each may be best suited. The document concludes with an example weekly schedule for a project manager to tie all the communication and tools together.
The document provides best practices for developing an app or website. It recommends starting with wireframing sketches and researching functional comparables. When ready for development, options include hiring staff, finding a technical co-founder, outsourcing work, or learning to code yourself. Managing the development requires finding top talent, setting concrete goals and timelines, and maintaining clear communication through daily meetings and documentation. The key is focusing on an easy to use product that solves users' needs.
Kris Buytaert discusses his transition from developer to operations engineer to consultant. He advocates for starting DevOps transformations with operations skills and involvement to improve success rates and adoption. Buytaert outlines four common transition cases for startups and multinationals, highlighting the importance of cultural and skills alignment between development and operations.
The document provides evaluation criteria for assessing student work on saving coral reefs across six areas: challenges, underlying problem, solutions, criteria/analysis of solutions, action plan, and collaboration. The criteria are rated on a scale from unsatisfactory to advanced. Proficient performance involves including key elements like what/why for challenges and who/what/how/why for solutions. Advanced performance provides additional details, research support, and goes beyond expectations.
The document introduces Ron Guttman as a speaker, trainer, and entertainer with over 35 years of experience in business and 20 years as a magician. It provides an overview of Ron's background and expertise in areas such as project management, critical thinking, memory techniques, team building, and presentation skills. The document also describes some of Ron's entertainment offerings, which incorporate mentalism, illusions, and audience participation.
This document discusses the challenges of adopting DevOps practices and containerization with Docker. It notes that while Docker and containers are useful technologies, they often recreate issues if culture and collaboration between development and operations teams does not change. Several "un" problems are outlined, such as code that is unbuildable, unpackageable, undeployable etc. due to a lack of automation, configuration management, or operations involvement in the development process. The document stresses that tools are not the most important factor - it is about cultural change, collaboration, shared goals and ensuring development outputs can be supported in production environments.
Turning an idea into a profitable finished productHani Gamal
Turning an idea into a profitable finished product lecture's presentation pitched at Moataz Al-Alfi Hall of the AUC new Cairo Campus to the favor of Fekrety EIP competition, 3rd of July, 2012
The document discusses tools and techniques for managing remote projects. It recommends using Scrum techniques like daily stand-ups and weekly planning to keep communication lines open. It also provides examples of project management tools like Google Docs, Basecamp, Pivotal Tracker, and Unfuddle and when each may be best suited. The document concludes with an example weekly schedule for a project manager to tie all the communication and tools together.
The document provides best practices for developing an app or website. It recommends starting with wireframing sketches and researching functional comparables. When ready for development, options include hiring staff, finding a technical co-founder, outsourcing work, or learning to code yourself. Managing the development requires finding top talent, setting concrete goals and timelines, and maintaining clear communication through daily meetings and documentation. The key is focusing on an easy to use product that solves users' needs.
Kris Buytaert discusses his transition from developer to operations engineer to consultant. He advocates for starting DevOps transformations with operations skills and involvement to improve success rates and adoption. Buytaert outlines four common transition cases for startups and multinationals, highlighting the importance of cultural and skills alignment between development and operations.
Devops, The future is here, it's just not evenly distributedKris Buytaert
Devops aims to break down barriers between development and operations teams through principles like continuous integration, automation, shared infrastructure access, and cross-functional teams. It advocates automating processes from building to deploying to testing in order to enable continuous delivery of new features in a secure and reliable manner. This helps improve communication between teams and allows organizations to get features to users faster while increasing stability, security, and customer satisfaction. Achieving devops culture and practices requires patience, improving collaboration, building trust between teams, and automating as many processes as possible.
7 Tools for your Puppetized Devops stackKris Buytaert
7 Tools for your puppetized devops stack discusses Puppet, Jenkins, fpm, Logstash, Graphite, the Marionette Collective, and Vagrant as tools for a DevOps stack. Puppet is used for configuration management. Jenkins is used for continuous integration. fpm creates packages. Logstash handles log collection and analysis. Graphite provides metrics graphing. The Marionette Collective provides distributed SSH commands. And Vagrant allows consistent environments. The talk emphasizes culture, automation, measurement, and sharing as key DevOps principles.
Automating MySQL operations with PuppetKris Buytaert
This document summarizes a presentation about automating MySQL operations with Puppet. It discusses:
- Why automation is important for consistency, security, and disaster recovery. Manual changes can introduce bugs and inconsistencies.
- Puppet is an open source configuration management tool that can be used to automate MySQL configuration, users, backups, replication, and high availability clustering with tools like Corosync/Pacemaker.
- Puppet modules define the desired state and Puppet ensures the actual state matches by making necessary changes. This provides auditability and change tracking through version control of Puppet code.
PuppetConf 2016: Successful Puppet Implementation in Large Organizations – Ja...Puppet
Here are the slides from James Sweeny's PuppetConf 2016 presentation called Successful Puppet Implementation in Large Organizations. Watch the videos at https://www.youtube.com/playlist?list=PLV86BgbREluVjwwt-9UL8u2Uy8xnzpIqa
This document discusses the evolution of devops concepts and tools over the past 10 years since the devops movement began. It notes that early topics focused on culture, automation and monitoring tools. Over time, tooling became more advanced but also more complex. Culture remains important but large enterprises still struggle with devops adoption due to broken cultures. New technologies like containers have created new challenges. Ultimately, devops is about change and people, not just tools. While progress has been made, there is still work to be done to fully implement devops principles and fix issues around tool hype, broken cultures and burnout.
PlatinumGames and Hansoft - the Road to AgilityHansoft AB
Presentation at GDC 2015 by Creative Producer Jean Pierre Kellams at PlatinumGames and Senior Coach Jon Leslie at Hansoft. Read more: ow.ly/JwCWc
PlatinumGames and Hansoft - the Road to Agility
More and more teams are moving towards agile or hybrids of agile and traditional methods. Managing the transition can be a challenge and it is important to align your teams, use the right metrics and organize the work in a good way in order to get studio wide buy-in and a satisfying result. In this session, Jean Pierre Kellams, Creative Producer of Scalebound from Osaka, Japan-based developer PlatinumGames, creator of titles such as Bayonetta, and Jon Leslie from Hansoft will tell you how the team at PlatinumGames made the switch. They will take you through the process, starting with the strengths and weaknesses that brought about the change, the actual transition, and the successes and failures that led to the realization that what seems ideal isn't always the case.
The document provides an overview of concepts related to breaking down work in an agile environment. It defines key terms like initiatives, epics, features, releases, sprints, and stories. It describes the process of decomposing work from high-level portfolio items and products down to lower levels like epics, features, and stories. It explains how these different levels relate to each other and how planning is done at different levels from strategic to tactical. It also discusses how these concepts are represented in the Version One tool.
The document provides an OSS checklist for evaluating the sc2reader project based on best practices from "Producing Open Source Software". It evaluates sc2reader across several categories such as name, mission statement, licensing, downloads, and documentation. While sc2reader meets many criteria, it is lacking in clearly communicating development status, guidelines for reporting bugs/submitting patches, and comprehensive documentation. The checklist raises questions about its usefulness and whether any tools could help projects improve in these areas.
70% of significant change/ transformation efforts fail. This presentation shows some key points of attention, both from the hardware as well as (and especially) from the software side. Focus is on leveraging intrinsic motivation throughout the organisation during change, using concepts such as FLOW and gamification as enabler.
The document provides an overview of the Power Steering project tracking tool used by the National Guard for continuous process improvement projects. It describes how to access and navigate Power Steering, the roles and responsibilities of Black Belts in using it to track project progress, and how to invite new users. The learning objectives are to understand how to use Power Steering to navigate, track projects, and share best practices.
The document provides guidance on using the Power Steering project tracking tool. It outlines how to access Power Steering, navigate the interface, update user profiles, and invite new users. Power Steering is used to track Department of Defense continuous process improvement projects, store associated templates and tools, and share best practices between projects. National Guard students who attend Black Belt training will receive login credentials to enter project details and updates.
Marketing the Agile Way - Applying Scrum Outside of DevelomentKirsten Knipp
Using agile development methodologies in marketing is becoming more prevalent. This presentation defines scrum and describes how it's used in practice at HubSpot to gain greater transparency, manage prioritization better and achieve more predictability in our marketing efforts.
Using agile development methodologies in marketing is becoming more prevalent. This presentation defines scrum and describes how it's used in practice at HubSpot to gain greater transparency, manage prioritization better and achieve more predictability in our marketing efforts.
Scaling - Getting Bigger is Not the AnswerDon Patti
Ask someone why they want to scale and their response is often, "So we can continue practicing agile as we grow bigger." While the pursuit of agility is a noble one, most often the pursuit of "bigness" is not. But what is?
In this talk, David Bulkin and Donald Patti will introduce attendees to three of the most popular scaling frameworks -- Scrum@Scale, LeSS and SAFe -- comparing the qualities of each. In addition, they'll explain what organizations looking to scale SHOULD pursue as they scale.
The document discusses problems with typical development approaches and how agile methodologies address these issues through feedback loops. Typical development relies on upfront planning that becomes outdated and does not integrate customer feedback well. Agile uses short iterations, user stories to track business value, and continuous feedback to allow plans to change quickly in response to new information. This helps ensure development stays aligned with customer needs and allows for incremental delivery of value.
The document discusses the needs for open and appropriate technology documentation. It notes that technology documentation needs to be tailored for different user groups, from teachers and developers to implementers, and that these groups have varying resources and needs. The document examines examples of technology documentation and identifies shortcomings. It emphasizes that documentors need access to all source materials to create customizable documentation. The key is remembering that the intended users, not the inventors, should be the top priority in documentation.
The power to Say NO - Using Scrum in a BAU TeamMia Horrigan
Using Scrum to empower your team during BAU (business as usual) development and maintenance. presentation at the #LAST Conference Melbourne 27 Jul 2012
#LAST (Lean, Agile, Systems Thinking)
Continuous Infrastructure First Ignite EditionKris Buytaert
This document discusses different approaches to implementing continuous infrastructure and collaboration between development and operations teams. It argues that starting with operations automating their own workflows first allows them to understand the tools and processes before enforcing them on developers, prevents technical debt, and enables delivery and provisioning from the start. Having dedicated operations resources focus on automation leads to improved collaboration and quality over having "devops" teams dictate tools to operations.
DevOps Days Kyiv 2019 -- continuous Infrafirstructure First //Kris buytaertMykola Marzhan
This document discusses different approaches to implementing continuous infrastructure and collaboration between development and operations teams. It argues that starting with operations automating their own workflows first allows them to understand the tools and processes before enforcing them on developers, prevents technical debt, and enables delivery and provisioning from the start. Getting operations involved early through dedicating resources to infrastructure as code avoids prolonged periods where operations teams are playing catch up or acting as heroes.
Devops, The future is here, it's just not evenly distributedKris Buytaert
Devops aims to break down barriers between development and operations teams through principles like continuous integration, automation, shared infrastructure access, and cross-functional teams. It advocates automating processes from building to deploying to testing in order to enable continuous delivery of new features in a secure and reliable manner. This helps improve communication between teams and allows organizations to get features to users faster while increasing stability, security, and customer satisfaction. Achieving devops culture and practices requires patience, improving collaboration, building trust between teams, and automating as many processes as possible.
7 Tools for your Puppetized Devops stackKris Buytaert
7 Tools for your puppetized devops stack discusses Puppet, Jenkins, fpm, Logstash, Graphite, the Marionette Collective, and Vagrant as tools for a DevOps stack. Puppet is used for configuration management. Jenkins is used for continuous integration. fpm creates packages. Logstash handles log collection and analysis. Graphite provides metrics graphing. The Marionette Collective provides distributed SSH commands. And Vagrant allows consistent environments. The talk emphasizes culture, automation, measurement, and sharing as key DevOps principles.
Automating MySQL operations with PuppetKris Buytaert
This document summarizes a presentation about automating MySQL operations with Puppet. It discusses:
- Why automation is important for consistency, security, and disaster recovery. Manual changes can introduce bugs and inconsistencies.
- Puppet is an open source configuration management tool that can be used to automate MySQL configuration, users, backups, replication, and high availability clustering with tools like Corosync/Pacemaker.
- Puppet modules define the desired state and Puppet ensures the actual state matches by making necessary changes. This provides auditability and change tracking through version control of Puppet code.
PuppetConf 2016: Successful Puppet Implementation in Large Organizations – Ja...Puppet
Here are the slides from James Sweeny's PuppetConf 2016 presentation called Successful Puppet Implementation in Large Organizations. Watch the videos at https://www.youtube.com/playlist?list=PLV86BgbREluVjwwt-9UL8u2Uy8xnzpIqa
This document discusses the evolution of devops concepts and tools over the past 10 years since the devops movement began. It notes that early topics focused on culture, automation and monitoring tools. Over time, tooling became more advanced but also more complex. Culture remains important but large enterprises still struggle with devops adoption due to broken cultures. New technologies like containers have created new challenges. Ultimately, devops is about change and people, not just tools. While progress has been made, there is still work to be done to fully implement devops principles and fix issues around tool hype, broken cultures and burnout.
PlatinumGames and Hansoft - the Road to AgilityHansoft AB
Presentation at GDC 2015 by Creative Producer Jean Pierre Kellams at PlatinumGames and Senior Coach Jon Leslie at Hansoft. Read more: ow.ly/JwCWc
PlatinumGames and Hansoft - the Road to Agility
More and more teams are moving towards agile or hybrids of agile and traditional methods. Managing the transition can be a challenge and it is important to align your teams, use the right metrics and organize the work in a good way in order to get studio wide buy-in and a satisfying result. In this session, Jean Pierre Kellams, Creative Producer of Scalebound from Osaka, Japan-based developer PlatinumGames, creator of titles such as Bayonetta, and Jon Leslie from Hansoft will tell you how the team at PlatinumGames made the switch. They will take you through the process, starting with the strengths and weaknesses that brought about the change, the actual transition, and the successes and failures that led to the realization that what seems ideal isn't always the case.
The document provides an overview of concepts related to breaking down work in an agile environment. It defines key terms like initiatives, epics, features, releases, sprints, and stories. It describes the process of decomposing work from high-level portfolio items and products down to lower levels like epics, features, and stories. It explains how these different levels relate to each other and how planning is done at different levels from strategic to tactical. It also discusses how these concepts are represented in the Version One tool.
The document provides an OSS checklist for evaluating the sc2reader project based on best practices from "Producing Open Source Software". It evaluates sc2reader across several categories such as name, mission statement, licensing, downloads, and documentation. While sc2reader meets many criteria, it is lacking in clearly communicating development status, guidelines for reporting bugs/submitting patches, and comprehensive documentation. The checklist raises questions about its usefulness and whether any tools could help projects improve in these areas.
70% of significant change/ transformation efforts fail. This presentation shows some key points of attention, both from the hardware as well as (and especially) from the software side. Focus is on leveraging intrinsic motivation throughout the organisation during change, using concepts such as FLOW and gamification as enabler.
The document provides an overview of the Power Steering project tracking tool used by the National Guard for continuous process improvement projects. It describes how to access and navigate Power Steering, the roles and responsibilities of Black Belts in using it to track project progress, and how to invite new users. The learning objectives are to understand how to use Power Steering to navigate, track projects, and share best practices.
The document provides guidance on using the Power Steering project tracking tool. It outlines how to access Power Steering, navigate the interface, update user profiles, and invite new users. Power Steering is used to track Department of Defense continuous process improvement projects, store associated templates and tools, and share best practices between projects. National Guard students who attend Black Belt training will receive login credentials to enter project details and updates.
Marketing the Agile Way - Applying Scrum Outside of DevelomentKirsten Knipp
Using agile development methodologies in marketing is becoming more prevalent. This presentation defines scrum and describes how it's used in practice at HubSpot to gain greater transparency, manage prioritization better and achieve more predictability in our marketing efforts.
Using agile development methodologies in marketing is becoming more prevalent. This presentation defines scrum and describes how it's used in practice at HubSpot to gain greater transparency, manage prioritization better and achieve more predictability in our marketing efforts.
Scaling - Getting Bigger is Not the AnswerDon Patti
Ask someone why they want to scale and their response is often, "So we can continue practicing agile as we grow bigger." While the pursuit of agility is a noble one, most often the pursuit of "bigness" is not. But what is?
In this talk, David Bulkin and Donald Patti will introduce attendees to three of the most popular scaling frameworks -- Scrum@Scale, LeSS and SAFe -- comparing the qualities of each. In addition, they'll explain what organizations looking to scale SHOULD pursue as they scale.
The document discusses problems with typical development approaches and how agile methodologies address these issues through feedback loops. Typical development relies on upfront planning that becomes outdated and does not integrate customer feedback well. Agile uses short iterations, user stories to track business value, and continuous feedback to allow plans to change quickly in response to new information. This helps ensure development stays aligned with customer needs and allows for incremental delivery of value.
The document discusses the needs for open and appropriate technology documentation. It notes that technology documentation needs to be tailored for different user groups, from teachers and developers to implementers, and that these groups have varying resources and needs. The document examines examples of technology documentation and identifies shortcomings. It emphasizes that documentors need access to all source materials to create customizable documentation. The key is remembering that the intended users, not the inventors, should be the top priority in documentation.
The power to Say NO - Using Scrum in a BAU TeamMia Horrigan
Using Scrum to empower your team during BAU (business as usual) development and maintenance. presentation at the #LAST Conference Melbourne 27 Jul 2012
#LAST (Lean, Agile, Systems Thinking)
Continuous Infrastructure First Ignite EditionKris Buytaert
This document discusses different approaches to implementing continuous infrastructure and collaboration between development and operations teams. It argues that starting with operations automating their own workflows first allows them to understand the tools and processes before enforcing them on developers, prevents technical debt, and enables delivery and provisioning from the start. Having dedicated operations resources focus on automation leads to improved collaboration and quality over having "devops" teams dictate tools to operations.
DevOps Days Kyiv 2019 -- continuous Infrafirstructure First //Kris buytaertMykola Marzhan
This document discusses different approaches to implementing continuous infrastructure and collaboration between development and operations teams. It argues that starting with operations automating their own workflows first allows them to understand the tools and processes before enforcing them on developers, prevents technical debt, and enables delivery and provisioning from the start. Getting operations involved early through dedicating resources to infrastructure as code avoids prolonged periods where operations teams are playing catch up or acting as heroes.
DevOps Days Kyiv 2019 -- continuous Infrafirstructure First //Kris buytaert
Government- popplet rubric
1. AMERICAN CANYON HIGH SCHOOL Topic:__________________________________
Popplet SCORING RUBRIC
EVALUATOR:________________ DATE: _________
Government – L.Bell
UNSATISFACTORY PROFICIENT ADVANCED
CONTENT (Below Performance Standards) (Minimal Criteria) (Demonstrates Exceptional Performance)
● Information presented in the ● Some information presented in the ● All information presented in the
Content Popplet was unclear, and Popplet was clear, and accurate. Popplet was clear, accurate and
inaccurate. ● Most “must haves” are included; thorough.
● Missing most/all “must Facts, Issues, Justification, Driving ● All “must haves” are included; Facts,
haves”; Facts, Issues, Question, Groups Decision(s), Issues, Justification, Driving Question,
Justification, Driving Actual Court Decision. Groups Decision(s), Actual Court
Question, Groups ● Terms/concepts are mostly used Decision.
Decision(s), Actual Court properly with brief explanation of ● Terms/concepts used properly with
Decision. reasoning for choices. detailed explanation of reasoning for
● Terms/concepts are used ● Information does not exceed class choices
incorrectly with little to no discussions. ● Information goes above what was
explanation of reasoning for discussed in class, and/or added in
choices. additional information as they saw fit.
● Information from class
discussions lacking/missing.
0 - - - - - - - - - - - - - - - - - - - - - - - - 10 12 - - - - - - - - - - - - - - - - - - - - - - - - 14 16 - - - - - - - - - - - -- - - - - - - - - - - - 18
SKILL UNSATISFACTORY PROFICIENT ADVANCED
● Popplet is one/two group ● Popplet is created and most group ● Popplet is created and all group
Technology
members and may not have members have been added as members have been added as
added “collaborators”. “collaborators”. “collaborators”.
● Layout is basic, and does not ● Layout is basic, and may include ● Layout is advanced, included
include “Popplets”, with “Popplets”, with “Popplets”, and/or
pictures/graphics/visuals/Lin pictures/graphics/visuals/Links. pictures/graphics/visuals/Links.
ks. ● Most links worked (if applicable) ● All links worked (if applicable)
● Links did not work (if ● Information is organized on the ● Information is organized on the site,
applicable) site, flows and is not recorded/not flows and is recorded ready to
● Information is unorganized ready to Present. Present.
on the site, does not flow
and is not recorded/not
ready to Present.