*** Please review the MISO security procedures observed for this Meetup session ***
Abstract: Technical Excellence, You Need It
Whether you are a manager, scrum master or engineer, you need to know why and how the technical practices of test-driven development, refactoring, continuous design, clean code and automated testing can help you and your organization be great.
Technical excellence is more than two week sprints, a burn-down chart and a daily stand-up meeting. The basic rules of Agile or Scrum are not an end in themselves, but a starting point based upon principles and practices that allow and encourage teams to adopt, adapt, and refine their craft. Unfortunately, it may seem to the technical people that agile is just another micro-management approach.
Extreme Programming with its provocative name, got people’s attention in 1999. It is based on sound technical practices. Why do so few agile teams employ engineering practices that support the tight iterative cycles of Agile and Scrum? The creators of Scrum expected the continuous improvement cycle to pull engineering practices into teams once the cycle revealed the problems of poor product quality, hard to change code, wasted time debugging, long stabilization efforts and the ever growing burden of manual test. This talk will cut through the mystery and show why we should all strive for Technical Excellence.
Keynote Learning Outcomes
The intention of Scrum’s creators
The reality of the current state of Agile/Scrum
Specific reasons to improve engineering practices
The importance of automation, and consequences of not automating
How TDD prevents defects and wasted time (TDD vs Debug Later Programing)
Unit Test Imperative
Test automation vs. the untested code gap
The importance of code quality, and consequences of not keeping code clean
The three critical skills of Refactoring
Excuses for not improving engineering practices
Technical excellence to do list for Managers, Scrum Masters and Developers
About the Speaker:
James Grenning trains, coaches and consults worldwide. James’ mission is to bring modern technical and management practices to to product development teams, especially embedded systems development. He is the author of Test-Driven Development for Embedded C (http://wingman-sw.com/tddec). He is a co-author of CppUTest, a popular unit test harness for embedded C and C++. He invented Planning Poker, an estimating technique used around the world, and participated in the creation of the Manifesto for Agile Software Development. His website is http://wingman-sw.com.
• 5:30pm: Doors open - Registration, Networking, Food
• 6:00pm: Welcome and Intro
• 6:30pm: Featured Speaker
• 7:45pm: Wrap-up and Raffle
• 8:00pm: Adjourn - Post meeting networking & cocktails
• What to bring
• Important to know
*** Meeting at MISO Security Procedures ***
We are still working through some of the details with MISO regarding new security procedures in development at MISO. For this month;
1) Please register if you are attending the meeting. Registration will be closed on Tuesday, 12Jun2018 at 12 Noon. There will be no walk-ins permitted
2) The Meetup registration list will be provided to MISO security as a checklist. You will need to sign-in when you arrive and sign-out when you depart for the evening.
3) You will be asked to produce a picture ID for the MISO security as part of the verification process to confirm the registration.
4) By 8:30P everyone will need to be out of the building and leave the MISO parking lot. No loitering in the parking lot.
Make your way to the storypoint location for those after meeting discussions.
Claim the event and start manage its content.I am the organizer