Practice how you can effectively tailor agile for planning your work, doing daily stand-ups with Scrum/Kanban boards, gathering feedback with product reviews/demos, and improving your way of working with agile retrospectives.
Learn how to apply agile practices with an agile mindset.
Increase your ability to pick those practices that help you to do a better job and collaborate better with your stakeholders.
The workshop is loaded with examples and suggestions to help you become more agile and lean.
Leadership is not as much style as it is authenticity. Many leaders believe leadership is acting and you are one way at work and their true self emerges outside of work.
Every leader needs to be themselves, develop their own leadership style. We cannot take another leader’s style and personality as our own. We should be our own leader not act as a persona of someone else’s style.
As an Authentic leader, your team readily follows you, your organization steadily grows and you influence a positive culture.
For us to be successful leaders, we need to show up as our authentic self’s so that we can be true leaders. Based on the work done by Bill George, the creator of the “authentic leadership” approach to management, this workshop will explore the importance of your authentic self, its impact on your leadership style, 4 traits of authentic leaders and provide 5 recommended steps towards your own authentic leadership.
Why Velocity alone is a poor indicator Forecasting with Probability How to create and read a CFD Methods for measuring team flow and process Simple ways to measure code quality Using metrics to inform and improve your process.
Mob Programming: All the brilliant people working on the same thing, at the same time, in the same place, and on the same computer. Mob Programming is a cost-effective, collaborative and fun way to get work done together.
It’s a whole-team approach to development, where coding, designing, testing, and working with the “customer” (partner, Product Owner, User, etc.) is all done as a team.
Refactoring is easy; the theories have been written and even automated in your tools. Yet many of us still have to work every day with ugly code and large amounts of technical debt. When faced with large code bases, we feel unable to begin and often fall back to the old excuse “that won’t work here.”
It’s time to get real. We are going to take a 300 line ball of mud, and show some new approaches and techniques so that you can actually start using those automated refactorings in your IDE to start safely changing your code little by little.
1. Make work visible to find bottlenecks, risks and issues
2. Optimize team workflow
3. Explain what work-in-progress (WIP) has to do with time-to-market.
4. Optimize workflow across the whole Value Stream
5. Identify benefits of managing by product versus managing by project.
Note: As the event organizer, we hold the right to cancel or change any talk or workshop especially if forced to do so (due to 3rd party, safety or security reasons). We will always do our best to assure any replacement with equivalent interest and engagement.