This document promotes the website www.GrowingAgile.co.nz and Twitter handle @GrowingAgile, which are owned by Sam Laing. The website and Twitter profile provide information about agile practices and growing agile organizations.
Our top 10 team hacks to improve productivity and effectiveness of your team. Presented at Agile Testing Days 2017 by Karen Greaves and Sam Laing of Growing Agile
Growing Internal Agile Coaches and TrainersGrowing Agile
Presentation at #Agile2017 on how a small agile coaching company (Growing Agile) helped a large global corporate (ACI Worldwide) build their own internal agile coaches and trainers
Distributed Teams - Hello? Can anyone hear me?Growing Agile
In the ideal perfect world there will be rainbows and unicorns and teams that all sit together. In reality, most teams have to deal with distribution in one form or another. For some: it’s team members spread across a building, for others it’s team members in other parts of the world in different time zones.
Have you even been on a call where you can hear someone ordering coffee, or a dog barking? My favorite is being told someone is joining the call, after you've spent 5 minutes explaining something in detail. Mostly distributed meetings are boring, and not really worth the time and effort.
As agile coaches we truly value face to face communication and visible boards and sticky-notes, we also value working from anywhere, having pets in the office and not having to travel. So what is possible here? We decided to fully immerse ourselves into the distributed world and see what happened. We were amazed - we managed to build trust, explore and discover great collaborative tools and we improved communication.
We would like to share some of our discoveries and tips with you. Join us to explore how agile can work for distributed teams.
Are you struggling to integrate User Experience techniques with your agile teams? Are any of these patterns familiar?
The UX team works one sprint ahead of the development team.
UX designers spend lots of energy on high fidelity mock-ups which the developers then ignore.
You produce working software each sprint, but recruiting users is time consuming so you only test with users before you release.
There is no time to incorporate changes from user feedback into the sprints before release.
The UX designers and the developers seem to speak a different language.
Developers get annoyed because the UX design work great on iOS, but clashes with Android standards.
If so join us for a fun interactive session where we use Lego to explore how you can overcome challenges like this in your own environment. You’ll work as a team doing both UX design, and development (with Lego), and see how and why these patterns happen, as well as what you can do about them.
This workshop is ideal for people from both the UX world, struggling to understand how to work with developers, and for developers struggling to understand what UX designers are trying to achieve.
Our top 10 team hacks to improve productivity and effectiveness of your team. Presented at Agile Testing Days 2017 by Karen Greaves and Sam Laing of Growing Agile
Growing Internal Agile Coaches and TrainersGrowing Agile
Presentation at #Agile2017 on how a small agile coaching company (Growing Agile) helped a large global corporate (ACI Worldwide) build their own internal agile coaches and trainers
Distributed Teams - Hello? Can anyone hear me?Growing Agile
In the ideal perfect world there will be rainbows and unicorns and teams that all sit together. In reality, most teams have to deal with distribution in one form or another. For some: it’s team members spread across a building, for others it’s team members in other parts of the world in different time zones.
Have you even been on a call where you can hear someone ordering coffee, or a dog barking? My favorite is being told someone is joining the call, after you've spent 5 minutes explaining something in detail. Mostly distributed meetings are boring, and not really worth the time and effort.
As agile coaches we truly value face to face communication and visible boards and sticky-notes, we also value working from anywhere, having pets in the office and not having to travel. So what is possible here? We decided to fully immerse ourselves into the distributed world and see what happened. We were amazed - we managed to build trust, explore and discover great collaborative tools and we improved communication.
We would like to share some of our discoveries and tips with you. Join us to explore how agile can work for distributed teams.
Are you struggling to integrate User Experience techniques with your agile teams? Are any of these patterns familiar?
The UX team works one sprint ahead of the development team.
UX designers spend lots of energy on high fidelity mock-ups which the developers then ignore.
You produce working software each sprint, but recruiting users is time consuming so you only test with users before you release.
There is no time to incorporate changes from user feedback into the sprints before release.
The UX designers and the developers seem to speak a different language.
Developers get annoyed because the UX design work great on iOS, but clashes with Android standards.
If so join us for a fun interactive session where we use Lego to explore how you can overcome challenges like this in your own environment. You’ll work as a team doing both UX design, and development (with Lego), and see how and why these patterns happen, as well as what you can do about them.
This workshop is ideal for people from both the UX world, struggling to understand how to work with developers, and for developers struggling to understand what UX designers are trying to achieve.
How to make your team 5 times more productiveGrowing Agile
A talk for the Product Meetup group, aimed at helping Product Managers and Product Owners make their teams more productive.
We share our top tips in this talk. Each tip is something we’ve personally tried with several teams and seen significant improvements in productivity and morale as a result.
ScrumMaster to Agile Coach ... Where is the map?Growing Agile
This was a workshop run at #SGPRG (Scrum Gathering Prague) to co-create a map for ScrumMasters to follow. The map will be uploaded here: www.agilepath.me
In this presentation we will look at the agile testing mindset and how it is different from traditional testing. We will look at each of these statements in turn, as well as an exercise to illustrate the impact of testing early. We will also share some techniques for you to use with each of these statements.
7 tips for managing software development in the age of agileGrowing Agile
Seven tips to focus on as the leader or manager of agile teams. This talk was given at the ITWEB conference in 2015 in South Africa and at #SGPRG (Scrum Gathering Prague)
Agile Management: The Art of Servant LeadershipGrowing Agile
Are you an Agile Manager? What does that mean anyway? Agile managers focus on growing their people and helping them be the best they can be. We touch on several areas and suggest a course to learn more.
https://www.udemy.com/gac-servantleadership/?couponCode=GASlideshare
Scrum Gathering South Africa 2014 Closing Keynote: My Scrum OdysseyGrowing Agile
Karen Greaves delivered the closing keynote for the 2014 Scrum Gathering in Cape Town. She shared her personal agile journey as well as the journey of the Scrum community in South Africa over the last 12 years.
Senior Project and Engineering Leader Jim Smith.pdfJim Smith
I am a Project and Engineering Leader with extensive experience as a Business Operations Leader, Technical Project Manager, Engineering Manager and Operations Experience for Domestic and International companies such as Electrolux, Carrier, and Deutz. I have developed new products using Stage Gate development/MS Project/JIRA, for the pro-duction of Medical Equipment, Large Commercial Refrigeration Systems, Appliances, HVAC, and Diesel engines.
My experience includes:
Managed customized engineered refrigeration system projects with high voltage power panels from quote to ship, coordinating actions between electrical engineering, mechanical design and application engineering, purchasing, production, test, quality assurance and field installation. Managed projects $25k to $1M per project; 4-8 per month. (Hussmann refrigeration)
Successfully developed the $15-20M yearly corporate capital strategy for manufacturing, with the Executive Team and key stakeholders. Created project scope and specifications, business case, ROI, managed project plans with key personnel for nine consumer product manufacturing and distribution sites; to support the company’s strategic sales plan.
Over 15 years of experience managing and developing cost improvement projects with key Stakeholders, site Manufacturing Engineers, Mechanical Engineers, Maintenance, and facility support personnel to optimize pro-duction operations, safety, EHS, and new product development. (BioLab, Deutz, Caire)
Experience working as a Technical Manager developing new products with chemical engineers and packaging engineers to enhance and reduce the cost of retail products. I have led the activities of multiple engineering groups with diverse backgrounds.
Great experience managing the product development of products which utilize complex electrical controls, high voltage power panels, product testing, and commissioning.
Created project scope, business case, ROI for multiple capital projects to support electrotechnical assembly and CPG goods. Identified project cost, risk, success criteria, and performed equipment qualifications. (Carrier, Electrolux, Biolab, Price, Hussmann)
Created detailed projects plans using MS Project, Gant charts in excel, and updated new product development in Jira for stakeholders and project team members including critical path.
Great knowledge of ISO9001, NFPA, OSHA regulations.
User level knowledge of MRP/SAP, MS Project, Powerpoint, Visio, Mastercontrol, JIRA, Power BI and Tableau.
I appreciate your consideration, and look forward to discussing this role with you, and how I can lead your company’s growth and profitability. I can be contacted via LinkedIn via phone or E Mail.
Jim Smith
678-993-7195
jimsmith30024@gmail.com
How to make your team 5 times more productiveGrowing Agile
A talk for the Product Meetup group, aimed at helping Product Managers and Product Owners make their teams more productive.
We share our top tips in this talk. Each tip is something we’ve personally tried with several teams and seen significant improvements in productivity and morale as a result.
ScrumMaster to Agile Coach ... Where is the map?Growing Agile
This was a workshop run at #SGPRG (Scrum Gathering Prague) to co-create a map for ScrumMasters to follow. The map will be uploaded here: www.agilepath.me
In this presentation we will look at the agile testing mindset and how it is different from traditional testing. We will look at each of these statements in turn, as well as an exercise to illustrate the impact of testing early. We will also share some techniques for you to use with each of these statements.
7 tips for managing software development in the age of agileGrowing Agile
Seven tips to focus on as the leader or manager of agile teams. This talk was given at the ITWEB conference in 2015 in South Africa and at #SGPRG (Scrum Gathering Prague)
Agile Management: The Art of Servant LeadershipGrowing Agile
Are you an Agile Manager? What does that mean anyway? Agile managers focus on growing their people and helping them be the best they can be. We touch on several areas and suggest a course to learn more.
https://www.udemy.com/gac-servantleadership/?couponCode=GASlideshare
Scrum Gathering South Africa 2014 Closing Keynote: My Scrum OdysseyGrowing Agile
Karen Greaves delivered the closing keynote for the 2014 Scrum Gathering in Cape Town. She shared her personal agile journey as well as the journey of the Scrum community in South Africa over the last 12 years.
Senior Project and Engineering Leader Jim Smith.pdfJim Smith
I am a Project and Engineering Leader with extensive experience as a Business Operations Leader, Technical Project Manager, Engineering Manager and Operations Experience for Domestic and International companies such as Electrolux, Carrier, and Deutz. I have developed new products using Stage Gate development/MS Project/JIRA, for the pro-duction of Medical Equipment, Large Commercial Refrigeration Systems, Appliances, HVAC, and Diesel engines.
My experience includes:
Managed customized engineered refrigeration system projects with high voltage power panels from quote to ship, coordinating actions between electrical engineering, mechanical design and application engineering, purchasing, production, test, quality assurance and field installation. Managed projects $25k to $1M per project; 4-8 per month. (Hussmann refrigeration)
Successfully developed the $15-20M yearly corporate capital strategy for manufacturing, with the Executive Team and key stakeholders. Created project scope and specifications, business case, ROI, managed project plans with key personnel for nine consumer product manufacturing and distribution sites; to support the company’s strategic sales plan.
Over 15 years of experience managing and developing cost improvement projects with key Stakeholders, site Manufacturing Engineers, Mechanical Engineers, Maintenance, and facility support personnel to optimize pro-duction operations, safety, EHS, and new product development. (BioLab, Deutz, Caire)
Experience working as a Technical Manager developing new products with chemical engineers and packaging engineers to enhance and reduce the cost of retail products. I have led the activities of multiple engineering groups with diverse backgrounds.
Great experience managing the product development of products which utilize complex electrical controls, high voltage power panels, product testing, and commissioning.
Created project scope, business case, ROI for multiple capital projects to support electrotechnical assembly and CPG goods. Identified project cost, risk, success criteria, and performed equipment qualifications. (Carrier, Electrolux, Biolab, Price, Hussmann)
Created detailed projects plans using MS Project, Gant charts in excel, and updated new product development in Jira for stakeholders and project team members including critical path.
Great knowledge of ISO9001, NFPA, OSHA regulations.
User level knowledge of MRP/SAP, MS Project, Powerpoint, Visio, Mastercontrol, JIRA, Power BI and Tableau.
I appreciate your consideration, and look forward to discussing this role with you, and how I can lead your company’s growth and profitability. I can be contacted via LinkedIn via phone or E Mail.
Jim Smith
678-993-7195
jimsmith30024@gmail.com
Artificial intelligence (AI) offers new opportunities to radically reinvent the way we do business. This study explores how CEOs and top decision makers around the world are responding to the transformative potential of AI.
The case study discusses the potential of drone delivery and the challenges that need to be addressed before it becomes widespread.
Key takeaways:
Drone delivery is in its early stages: Amazon's trial in the UK demonstrates the potential for faster deliveries, but it's still limited by regulations and technology.
Regulations are a major hurdle: Safety concerns around drone collisions with airplanes and people have led to restrictions on flight height and location.
Other challenges exist: Who will use drone delivery the most? Is it cost-effective compared to traditional delivery trucks?
Discussion questions:
Managerial challenges: Integrating drones requires planning for new infrastructure, training staff, and navigating regulations. There are also marketing and recruitment considerations specific to this technology.
External forces vary by country: Regulations, consumer acceptance, and infrastructure all differ between countries.
Demographics matter: Younger generations might be more receptive to drone delivery, while older populations might have concerns.
Stakeholders for Amazon: Customers, regulators, aviation authorities, and competitors are all stakeholders. Regulators likely hold the greatest influence as they determine the feasibility of drone delivery.
Specific ServPoints should be tailored for restaurants in all food service segments. Your ServPoints should be the centerpiece of brand delivery training (guest service) and align with your brand position and marketing initiatives, especially in high-labor-cost conditions.
408-784-7371
Foodservice Consulting + Design
The Team Member and Guest Experience - Lead and Take Care of your restaurant team. They are the people closest to and delivering Hospitality to your paying Guests!
Make the call, and we can assist you.
408-784-7371
Foodservice Consulting + Design
Raise your hands if you said or heard any of the following:
Testing is about:
checking the system
finding bugs
Trying to break the system
Testers are responsible for quality
Testing is a phase after development
Today I am going to show you how agile testing is none of these things
Let’s look at testing as a phase.
How many of you have boards like this with a test column after the dev column?
This is traditional thinking
In agile testing is an activity that takes place THROUGHOUT
It’s just another task.
A great tip is to use different coloured stickies for test tasks and try to get them done first.
Even if you don’t do TDD, get the tester to brainstorm what they are going to test before any code gets written
A great technique is the show me column.
Most teams do code reviews, and usually the last task to get done
Instead review every task, dev and test by showing someone else on the team
Drives shared knowledge, identifiies and fixes issues faster
Bugs are more expensive the later you fix them, using this you can fix them within hours of them being introduced.
Now lets talk about finding bugs
How many of you measure tester performance based on the number of bugs they find
Or how about the number they don’t find that are found in the wild?
Consider this star
Can you work out how many points it has?
Write down your answer
How many of you wrote down something other than 5?
If this was code, we just found a bug
How could we prevent that bug?
What if we told you this was one point, and this was not a point
How many of you would have written down 5.
Asking a few questions before you assumed what we meant would have prevented bugs
By asking questions early, before code is written you can prevent bugs
Focus on making sure the whole team has a shared understanding before any code gets written
Often teams make assumptions in planning. Don’t
Ask even the most stupid questions. If it’s not clear to you, it’s not clear to everyone
Make sure everyone leaves the room with the same picture in their mind
6 month report story
Most testers we know, explain there jobs by saying the check stuff
Does the system work
Does it meet the spec
Does 1 + 1 = 2
You know what’s really good at checking stuff? Computers!
If it’s a simple check – automate it. Free up testers from checking
Best way to automate – testers write test cases, devs write fixture.
Put the two together and you have an functional level test before any code is written.
So if tester’s aren’t checking what should they be doing?
Understanding the user needs, making sure they system that is built will solve a real business need
Do exploratory testing that computers suck at and giving feedback on how the system behaves
Most importantly ask “how can you test it”
People who do TDD know that code written this way is designed to be testable.
Testers should help by asking how can we test this up front.
Many testers are proud of their ability to break stuff
But lets face it broken systems don’t help anyone.
Instead of a blame game between dev and test it’s more useful to collaborate
Testers and developers should be working together to build the best possible system. Not trying to catch each other out.
Tell Maersk Story – if we show you the acceptance tests you might just build a system that makes them pass !
Testers tell developers how you will test it before they build it, chances are they will build it right.
Often testers are seen as the owners of the quality gate
They alone get to say if something is ready for release
Often they seem dead against products being released, mostly because they will be blamed if quality is not good
In agile the whole team is repsonsible
Testers aren’t the last people in the chain anymore, they are just part of a team taking pride in their work
To summarise the agile testing mindset is about:
Testing as an activity not a phase
Prevent bugs rather than finding them
Being a tester give feedback not a checker
Helping to build rather than breaking
The team being responsible for quality not just the tester
We’d like to leave you with my top 3 tips to make your testing more agile
We’ll be around tonight and tomorrow if you have questions