The document describes an experiment with an image of a red panda as the starting point. The creator reflects on which elements of their experiments they will include in their final product.
Making Infrastructure as Awesome as Agile Developmentmsilpala
I gave this talk at the AgileIndy 2016 conference in Indianapolis, IN. April 12, 2016. It gives s tour of what's so awesome about agile software (as it was intended—not as many of today's implementations go), and ways to bring some of that awesomeness to your DevOps adoption.
Three years ago, Morten von Seelen started as intern at Kamstrup and today, he is working as Software Engineer with specialization in system security.
In an inspiring and exciting way, Morten tells about the everyday as developer and employee at Kamstrup and how he reached to become an "Inhouse Hacker".
The presentation will be held in english.
This document discusses test automation challenges at an investment bank and lessons learned. It outlines problems with lengthy manual regression testing. An attempt was made to use Jameleon for test automation but it caused issues. They identified needs for metrics, definitions of done, and separating test connections. Recommendations include using tools like Selenium and SoapUI with a Jenkins/JIRA setup. While quick wins are possible, separating test connections and fully defining requirements are important for successful test automation.
This document summarizes a team's transition from Scrum to Kanban. The team used Scrum practices like 2-week iterations and daily standups but found the iterations felt artificial and Scrum was not flexible enough for their work. With Kanban, they visualized their workflow on a board, limited work-in-progress, and measured lead time. This provided greater flexibility while still maintaining structure and discipline. The team observed benefits like improved responsiveness and ability to handle unexpected work, though protecting capacity was important. In summary, Kanban was a better fit for the team's needs than Scrum.
How engineering practices help businessAndrey Rebrov
This document provides advice on how to introduce new engineering practices and technologies to a team or business. It discusses several examples of proposed new practices and technologies such as test automation, continuous integration, refactoring, and DevOps. For each, it advises how to demonstrate the benefits through examples and metrics, how to gain buy-in from various stakeholders, and pitfalls to avoid such as claiming a practice is necessary just because a famous person recommends it. The overall message is that new practices must provide clear value and be introduced through demonstration and collaboration rather than dictates.
Agile Testing in Enterprise: Way to transform - SQA Days 2014Andrey Rebrov
This document discusses problems that can occur with traditional testing approaches and how to transition to agile testing practices. It provides two examples of organizations that struggled with long regression cycles, missed estimates, low quality and stress. The root causes are identified as document-based collaboration, lack of testing knowledge by developers, and infrastructure management chaos. Recommendations are made to use Kanban, collaborate on requirements, implement smart metrics, test automation, and a DevOps approach. Specific practices that were implemented include risk management, specification by example, test-driven development, continuous integration, configuration automation, and test automation. The results were increased delivery rates up to 5 times, zero bugs in production, no overtime, and more enjoyable work.
Lean Kanban India 2016 | Waterfall vs Kanban – Experience the Flow | Sanjay K...LeanKanbanIndia
The document compares how work flows using the Waterfall vs Kanban project management methods. It outlines a simulation where 10 features are developed over 10 days with limited resources. Using a Kanban board and cycle times, the progress of each method is tracked. Special events and defects impacted the flow of work differently between the two methods. At days 4, 7, and 10 the Kanban boards are reviewed to compare the progress and flow of work under each approach.
Making Infrastructure as Awesome as Agile Developmentmsilpala
I gave this talk at the AgileIndy 2016 conference in Indianapolis, IN. April 12, 2016. It gives s tour of what's so awesome about agile software (as it was intended—not as many of today's implementations go), and ways to bring some of that awesomeness to your DevOps adoption.
Three years ago, Morten von Seelen started as intern at Kamstrup and today, he is working as Software Engineer with specialization in system security.
In an inspiring and exciting way, Morten tells about the everyday as developer and employee at Kamstrup and how he reached to become an "Inhouse Hacker".
The presentation will be held in english.
This document discusses test automation challenges at an investment bank and lessons learned. It outlines problems with lengthy manual regression testing. An attempt was made to use Jameleon for test automation but it caused issues. They identified needs for metrics, definitions of done, and separating test connections. Recommendations include using tools like Selenium and SoapUI with a Jenkins/JIRA setup. While quick wins are possible, separating test connections and fully defining requirements are important for successful test automation.
This document summarizes a team's transition from Scrum to Kanban. The team used Scrum practices like 2-week iterations and daily standups but found the iterations felt artificial and Scrum was not flexible enough for their work. With Kanban, they visualized their workflow on a board, limited work-in-progress, and measured lead time. This provided greater flexibility while still maintaining structure and discipline. The team observed benefits like improved responsiveness and ability to handle unexpected work, though protecting capacity was important. In summary, Kanban was a better fit for the team's needs than Scrum.
How engineering practices help businessAndrey Rebrov
This document provides advice on how to introduce new engineering practices and technologies to a team or business. It discusses several examples of proposed new practices and technologies such as test automation, continuous integration, refactoring, and DevOps. For each, it advises how to demonstrate the benefits through examples and metrics, how to gain buy-in from various stakeholders, and pitfalls to avoid such as claiming a practice is necessary just because a famous person recommends it. The overall message is that new practices must provide clear value and be introduced through demonstration and collaboration rather than dictates.
Agile Testing in Enterprise: Way to transform - SQA Days 2014Andrey Rebrov
This document discusses problems that can occur with traditional testing approaches and how to transition to agile testing practices. It provides two examples of organizations that struggled with long regression cycles, missed estimates, low quality and stress. The root causes are identified as document-based collaboration, lack of testing knowledge by developers, and infrastructure management chaos. Recommendations are made to use Kanban, collaborate on requirements, implement smart metrics, test automation, and a DevOps approach. Specific practices that were implemented include risk management, specification by example, test-driven development, continuous integration, configuration automation, and test automation. The results were increased delivery rates up to 5 times, zero bugs in production, no overtime, and more enjoyable work.
Lean Kanban India 2016 | Waterfall vs Kanban – Experience the Flow | Sanjay K...LeanKanbanIndia
The document compares how work flows using the Waterfall vs Kanban project management methods. It outlines a simulation where 10 features are developed over 10 days with limited resources. Using a Kanban board and cycle times, the progress of each method is tracked. Special events and defects impacted the flow of work differently between the two methods. At days 4, 7, and 10 the Kanban boards are reviewed to compare the progress and flow of work under each approach.
What is the best way to measure DevOps performance? There are many ways that people have tried to measure productivity in software delivery in the past -- what works and what doesn’t? In this webinar, Dr. Nicole Forsgren and Robert Reeves will present some lessons learned about measuring software delivery and why it’s important. The webinar will also highlight the key factors driving DevOps performance and offer a preview to some of the challenges on the horizon.
Tune into this webinar to learn about:
Flaws in previous attempts to measure performance
What really matters (hint: focus on outcomes)
The four measures that are key to delivery performance
The *big* difference between high performers and the rest
Why maturity models don’t work
What high performers can do for their organizations
What challenges are up next in technology transformations… things like data, serverless, and security.
The document describes a Kanban flow model where work items enter a backlog queue and the highest priority items are pulled into development. Once development is complete, items move to an output queue until deployment. When deployment has an issue, work backs up. Limiting work in progress and defining policies for "done" and expedited items helps work flow again. When testing gets stuck, cross-functional teams help unblock each other to solve problems and keep work flowing.
Scaffolding a legacy app with BDD scenarios using SpecFlow/Cucumber (BDD Lond...Gáspár Nagy
Do you remember your childhood when your mom or an older story teller pronounced the most interesting words in the world? “Once upon a time…” Let me be now your story teller, listen to my story about a legacy app, a painful problem, the search for the solution and the lucky outcome. No, no, this is not the story about a new green field project where everything is so clear. However, even in this story there is a master builder, who shows the developers how to scaffold the legacy app with BDD scenarios using SpecFlow or Cucumber and everything will be all right in the end. Let me tell you about different strategies, collaboration and testing patterns that can be followed in such a renovation-like situation. So, are you ready?... “Once upon a time there was a company where…” To be continued at my session
Scaffolding a legacy app with BDD scenarios using SpecFlow/Cucumber (HUSTEF 2...Gáspár Nagy
Do you remember your childhood when your mom or an older story teller pronounced the most interesting words in the world? “Once upon a time…” Let me be now your story teller, listen to my story about a legacy app, a painful problem, the search for the solution and the lucky outcome. No, no, this is not the story about a new green field project where everything is so clear. However, even in this story there is a master builder, who shows the developers how to scaffold the legacy app with BDD scenarios using SpecFlow or Cucumber and everything will be all right in the end. Let me tell you about different strategies, collaboration and testing patterns that can be followed in such a renovation-like situation. So, are you ready?... “Once upon a time there was a company where…” To be continued at my session
Webinar: Kanban or Scrum – Is Scrum for developers and Kanban for IT support?Intland Software GmbH
Watch this webinar recording to learn about the fundamentals of the two most popular Agile approaches: Scrum and Kanban. The webinar explains why, how and when these are best used, and the benefits commonly associated with their use. The video also talks about Scrumban, the approach combining the benefits of Scrum and Kanban, and discusses how you could benefit from using Scrumban in your organization. As usual, a live demonstration then shows how codeBeamer supports all Agile processes.
http://intland.com/webinar/2015-03/kanban-or-scrum-is-scrum-for-developers-and-kanban-for-it-support-4/
Extending JIRA to Enable High Volume KPI Benchmarking - Keyur PatelAtlassian
At Intel, KPIs are measured and reported weekly across multiple, global projects. In this session, we'll cover the business case and architecture behind developing an end-to-end process management system for KPI benchmarking, tracking, and monitoring using JIRA for more than 6,000 users.
This document summarizes trends in test automation, including:
- In the past, test automation was mainly used for regression testing after development and had a long return on investment.
- Now, test automation is becoming more flexible, faster, and integrated into the development process earlier on. Automated testing can start from the beginning of a project and be a continuous process.
- Trends include test automation being less technical and specialized, having a shorter return on investment, and becoming part of agile and DevOps practices with continuous testing and deployment. Automation allows testing to speed up and occur more frequently.
Moving QA from Reactive to Proactive with qTestQASymphony
This document discusses moving quality assurance from a reactive to a proactive approach using qTest. It outlines some of the challenges with the current reactive approach, such as crashes occurring and teams blaming the QA team. It then discusses how to take a more proactive approach by efficiently creating and organizing tests, monitoring tests, reusing tests and parameters, consolidating results, and defining test scenarios before coding using behavior driven development. The key recommendations are to record manual and exploratory tests, use a test management system that promotes reuse, radiate test results to development systems, build combined testing dashboards, and use BDD to ensure early test planning.
This document discusses qTest, a test case management tool. It provides an overview of qTest's features, advantages, and workflow. Key points include:
- qTest helps improve testing productivity, collaboration, and integration between teams.
- Features include test planning, scalability, easy setup and use, and integration with other systems.
- Advantages include requirements and defect tracking, customization, and robust reporting capabilities.
- The workflow involves business analysts, project managers, testers, developers, and administrators collaborating on requirements, test design, execution, and reporting throughout the testing process.
This document summarizes the scaling of agile practices at a UK financial investment advisory firm. It discusses how the firm initially had success using scrum over 10 sprints to enhance an existing application. However, an annual client satisfaction survey later raised concerns about code quality, architectural stability, and technical competency. New metrics were introduced to better measure sprint effectiveness and identify areas for improvement, including a Sprint Acceptance Index and Sprint Demo Defect Density measure. The goal is to stabilize performance trends and focus on weaknesses indicated by these more objective measures.
The document discusses Agile and Scrum frameworks as alternatives to the traditional Waterfall model. It outlines the key principles of the Agile Manifesto which values individuals and collaboration over processes. The three main pillars of Scrum are transparency, inspection, and adaptation. Scrum uses artifacts like the Product and Sprint Backlogs and defines roles of the Product Owner, Scrum Master, and self-organizing Development Team. Key Scrum ceremonies are also summarized such as Sprint Planning, Daily Scrum, Review and Retrospective meetings.
Understanding the Whole System, Not Just a PartBrian Sjoberg
Are your solutions to recurring issues having only minor improvements? Are some of these solutions actually making things worse in the long run? When answering yes to these, typically, we are trying to solve the issues with too narrow a view. Oddly we think we are addressing it at sufficient level but usually not. In order to see the entire picture we need a common language that will enable us to understand an entire complex adaptive system (e.g. organizations, teams, individuals). Join us as we learn a language called System Modeling.
With this language we will be able to have rich dialogue to gain a full understanding of the entire complex adaptive system so that we can create solutions at the fundamental level and not the symptomatic level. Addressing system issues at the fundamental level will significantly improve the system. Symptomatic solutions may give the appearance of improvement in the short term but typically make things worse in the long run. Unfortunately we usually pick the symptomatic solutions because they seem obvious and we don't realize the long term impacts because of feedback delays that could take weeks, months or even years to realize.
This document discusses using Puppet for configuration management and summarizing the benefits and concerns of getting management and developers onboard. It outlines a two phase process of pre-presentation to gather information and address concerns, and a development/implementation phase with communication. Benefits include stability, consistency, control and time savings while concerns include time to implement, accountability and being "another tool". The document advocates treating dev and ops as symbiotic and providing necessary documentation and resources.
Elm - never get a runtime error anymore. Almost.Anton Astashov
Elm, a transpiled-to-JavaScript language which makes sure you’ll never have a runtime error in your app. Almost. Why it’s cool, what it looks like, it’s pros and (most importantly) cons.
The goal of centralized tools & support teams is to provide the most value for our development and operations customers with the least amount of overhead. One way of optimizing this delivery of value in large enterprise engineering environments is through standardization and automation.
Learn how Bose engineers use ElectricFlow to deliver standardized and integrated build environment to teams in a matter of minutes. In this session we’ll cover:
• Effective use of a Procedure Library to abstract away complexity and standardize build procedures
• Creation and use of a Build Data Management system to handle dependencies between components
• Methods for refactoring existing automation to take advantage of advanced ElectricFlow features
• Options for enabling shared visibility into the health of all applications and commit pipelines
This document discusses challenges with estimating velocity for the initial sprint of a new Scrum team. It notes that using past data from other teams is not accurate for a new team. While management wants estimates upfront, the best approach is to wait for real data from the first sprint. The document recommends a risk mitigation approach of estimating tasks in hours to approximate a velocity range for the first sprint. Additional challenges can arise from delivering a minimum viable product that does not match architectural needs.
The student struggled with various aspects of the project such as research, planning, and production due to mental and physical health issues. Production was particularly challenging, as the student only managed to take 10 mediocre photos due to a lack of effort and inability to leave home frequently. While the final product was a black and white street photography portfolio as intended, the quality and standard did not meet the student's original intentions due to weaknesses in various phases of the project. The student learned from the experience but remained disappointed they could not push themselves further or accomplish their full goals.
The interviews provided feedback on expectations for a photography portfolio. Both interviewees said they would expect photos to be named, dated, and have location details. They also agreed a website would help promote the work. One preferred black and white while the other said a mix of color and black and white would be best. The number of photos expected ranged from 10-12 to 20-30. Both said framed photos would look more professional than board-mounted. The interviews reinforced the photographer's plans to include names, shoot in black and white, create a website, and frame the final portfolio photos.
The document provides an evaluation by Alexander Sullivan-Cree of various aspects of a client project they completed. For research, they struggled to find relevant demographic information for their target audience. Their planning went well as they developed good ideas, creating initial designs before finalizing in Illustrator. Time management was poor due to health issues, resulting in rushed work that did not meet their standards. They achieved the retro aesthetic they aimed for but were unhappy with the quality, especially the "alien" mascot created through copying rather than skill.
This document outlines a client project for a comic book store called Destination Venus. The student proposes 3 ideas: 1) Creating a mascot for the store in the form of an alien or astronaut, which could be used on promotional materials. 2) Designing new promotional materials like posters and business cards with a space theme. 3) Redesigning the store's website and social media pages to have a more modern space and comic book theme. The student decides to pursue the mascot idea as their final project. They provide details on the design inspiration, colors, production schedule, and plan to create both an astronaut and alien mascot in Adobe Illustrator over 3 weeks.
Alexander Sullivan-Cree is applying to university through UCAS. He attended King James Highschool where he earned various GCSE grades. He then attended York College where he earned pass, merit, and distinction grades. He is considering courses in Marine and Natural History Photography at Falmouth University, Japanese at the University of Edinburgh or University of Leeds, and Graphic Design which he rates as an 8/10 suitability due to being a good choice for his current course of study.
This document provides an evaluation of the student's fanzine project. For the research stage, the student felt their initial ideas were strongest but struggled to find related existing fanzines. Their planning was one of the strongest parts as they knew the information and chose a layout/color scheme. However, they changed their pagination multiple times. They managed their time effectively using a production schedule but wish they had more time for additional pages/a more professional look. Their fanzine has a simpler, notebook-like aesthetic compared to a professional fanzine and they would improve layout, original artwork, and front cover design for the future.
What is the best way to measure DevOps performance? There are many ways that people have tried to measure productivity in software delivery in the past -- what works and what doesn’t? In this webinar, Dr. Nicole Forsgren and Robert Reeves will present some lessons learned about measuring software delivery and why it’s important. The webinar will also highlight the key factors driving DevOps performance and offer a preview to some of the challenges on the horizon.
Tune into this webinar to learn about:
Flaws in previous attempts to measure performance
What really matters (hint: focus on outcomes)
The four measures that are key to delivery performance
The *big* difference between high performers and the rest
Why maturity models don’t work
What high performers can do for their organizations
What challenges are up next in technology transformations… things like data, serverless, and security.
The document describes a Kanban flow model where work items enter a backlog queue and the highest priority items are pulled into development. Once development is complete, items move to an output queue until deployment. When deployment has an issue, work backs up. Limiting work in progress and defining policies for "done" and expedited items helps work flow again. When testing gets stuck, cross-functional teams help unblock each other to solve problems and keep work flowing.
Scaffolding a legacy app with BDD scenarios using SpecFlow/Cucumber (BDD Lond...Gáspár Nagy
Do you remember your childhood when your mom or an older story teller pronounced the most interesting words in the world? “Once upon a time…” Let me be now your story teller, listen to my story about a legacy app, a painful problem, the search for the solution and the lucky outcome. No, no, this is not the story about a new green field project where everything is so clear. However, even in this story there is a master builder, who shows the developers how to scaffold the legacy app with BDD scenarios using SpecFlow or Cucumber and everything will be all right in the end. Let me tell you about different strategies, collaboration and testing patterns that can be followed in such a renovation-like situation. So, are you ready?... “Once upon a time there was a company where…” To be continued at my session
Scaffolding a legacy app with BDD scenarios using SpecFlow/Cucumber (HUSTEF 2...Gáspár Nagy
Do you remember your childhood when your mom or an older story teller pronounced the most interesting words in the world? “Once upon a time…” Let me be now your story teller, listen to my story about a legacy app, a painful problem, the search for the solution and the lucky outcome. No, no, this is not the story about a new green field project where everything is so clear. However, even in this story there is a master builder, who shows the developers how to scaffold the legacy app with BDD scenarios using SpecFlow or Cucumber and everything will be all right in the end. Let me tell you about different strategies, collaboration and testing patterns that can be followed in such a renovation-like situation. So, are you ready?... “Once upon a time there was a company where…” To be continued at my session
Webinar: Kanban or Scrum – Is Scrum for developers and Kanban for IT support?Intland Software GmbH
Watch this webinar recording to learn about the fundamentals of the two most popular Agile approaches: Scrum and Kanban. The webinar explains why, how and when these are best used, and the benefits commonly associated with their use. The video also talks about Scrumban, the approach combining the benefits of Scrum and Kanban, and discusses how you could benefit from using Scrumban in your organization. As usual, a live demonstration then shows how codeBeamer supports all Agile processes.
http://intland.com/webinar/2015-03/kanban-or-scrum-is-scrum-for-developers-and-kanban-for-it-support-4/
Extending JIRA to Enable High Volume KPI Benchmarking - Keyur PatelAtlassian
At Intel, KPIs are measured and reported weekly across multiple, global projects. In this session, we'll cover the business case and architecture behind developing an end-to-end process management system for KPI benchmarking, tracking, and monitoring using JIRA for more than 6,000 users.
This document summarizes trends in test automation, including:
- In the past, test automation was mainly used for regression testing after development and had a long return on investment.
- Now, test automation is becoming more flexible, faster, and integrated into the development process earlier on. Automated testing can start from the beginning of a project and be a continuous process.
- Trends include test automation being less technical and specialized, having a shorter return on investment, and becoming part of agile and DevOps practices with continuous testing and deployment. Automation allows testing to speed up and occur more frequently.
Moving QA from Reactive to Proactive with qTestQASymphony
This document discusses moving quality assurance from a reactive to a proactive approach using qTest. It outlines some of the challenges with the current reactive approach, such as crashes occurring and teams blaming the QA team. It then discusses how to take a more proactive approach by efficiently creating and organizing tests, monitoring tests, reusing tests and parameters, consolidating results, and defining test scenarios before coding using behavior driven development. The key recommendations are to record manual and exploratory tests, use a test management system that promotes reuse, radiate test results to development systems, build combined testing dashboards, and use BDD to ensure early test planning.
This document discusses qTest, a test case management tool. It provides an overview of qTest's features, advantages, and workflow. Key points include:
- qTest helps improve testing productivity, collaboration, and integration between teams.
- Features include test planning, scalability, easy setup and use, and integration with other systems.
- Advantages include requirements and defect tracking, customization, and robust reporting capabilities.
- The workflow involves business analysts, project managers, testers, developers, and administrators collaborating on requirements, test design, execution, and reporting throughout the testing process.
This document summarizes the scaling of agile practices at a UK financial investment advisory firm. It discusses how the firm initially had success using scrum over 10 sprints to enhance an existing application. However, an annual client satisfaction survey later raised concerns about code quality, architectural stability, and technical competency. New metrics were introduced to better measure sprint effectiveness and identify areas for improvement, including a Sprint Acceptance Index and Sprint Demo Defect Density measure. The goal is to stabilize performance trends and focus on weaknesses indicated by these more objective measures.
The document discusses Agile and Scrum frameworks as alternatives to the traditional Waterfall model. It outlines the key principles of the Agile Manifesto which values individuals and collaboration over processes. The three main pillars of Scrum are transparency, inspection, and adaptation. Scrum uses artifacts like the Product and Sprint Backlogs and defines roles of the Product Owner, Scrum Master, and self-organizing Development Team. Key Scrum ceremonies are also summarized such as Sprint Planning, Daily Scrum, Review and Retrospective meetings.
Understanding the Whole System, Not Just a PartBrian Sjoberg
Are your solutions to recurring issues having only minor improvements? Are some of these solutions actually making things worse in the long run? When answering yes to these, typically, we are trying to solve the issues with too narrow a view. Oddly we think we are addressing it at sufficient level but usually not. In order to see the entire picture we need a common language that will enable us to understand an entire complex adaptive system (e.g. organizations, teams, individuals). Join us as we learn a language called System Modeling.
With this language we will be able to have rich dialogue to gain a full understanding of the entire complex adaptive system so that we can create solutions at the fundamental level and not the symptomatic level. Addressing system issues at the fundamental level will significantly improve the system. Symptomatic solutions may give the appearance of improvement in the short term but typically make things worse in the long run. Unfortunately we usually pick the symptomatic solutions because they seem obvious and we don't realize the long term impacts because of feedback delays that could take weeks, months or even years to realize.
This document discusses using Puppet for configuration management and summarizing the benefits and concerns of getting management and developers onboard. It outlines a two phase process of pre-presentation to gather information and address concerns, and a development/implementation phase with communication. Benefits include stability, consistency, control and time savings while concerns include time to implement, accountability and being "another tool". The document advocates treating dev and ops as symbiotic and providing necessary documentation and resources.
Elm - never get a runtime error anymore. Almost.Anton Astashov
Elm, a transpiled-to-JavaScript language which makes sure you’ll never have a runtime error in your app. Almost. Why it’s cool, what it looks like, it’s pros and (most importantly) cons.
The goal of centralized tools & support teams is to provide the most value for our development and operations customers with the least amount of overhead. One way of optimizing this delivery of value in large enterprise engineering environments is through standardization and automation.
Learn how Bose engineers use ElectricFlow to deliver standardized and integrated build environment to teams in a matter of minutes. In this session we’ll cover:
• Effective use of a Procedure Library to abstract away complexity and standardize build procedures
• Creation and use of a Build Data Management system to handle dependencies between components
• Methods for refactoring existing automation to take advantage of advanced ElectricFlow features
• Options for enabling shared visibility into the health of all applications and commit pipelines
This document discusses challenges with estimating velocity for the initial sprint of a new Scrum team. It notes that using past data from other teams is not accurate for a new team. While management wants estimates upfront, the best approach is to wait for real data from the first sprint. The document recommends a risk mitigation approach of estimating tasks in hours to approximate a velocity range for the first sprint. Additional challenges can arise from delivering a minimum viable product that does not match architectural needs.
The student struggled with various aspects of the project such as research, planning, and production due to mental and physical health issues. Production was particularly challenging, as the student only managed to take 10 mediocre photos due to a lack of effort and inability to leave home frequently. While the final product was a black and white street photography portfolio as intended, the quality and standard did not meet the student's original intentions due to weaknesses in various phases of the project. The student learned from the experience but remained disappointed they could not push themselves further or accomplish their full goals.
The interviews provided feedback on expectations for a photography portfolio. Both interviewees said they would expect photos to be named, dated, and have location details. They also agreed a website would help promote the work. One preferred black and white while the other said a mix of color and black and white would be best. The number of photos expected ranged from 10-12 to 20-30. Both said framed photos would look more professional than board-mounted. The interviews reinforced the photographer's plans to include names, shoot in black and white, create a website, and frame the final portfolio photos.
The document provides an evaluation by Alexander Sullivan-Cree of various aspects of a client project they completed. For research, they struggled to find relevant demographic information for their target audience. Their planning went well as they developed good ideas, creating initial designs before finalizing in Illustrator. Time management was poor due to health issues, resulting in rushed work that did not meet their standards. They achieved the retro aesthetic they aimed for but were unhappy with the quality, especially the "alien" mascot created through copying rather than skill.
This document outlines a client project for a comic book store called Destination Venus. The student proposes 3 ideas: 1) Creating a mascot for the store in the form of an alien or astronaut, which could be used on promotional materials. 2) Designing new promotional materials like posters and business cards with a space theme. 3) Redesigning the store's website and social media pages to have a more modern space and comic book theme. The student decides to pursue the mascot idea as their final project. They provide details on the design inspiration, colors, production schedule, and plan to create both an astronaut and alien mascot in Adobe Illustrator over 3 weeks.
Alexander Sullivan-Cree is applying to university through UCAS. He attended King James Highschool where he earned various GCSE grades. He then attended York College where he earned pass, merit, and distinction grades. He is considering courses in Marine and Natural History Photography at Falmouth University, Japanese at the University of Edinburgh or University of Leeds, and Graphic Design which he rates as an 8/10 suitability due to being a good choice for his current course of study.
This document provides an evaluation of the student's fanzine project. For the research stage, the student felt their initial ideas were strongest but struggled to find related existing fanzines. Their planning was one of the strongest parts as they knew the information and chose a layout/color scheme. However, they changed their pagination multiple times. They managed their time effectively using a production schedule but wish they had more time for additional pages/a more professional look. Their fanzine has a simpler, notebook-like aesthetic compared to a professional fanzine and they would improve layout, original artwork, and front cover design for the future.
This document outlines Alexander Sullivan-Cree's showreel, which includes work from Level 3 Year 1, Level 3 Year 2, and Level 2 Year 1 of his studies. The showreel provides a high-level overview of the types of projects and work Alexander completed during different years and levels of his education.
UCAS is an organization that handles applications to higher education programs in the United Kingdom. The document discusses an individual named Alexander Sullivan-Cree who is likely involved with UCAS as their name is the title of the document. However, no other contextual information is provided about Alexander Sullivan-Cree or their specific role at UCAS.
This document discusses the color scheme, fonts, and locations for a photography portfolio project. For the color scheme, the project will focus on black and white photography and use the color #0c0c0c for the website. No special fonts are needed for the photography, but the creator plans to design their own font incorporating their name for the portfolio title. The primary photography locations will be the creator's hometown of Knaresborough for its tourist attractions, Whitby for its seaside scenery, and York for its historic areas and street performers.
The document discusses research conducted for a photography portfolio project. It includes interviews with two people about what they would expect to see in a portfolio. It also covers the interviewees' familiarity with street photographers and preferences for displaying work. Both interviews indicated names and locations should be included with photos and that a website could help promote the work. Black and white images were favored over color by one interviewee. The document also provides a bibliography of sources consulted.
The document discusses potential problems that could arise during a street photography project and ways to address them. It identifies issues with equipment failure or unavailability, including cameras breaking down or memory cards corrupting. Software and hardware compatibility between college and personal devices is also flagged as a risk. Location access problems and unpredictable British weather are highlighted as external factors that could impact shoots. Backups, spare gear, and alternative local shooting spots are proposed to mitigate many of these potential problems.
Alexander Sullivan-Cree has had a lifelong interest in photography and media that began when he was diagnosed with Type 1 diabetes at age nine. This dashed his hopes of joining the navy like other men in his family. At college, he studied photography, video editing, and audio editing software. For projects, he created video game assets, magazines focused on anime and manga, and a fashion magazine featuring original photography shoots. His dream is to have his photography published in prestigious magazines like National Geographic that document wildlife and culture around the world.
This document discusses research for a photography portfolio, including existing photographers like Vivian Maier, William Klein, Robert Frank, Eddie Adams, and Alfred Eisenstaedt. It also includes interviews with two people about what they would expect to see in a portfolio, whether black and white or color is more professional, and how many photos a portfolio should contain. The document ends with a bibliography of sources about iconic street photographers.
The document summarizes research conducted for a local comic book store client. It discusses the store's diverse audience due to its range of comics, citing a survey that found 63% of comic buyers are men aged 13-29. It also notes that while comics generally appeal more to boys and men, the store is located in a cinema, so it gets traffic from all ages. To avoid alienating female customers, the document recommends a gender-neutral color scheme for marketing. It also discusses Harrogate's demographics, including its female population of 51% and religious diversity.
The student proposes a black and white street photography portfolio titled "City Ruins" featuring images taken in their hometown of Knaresborough, Yorkshire. Photography will be the primary medium, with the goal of also creating a website and booklet to showcase the work. The student has researched street photographers like Joel Meyerowitz, Helen Levitt, and Henri Cartier-Bresson for inspiration. Peer and public feedback will be gathered to evaluate the project, which will involve primary research, experiments, image taking and editing over 15 weeks culminating in a final presentation.
The document provides biographies of four photographers: Joel Meyerowitz, Helen Levitt, Henri Cartier-Bresson, and Nick Turpin. It describes their backgrounds, influences, notable works, and contributions to photography. Joel Meyerowitz pioneered the use of color photography and published influential books. Helen Levitt photographed street scenes and children in New York. Henri Cartier-Bresson developed a passion for photography after being introduced to the Leica camera, and published The Decisive Moment. Nick Turpin studied photography and established the In-Public collective to promote street photography.
The student proposes a black and white street photography portfolio titled "City Ruins" featuring images taken in their hometown of Knaresborough, Yorkshire. Photography will be the primary medium, and if time allows, a website and booklet will be created to showcase the work. The student has researched street photographers like Joel Meyerowitz, Helen Levitt, and Henri Cartier-Bresson for inspiration. Peer and public feedback will be gathered to evaluate the project, and over 20 weeks the student will complete tasks like primary/secondary research, experiments, production, and presentation.
The proposal outlines a street photography portfolio titled "City Ruins" focused on the student's hometown of Knaresborough, Yorkshire. Photography will be the primary medium, with the goal of also creating a website and booklet to showcase the work. The student has researched street photographers like Joel Meyerowitz, Helen Levitt, and Henri Cartier-Bresson for inspiration. Peer and public feedback will be used for evaluation, with the project timeline spanning pre-production, production, and evaluation phases over 17 weeks culminating in a final presentation.
The document provides details about Nobuo Uematsu, the famous composer for many Final Fantasy soundtracks. It summarizes that Uematsu grew up in Kochi Prefecture in Shikoku, Japan, and that despite no formal music training, he started composing music for Square and became their main composer. It also discusses some of his musical influences like Deep Purple and mentions that he is proud that his music brings people together in harmony.
The document provides details on idea development, pagination, and a production schedule for creating a fanzine about the Final Fantasy video game series. It includes mood boards, character pages on Cloud Strife, Jenova and Sephiroth, an interview with Nobuo Uematsu, and illustrations to feature in the fanzine. A production schedule is outlined over 3 weeks to complete layouts, illustrations, written pages, and assembly of the fanzine.
How to Make a Field Mandatory in Odoo 17Celine George
In Odoo, making a field required can be done through both Python code and XML views. When you set the required attribute to True in Python code, it makes the field required across all views where it's used. Conversely, when you set the required attribute in XML views, it makes the field required only in the context of that particular view.
বাংলাদেশের অর্থনৈতিক সমীক্ষা ২০২৪ [Bangladesh Economic Review 2024 Bangla.pdf] কম্পিউটার , ট্যাব ও স্মার্ট ফোন ভার্সন সহ সম্পূর্ণ বাংলা ই-বুক বা pdf বই " সুচিপত্র ...বুকমার্ক মেনু 🔖 ও হাইপার লিংক মেনু 📝👆 যুক্ত ..
আমাদের সবার জন্য খুব খুব গুরুত্বপূর্ণ একটি বই ..বিসিএস, ব্যাংক, ইউনিভার্সিটি ভর্তি ও যে কোন প্রতিযোগিতা মূলক পরীক্ষার জন্য এর খুব ইম্পরট্যান্ট একটি বিষয় ...তাছাড়া বাংলাদেশের সাম্প্রতিক যে কোন ডাটা বা তথ্য এই বইতে পাবেন ...
তাই একজন নাগরিক হিসাবে এই তথ্য গুলো আপনার জানা প্রয়োজন ...।
বিসিএস ও ব্যাংক এর লিখিত পরীক্ষা ...+এছাড়া মাধ্যমিক ও উচ্চমাধ্যমিকের স্টুডেন্টদের জন্য অনেক কাজে আসবে ...
it describes the bony anatomy including the femoral head , acetabulum, labrum . also discusses the capsule , ligaments . muscle that act on the hip joint and the range of motion are outlined. factors affecting hip joint stability and weight transmission through the joint are summarized.
Philippine Edukasyong Pantahanan at Pangkabuhayan (EPP) CurriculumMJDuyan
(𝐓𝐋𝐄 𝟏𝟎𝟎) (𝐋𝐞𝐬𝐬𝐨𝐧 𝟏)-𝐏𝐫𝐞𝐥𝐢𝐦𝐬
𝐃𝐢𝐬𝐜𝐮𝐬𝐬 𝐭𝐡𝐞 𝐄𝐏𝐏 𝐂𝐮𝐫𝐫𝐢𝐜𝐮𝐥𝐮𝐦 𝐢𝐧 𝐭𝐡𝐞 𝐏𝐡𝐢𝐥𝐢𝐩𝐩𝐢𝐧𝐞𝐬:
- Understand the goals and objectives of the Edukasyong Pantahanan at Pangkabuhayan (EPP) curriculum, recognizing its importance in fostering practical life skills and values among students. Students will also be able to identify the key components and subjects covered, such as agriculture, home economics, industrial arts, and information and communication technology.
𝐄𝐱𝐩𝐥𝐚𝐢𝐧 𝐭𝐡𝐞 𝐍𝐚𝐭𝐮𝐫𝐞 𝐚𝐧𝐝 𝐒𝐜𝐨𝐩𝐞 𝐨𝐟 𝐚𝐧 𝐄𝐧𝐭𝐫𝐞𝐩𝐫𝐞𝐧𝐞𝐮𝐫:
-Define entrepreneurship, distinguishing it from general business activities by emphasizing its focus on innovation, risk-taking, and value creation. Students will describe the characteristics and traits of successful entrepreneurs, including their roles and responsibilities, and discuss the broader economic and social impacts of entrepreneurial activities on both local and global scales.
Walmart Business+ and Spark Good for Nonprofits.pdfTechSoup
"Learn about all the ways Walmart supports nonprofit organizations.
You will hear from Liz Willett, the Head of Nonprofits, and hear about what Walmart is doing to help nonprofits, including Walmart Business and Spark Good. Walmart Business+ is a new offer for nonprofits that offers discounts and also streamlines nonprofits order and expense tracking, saving time and money.
The webinar may also give some examples on how nonprofits can best leverage Walmart Business+.
The event will cover the following::
Walmart Business + (https://business.walmart.com/plus) is a new shopping experience for nonprofits, schools, and local business customers that connects an exclusive online shopping experience to stores. Benefits include free delivery and shipping, a 'Spend Analytics” feature, special discounts, deals and tax-exempt shopping.
Special TechSoup offer for a free 180 days membership, and up to $150 in discounts on eligible orders.
Spark Good (walmart.com/sparkgood) is a charitable platform that enables nonprofits to receive donations directly from customers and associates.
Answers about how you can do more with Walmart!"
Temple of Asclepius in Thrace. Excavation resultsKrassimira Luka
The temple and the sanctuary around were dedicated to Asklepios Zmidrenus. This name has been known since 1875 when an inscription dedicated to him was discovered in Rome. The inscription is dated in 227 AD and was left by soldiers originating from the city of Philippopolis (modern Plovdiv).
हिंदी वर्णमाला पीपीटी, hindi alphabet PPT presentation, hindi varnamala PPT, Hindi Varnamala pdf, हिंदी स्वर, हिंदी व्यंजन, sikhiye hindi varnmala, dr. mulla adam ali, hindi language and literature, hindi alphabet with drawing, hindi alphabet pdf, hindi varnamala for childrens, hindi language, hindi varnamala practice for kids, https://www.drmullaadamali.com
ISO/IEC 27001, ISO/IEC 42001, and GDPR: Best Practices for Implementation and...PECB
Denis is a dynamic and results-driven Chief Information Officer (CIO) with a distinguished career spanning information systems analysis and technical project management. With a proven track record of spearheading the design and delivery of cutting-edge Information Management solutions, he has consistently elevated business operations, streamlined reporting functions, and maximized process efficiency.
Certified as an ISO/IEC 27001: Information Security Management Systems (ISMS) Lead Implementer, Data Protection Officer, and Cyber Risks Analyst, Denis brings a heightened focus on data security, privacy, and cyber resilience to every endeavor.
His expertise extends across a diverse spectrum of reporting, database, and web development applications, underpinned by an exceptional grasp of data storage and virtualization technologies. His proficiency in application testing, database administration, and data cleansing ensures seamless execution of complex projects.
What sets Denis apart is his comprehensive understanding of Business and Systems Analysis technologies, honed through involvement in all phases of the Software Development Lifecycle (SDLC). From meticulous requirements gathering to precise analysis, innovative design, rigorous development, thorough testing, and successful implementation, he has consistently delivered exceptional results.
Throughout his career, he has taken on multifaceted roles, from leading technical project management teams to owning solutions that drive operational excellence. His conscientious and proactive approach is unwavering, whether he is working independently or collaboratively within a team. His ability to connect with colleagues on a personal level underscores his commitment to fostering a harmonious and productive workplace environment.
Date: May 29, 2024
Tags: Information Security, ISO/IEC 27001, ISO/IEC 42001, Artificial Intelligence, GDPR
-------------------------------------------------------------------------------
Find out more about ISO training and certification services
Training: ISO/IEC 27001 Information Security Management System - EN | PECB
ISO/IEC 42001 Artificial Intelligence Management System - EN | PECB
General Data Protection Regulation (GDPR) - Training Courses - EN | PECB
Webinars: https://pecb.com/webinars
Article: https://pecb.com/article
-------------------------------------------------------------------------------
For more information about PECB:
Website: https://pecb.com/
LinkedIn: https://www.linkedin.com/company/pecb/
Facebook: https://www.facebook.com/PECBInternational/
Slideshare: http://www.slideshare.net/PECBCERTIFICATION
How to Setup Warehouse & Location in Odoo 17 InventoryCeline George
In this slide, we'll explore how to set up warehouses and locations in Odoo 17 Inventory. This will help us manage our stock effectively, track inventory levels, and streamline warehouse operations.
Communicating effectively and consistently with students can help them feel at ease during their learning experience and provide the instructor with a communication trail to track the course's progress. This workshop will take you through constructing an engaging course container to facilitate effective communication.
Strategies for Effective Upskilling is a presentation by Chinwendu Peace in a Your Skill Boost Masterclass organisation by the Excellence Foundation for South Sudan on 08th and 09th June 2024 from 1 PM to 3 PM on each day.