Your New Bottom Line – Delighting Your Customers
Wednesday, July 27 @ 3:45 pm, Learning Center
Organizations today want to be more responsive to their marketplace opportunities, more productive and more efficient; they want to be agile. Many have implemented agile practices for improving software development. But if you want to really make a difference it requires leadership that emphasizes creating, satisfying and delighting customers every day.
This session focuses on leadership and tactical techniques for delighting your customers that you can take back and put to use. You will learn how a culture of delighting customers is built around a work force characterized by high levels of productivity, continuous innovation, and elevated levels of sustained motivation and job satisfaction.
Your customers are your lifeblood; it’s not enough just to satisfy them, you need to delight them. You need them sharing their delight with others, sharing opportunities with you, and coming back again and again.
Make it your new bottom line! Focus your organization on delighting your customers. Your customers will love you and so will your shareholders. It’s hard work but immensely rewarding.
- Understand the importance of delighting your customers through collaboration and always generating value.
- Learn how a culture of delighting customers is built around, and compliments, a highly motivated workforce.
- Acquire techniques for delighting customers you can put to use now.
- Learn that delighting customers applies to everyone. Apply the concepts as a way of thinking for software development and scale it to running your organization.
- See how customer delight can drive your financial performance.
- Sharpen your leadership focus on delighting customers; make it your new bottom line.
Emergent Architecture – Just Enough Just in Time
Thursday, July 28 @ 3:45 pm, Inman
With Scrum and other forms of agile software development we focus on incrementally evolving architecture one sprint or iteration at a time and avoid the potential waste of big design up front. What’s this really mean? We’ll talk about pragmatically doing just enough just in time while delivering a potentially shippable increment of working software every sprint.
So where and when do we plan, and how much? What about the big picture? How does our architecture fit within the enterprise? How does it facilitate our business objectives? How do we manage risk? And, what about all the details? What tools are we using, what standards are we adhering to, how are we managing maintainability and all the other NFR’s? Is everything integrating together nicely? And, what is role of the solution/enterprise architect in an agile world?
This session is all about helping you understand architecture in the world of today’s agile software development.
- Emergent Architecture is an important part of agile development
- Deliver business value each Sprint
- Big design up front is waste, do just enough just in time
- Delay requirements until last responsible moment
- Architects are active members of the development teams
- Work in slices rather than layers
- Choose popular principles, patterns, practices
- Know when you are done
- It takes smart developers to write software