You know what Continuous Integration is. You have heard it mentioned at every conference and at every meetup. It’s part automated testing, part automated deployment, part test-driven development, part every other DevOps catch-phrase. Now you are ready to get started implementing CI practices.
Hear Dan Munz, David Kennedy and Greg Boone discuss how CFPB was born, what challenges they faced and how WordPress became their CMS backbone throughout it all.
Scale quality with kaizen - Tech.Rocks conferenceFabrice Bernhard
MVPs at full speed with a little team: OK. But once the project scales, how do you address the inevitable slowdown due to exponential complexity? Kaizen is Toyota's scalable solution and our results are impressive.
PROJECTCON | AGILECON Midwest 2019 in Indianapolis on May 10, 2019
Presenter: Benjamin Day
Real World Scrum with Azure DevOps
You’ve got a subscription for Azure DevOps (formerly known as Visual Studio Team Services or VSTS) and you’re looking to do Scrum. Ok. Great. Now what does that mean? What does Azure DevOps actually do to help your Scrum team(s) run more efficiently? If I’m the Scrum Master, what should I be coaching my team to do? What can you do to help get to high-quality, “done”, working software faster? How does Azure DevOps make anything in Scrum easier?
In this session, we will address these from the perspective of a technically-minded Scrum Master. He’ll show you how to address four of the main pieces of running a Scrum project using Azure DevOps: Stakeholder Interaction, Planning & Execution, Testing, and streamlining the Definition of Done (DoD). Along the way there will be plenty of talk about work tracking, project management, QA testing, and automated builds.
Key Take-a-Ways:
Streamline your scrum process using Azure DevOps
Use Azure DevOps for manage stakeholder interaction using the Feedback Manager
Planning & Executing your sprints
Using Azure DevOps’s Test Plan tools to track and manage the QA testing effort
Automating release and testing using automated build
Improving your skills as a Scrum Master
Event Website: https://projectconevent.com
LinkedIn: https://www.linkedin.com/company/projectcon-llc
Facebook: http://www.facebook.com/ProjectConEvent
Twitter: http://www.twitter.com/projectconevent
YouTube: https://www.youtube.com/channel/UCLLG1SGPs1L5YLoFndvGGhQ
Instagram: https://www.instagram.com/projectconevent
Presentation Slides: https://slideshare.com/projectcon
Post Event Trailer: https://youtu.be/1_RzFBnZ7bo
You know what Continuous Integration is. You have heard it mentioned at every conference and at every meetup. It’s part automated testing, part automated deployment, part test-driven development, part every other DevOps catch-phrase. Now you are ready to get started implementing CI practices.
Hear Dan Munz, David Kennedy and Greg Boone discuss how CFPB was born, what challenges they faced and how WordPress became their CMS backbone throughout it all.
Scale quality with kaizen - Tech.Rocks conferenceFabrice Bernhard
MVPs at full speed with a little team: OK. But once the project scales, how do you address the inevitable slowdown due to exponential complexity? Kaizen is Toyota's scalable solution and our results are impressive.
PROJECTCON | AGILECON Midwest 2019 in Indianapolis on May 10, 2019
Presenter: Benjamin Day
Real World Scrum with Azure DevOps
You’ve got a subscription for Azure DevOps (formerly known as Visual Studio Team Services or VSTS) and you’re looking to do Scrum. Ok. Great. Now what does that mean? What does Azure DevOps actually do to help your Scrum team(s) run more efficiently? If I’m the Scrum Master, what should I be coaching my team to do? What can you do to help get to high-quality, “done”, working software faster? How does Azure DevOps make anything in Scrum easier?
In this session, we will address these from the perspective of a technically-minded Scrum Master. He’ll show you how to address four of the main pieces of running a Scrum project using Azure DevOps: Stakeholder Interaction, Planning & Execution, Testing, and streamlining the Definition of Done (DoD). Along the way there will be plenty of talk about work tracking, project management, QA testing, and automated builds.
Key Take-a-Ways:
Streamline your scrum process using Azure DevOps
Use Azure DevOps for manage stakeholder interaction using the Feedback Manager
Planning & Executing your sprints
Using Azure DevOps’s Test Plan tools to track and manage the QA testing effort
Automating release and testing using automated build
Improving your skills as a Scrum Master
Event Website: https://projectconevent.com
LinkedIn: https://www.linkedin.com/company/projectcon-llc
Facebook: http://www.facebook.com/ProjectConEvent
Twitter: http://www.twitter.com/projectconevent
YouTube: https://www.youtube.com/channel/UCLLG1SGPs1L5YLoFndvGGhQ
Instagram: https://www.instagram.com/projectconevent
Presentation Slides: https://slideshare.com/projectcon
Post Event Trailer: https://youtu.be/1_RzFBnZ7bo
The Wall Street Journal already mentioned it in 2011: “Software is eating the world”. The world is starting to discover that nowadays, every company is an IT company. Product owners and other business representatives are seeing their competitors release new features to end users every day, and are demanding the same from their own software teams.
How do you measure up to this heavy pressure as an IT organisation? How to you manage to be able to quickly make changes to software systems in fast paced environments, without losing grip on quality? How do you build and test software in such a way, that it's always in a releasable state?
In this talk, I'll explain the principles of Continuous Delivery. You'll leave the session with enough insights to get started yourself right away.
Large organisations will need CTOs to survive the digital revolution.
These CTOs will be former web developers, who know how to get things done on large architectures. Symfony developers will therefore be excellent candidates.
But with great power comes great responsibilities. Here are five important tips to keep in mind:
- stay lean
- be rational
- act as business leaders
- foster teamwork
- know that you know nothing
Good luck in your future responsibilities!
The Web moves fast, really fast. No one talks about what version of a web site you are using. Maybe you are using the beta version. Even then, it is always new. The Web is obsessed with new. It thrives on new. To meet this demand, in the early years of the web, teams learned a new way to deploy their software. Rather than the traditional models used by compiled, installed software, these pioneers on the Internet deployed software when it was ready. That meant Web sites could be responsive to changes, fix bugs quickly, and add new features to compete with the market. This method is still alive today. Successful web companies still do this to keep their advantage. While there are no set rules, there are good examples of what others do and how it helps them be successful.
The Wall Street Journal already mentioned it in 2011: “Software is eating the world”. The world is starting to discover that nowadays, every company is an IT company. Product owners and other business representatives are seeing their competitors release new features to end users every day, and are demanding the same from their own software teams.
How do you measure up to this heavy pressure as an IT organisation? How to you manage to be able to quickly make changes to software systems in fast paced environments, without losing grip on quality? How do you build and test software in such a way, that it's always in a releasable state?
In this talk, I'll explain the principles of Continuous Delivery. You'll leave the session with enough insights to get started yourself right away.
Large organisations will need CTOs to survive the digital revolution.
These CTOs will be former web developers, who know how to get things done on large architectures. Symfony developers will therefore be excellent candidates.
But with great power comes great responsibilities. Here are five important tips to keep in mind:
- stay lean
- be rational
- act as business leaders
- foster teamwork
- know that you know nothing
Good luck in your future responsibilities!
The Web moves fast, really fast. No one talks about what version of a web site you are using. Maybe you are using the beta version. Even then, it is always new. The Web is obsessed with new. It thrives on new. To meet this demand, in the early years of the web, teams learned a new way to deploy their software. Rather than the traditional models used by compiled, installed software, these pioneers on the Internet deployed software when it was ready. That meant Web sites could be responsive to changes, fix bugs quickly, and add new features to compete with the market. This method is still alive today. Successful web companies still do this to keep their advantage. While there are no set rules, there are good examples of what others do and how it helps them be successful.
Making Support Fun & Profitable: DrupalCon Portland Anne Stefanyk
After the site launches and the project is over, there are two paths: developers and project managers can shake client's hands, pat backs, and all head our separate ways. Or we can continue to build a relationship - continue being a part of our client's success. Strong long-term relationships benefit clients by providing trust and security, like a familiar mechanic or the barber we have had since we were a kid. As merchants, we also benefit. Happy clients mean referrals and recurring income.
Offering support is a different type of commitment, requiring a different strategy. A dev shop becomes a different type of service provider, and needs to prepare for great execution. This session will cover the why, how, and when of offering support, as well as exchange ideas about the many aspects: selling, marketing, staffing, delivering and monitoring support for Drupal.
Appealing to both the technical and non-technical, topics include:
- How to determine what type of support your clients need
- Organizing support requests, working within budgets and architecting timelines
- Workflow tactics and tools we love
- How to audit a site, understand it, and help it grow
- Best practices for your support development workflow
- Developer notes from the trenches- what you should know and look for
Come hear different perspectives on support and join the conversation!
Data Governance in an Agile SCRUM Lean MVP WorldDATAVERSITY
Most of us learned data modeling via a waterfall-driven methodology lens. Yet Agile and other modern development methods have for the most part assumed that data governance is an anti-pattern to just getting things (software) done. Well look at questions such as:
•Are Agile and Data Governance Enemies?
•How can we get stuff done AND get systems delivered?
•And what do we do about existing systems delivered without data governance attention?
We'll also look at how data modeling fits in the answers to these questions.
In the world of agile, there is theory and then there is practice. We like to talk about self-organizing teams, asynchronous execution, BDD, TDD, and emergent architecture. We also talk about cross-functional teams: how analysts, testers, architects, technical writers, and UX designers belong on the same team, right next to programmers. It all sounds nice in theory, but how does this work in reality? What do these people actually do? How do they interact? What does it look like? Is there really a pragmatic way to make this work?
In this simulation, a cross-functional team will actually build a piece of software. Every specialist will have a hand in the process. Every specialist will also act as a generalist. Everyone will add value. And as a team, we’ll get something DONE.
This is your opportunity to see agile development in practice, and to bridge the gap between what agilists say and what teams do. And it’s not as new or as difficult as you think – affinity between testers, BA’s, coders, and other team members has really been at the root of effective development practices all along. Let’s just finally acknowledge that it works, demonstrate its capabilities, and encourage it going forward.
This IS agile development.
General introduction to agile practices like Scrum and Kanban. Also covers what situations Agile is best at, what situations Agile doesn't help with, and what an Agile team should look like. This deck is a general intro to Agile for OpenSource Connections clients.
Антон Семенченко, опыт в IT более 10 лет, работает в компании ISSoft, специализируется в разработке и автоматизированном тестировании ПО плюс менеджмент\продажи. C++ Architect, Automation Practice Lead, PM, Group Manager
«Agile ValueTeam, учимся понимать Scrum». IT секция. Agile отделение. Для всех уровней подготовки.
«Как эффективно продавать Automation Service». IT секция. Продажи.
«Как эффективно организовать Автоматизацию, если у вас недостаточно времени, ресурсов и денег». Development секция. Отделение тестирования.
An Engineer’s Essential Tool in Agile: Design ThinkingSoniaMayPatlan
Many engineers are not connected to customers, resulting in solutions that lack high impact and benefit. But by combining design thinking with Agile, we create innovations that delight our customers. Find out, how a design thinking model called Design for Delight is applied within Agile frameworks to deliver thoughtful and inclusive solutions that can change the world.
10 bezcennych lekcji dla software developera stającego się szefem firmyWojciech Seliga
[Originally Polish lecture with English slides - with a few exceptions]
Przez wiele lat byłem software developerem. Koncentrowałem się na kodzie, projektach software'owych oraz interakcjach w moim zespole i z klientami. Byłem pewny, że Agile rozwiązuje wszystkie problemy tego świata. Śmiałem się z komiksów Scotta Adamsa i stworzonej przez niego karykatury szefa (PHB). Życie było proste i piękne...
Teraz od ponad 8 lat prowadzę firmę software'ową, którą przy blisko 90 osobach trudno już nazwać maleństwem. Sam stałem się "szefem" na pełen etat.
Podczas prezentacji podzielę się z Wami różnymi doświadczeniami oraz naukami (nieraz bolesnymi) jakie wyniosłem w ostatnich latach podczas mojej stopniowej przemiany z developera/inżyniera w przedsiębiorcę i szefa firmy. O ile zapewne nie wszystkie sytuacje i wnioski mają lub mogą mieć (o ile marzysz o własnym startupie czy zespole) zastosowanie w Twoim życiu, same sobie ich uświadomienie może oszczędzić Ci w przyszłości straty mnóstwa czasu, energii i pieniędzy oraz uniknąć przykrych rozczarowań.
A compilation of the absolute basics for those who want to know about Agile Methodology with some insights on Scrum. The idea is to give enough to fuel the curiosity to learn more. It might not interest one of he / she is an Agile guru but may I ask for your review / comments / suggestions. I'd love to hear from you all...
Enhancing Software Engineering Practices at Our Startup.pptxmuktar42
when I assumed the position of Director of Software Engineering at one of my previous early-stage startups, I swiftly recognized opportunities for enhancement. Reflecting on the initial presentation I delivered to the team, I find it holds significant value for startups in similar stages. In this reflective piece, I aim to revisit the insights shared during that pivotal moment, offering valuable lessons for budding startups.
Ten lessons I painfully learnt while moving from software developer to entrep...Wojciech Seliga
My presentation from InfoShare 2016 conference.
For many years I was a software developer. I would concentrate on the code, software projects and the interactions with my closes team and the users. I was sure that Agile solves all world’s problems. I would laugh over Scott Adam’s Dilbert comics with his Point Hair Boss. Life was simple, life was good. Now for 8+ years I have been running a software company, not a small one anymore. I became myself a full-time boss who only codes sometimes at home or during hackathons.
This session is about sharing with you those critical lessons which I painfully learnt when trying to grow into this new role - transitioning from being a software engineer into being an entrepreneur and top manager. Wheres not all of the lessons may or will (if you dream about your own startup) apply to your case, being aware of them may save you tons of time, energy, money or even help you to avoid the total disaster - burying your own company or dreams. And after all, sharing war stories from the past is fun … when these stories are the past.
Using Docker for local development is great due to the fast start-up speed and small footprint. It provides more open source projects while packaging the stacks as Docker images, speeding up the installation and collaboration.
A simple Drupal 7 to Drupal 8 Migration.
With its new prominent features, Drupal 8 will set the standards in terms of offering numerous ways to customise website content, display data on mobile devices and build API’s.
Due to the modern OOP (Object Oriented Programming) approach, it gives us a simpler migration process from its predecessor, with in-place content editing tools, along with a broad array of new themes.
Having an accessible website provides equal access and equal opportunity to people with disabilities. Providing an accessible website helps people with disabilities actively participate in society. Moreover, accessibility barriers in other media like print audio and visual can be overcome through an accessible Web. And last but not the least, web accessibility is required by laws and policies in some cases.
Drupal Continuous Integration and devops - Beyond JenkinsPromet Source
Drupal Continuous Integration and Condinuous Delivery - boyond DevOps and Jenkins. Our Journey from configuration management using chef to 10 steps of best practices of Drupal CI/CD
Drupal 8 Involvement with Promet SourcePromet Source
Promet Source's team reviews the importance on giving back to the Drupal 8 project by taking on issues from drupal.org and how anyone can contribute regardless of their experience.
Using Commerce License for Premium Content on Drupal SitesPromet Source
Does your Drupal site have premium content or files that live behind a paywall? Looking for a reliable, easy way to license that content to authenticated users?
Commerce License simplifies the process for granting access to premium content on local or remote sites for users.
Behavioral driven development with BehatPromet Source
This workshop helps developers to get started with the process of behavior driven development (BDD) in PHP using the Behat toolkit with Drupal specific extensions in order to align technical testing with business expectations when using Drupal as a development platform.
Composer tools and frameworks for DrupalPromet Source
This presentation from Drupal GovCon 2015 reviews the composer framework and toolkit for dependency management in Drupal. If your Drupal project is using PHP libraries outside of the Drupal ecosystem then you can benefit by adopting this powerful workflow today.
Responsive Design Testing the Promet WayPromet Source
Responsive web design demands flexibility from designers, developers and QA teams. This slideshow reviews the tools and methodology that Promet Source's QA team employs to see if a responsive design makes the cut for the latest browsers and operating systems.
Optimize and succeed your next Fixed Budget Project planning process Promet Source
Presentation given by @akucharski at the #14ntcdrupal non for profit conference drupal day in Washington DC. Tips on how to improve your chances of success for fixed budget projects. Covers the RFP process, contracting and terms, project planning and post project implementation maintenance.
Higher Ed Web 2013 presentation - Field of Dreams, build it and they will comePromet Source
Grinnell College in Iowa had a website that wasn’t representing the school well, and an intranet system that had been hijacked by users to bypass the main site. When tasked with redesigning the site, Grinnell needed to differentiate itself from its peers, and bring users back. Grinnell boasts rigorous academics, an active campus, and fantastic facilities, but many schools can claim the same. One differentiator is that Grinnell celebrates the individual. Through its welcoming culture of self-governance and the ability to create your own curriculum, the college empowers students to carve their own way through the college experience. It is not the only school that allows a student to do this, though it is one of the few.
So we asked: how do we distinguish Grinnell's unique take on crafting an individual education from its peers? How do we show the activities and news happening on campus? How does Grinnell bring users back from the intranet? How do we make as many departments as possible happy with a full redesign? And lastly, how do we best use Drupal to make it all happen? We decided to demonstrate it with a website that allows users to customize their experience on the site. Learn how Grinnell College, Promet Source (the developers) and Rogue Element (the design firm) worked together to create a customizable website: how Rogue designed it, how Promet built it and how Grinnell planned to use it.
Waterfall, Agile, Extreme Programming, Water-gile In this session we will discuss agile strategies that can help you get to done; efficiently, quickly and happier. I will cover the Scrum Framework concepts and some of the lessons learned from using agile strategy to manage a multinational distributed team. that does Drupal every day.
This session is for Managers and team members that want to learn more about agile strategies and how to apply them to Drupal.
Topics Covered
Where we all start, Waterfall.
Why agile is wrong, Agility is right.
Scrum Framework basics
What actions are Agile
What actions are not Agile
Lessons learned working with agile
Challenges of Scrum for small teams
Agility you can implement now
Project Estimation Presentation - Donte's 8th level of estimating level of ef...Promet Source
Johnnie Fox, Project Manager at Promet delivers this overview on web development project estimation, how to do it right and the pitfalls to watch out for.
DevOps for Drupal: Why We Cook With ChefPromet Source
DevOps for Drupal presentation given at DrupalCon 2013 in Portland. Promet Source shares secrets for automation and how to make your infrastructure hum.
Open Source Software: An Edge For Your Growing Business
DrupalCon 2013 Making Support Fun & Profitable
1. Building Bridges, Connecting Communities
Meghan Sweet, Anne Stefanyk,
Scott Massey, Michelle Krejci
Tuesday May 21, 2pm
Making Support Fun & Profitable
2. Introductions
Anne - Supporting the People in Support
Michelle - Onboarding & Auditing for Success
Meghan - Technical Support
Scott - Support Design & Management
9. Safety & Security
Clients: need to be able to trust you and
communicate effectively with the team
Developers: need a gatekeeper or someone
up the chain to turn to
16. Survey of 365 IT managers found that
of all projects:
- 16% successful
- 31% were impaired or cancelled
- 53% were deemed "project challenged"
The CHAOS report
18. - Content not available to Drupal, which
likes to manage that sort of thing.
- Does not scale.
- Theme lives inside content editor's head.
QUICK CHECK:
turn off the WYSIWYG and see what
happens.
22. If it is not immediately clear
what a custom module does,
it could mean a black hole
of support.
QUICK CHECK:
Sorry, there's not.
Run some scripts that check for complexity
and best practices.
Then try good 'ole looking at the code.
24. Uh oh.
This developer never read any
documentation ever.
Proceed with caution.
QUICK CHECK:
Look at what modules are enabled,
see if you can find them.
28. Until then...
Look for shops or contractors with a View-to-
Support mentality.
Have one yourself.
Put all config in code:
- Features
- Configuration
- Role Export, Block Export, Strongarm, etc.
Test your shit.
32. Its dynamic.
Timelines, budgets, servers,
core/contrib, team's abilities.
Deal with what you have and don't have
Stretching it only makes it worse later.
Drupal is an ecosystem
34. 01. Overriding your overrides
02. Abandoning modular structure
03. Adding more hastily
04. Coding rather than training
05. Scattering code
10 Drupal Diseases
35. 06. Features without a workflow
07. Patching without sharing
08. Not leaving a trail
09. High coupling
10. Ignoring api.drupal.org
10 Drupal Diseases
36. Follow the established
development philosophy
Play to your strengths and
client's true needs
Escalate when needed
Non-invasive procedures
37. What is sustainable?
Avoid technical debt
Both sites of the continuum are
right / wrong sometimes
Moral compass of technical
decision making
38. Most of response time is figuring out
what's broken.
Can I reproduce this reliability?
Analyze causes/effects.
Propose solution. Analyze cost/benefit.
Response time
39. Keep it simple, keep it sane.
Ideally your whole team can
deploy.
Drush aliases and ssh config
for the win.
Deployment
46. Design Specifics
“Do nothing that is of no use”
-Miyamoto Musashi
-No PM Workflow
-Can your SE draw the process?
-Get a PSA application
-Monitor & Automate
47. Contract Design
-Deliverables are "achievables"
-Risk is your guide for agreement type.
-Templates, not snowflakes
(menu: the vortex in atlanta)
49. Lightning Round & Questions
1. What do you love about support?
2. "I would do anything for [client] love, but I
won't do that."
3. What is your most awesome/needed tool?
4. What is your biggest challenge/success?
50. Building Bridges, Connecting Communities
Evaluate this session at:portland2013.drupal.org/
session/making-support-fun-and-profitableThank
you!
What did you think?