Join us Tuesday, March 3rd, where Peter will talk about how how to optimize your backlog to deliver the most impact.

Doors open at 5:30, presentation starts at 6:00 at the Nintex, in Bellevue.

Linking Strategy to Execution: Designing Business Value into the Backlog

Many organizations complain about the chasm between business stakeholders and software development teams. Improved requirements, planning, and project management controls help you deliver on promise, but they often fall short when it comes to prioritizing what to build. In this talk, Peter will show how to use design practices to increase innovation, autonomy, team health, and generate more business value in the backlog.

Peter Moon is a Managing Partner at Navicet, a design consultancy that helps teams develop design capabilities into a competitive advantage.

Peter has over 30 years of commercial software design and IT management experience.

He is a 13 year veteran of Microsoft and held such positions as Director of Tools for North America Services, Engineering PUM, Quality Director, and Consulting Engagement Manager where he drove some of the largest services engagements in North America.

While at Microsoft, Peter developed new practices for IT software design and drove global adoption for over 10,000 IT pros. He has been a speaker at numerous industry conferences, has coached hundreds of teams to achieve better business results through proven practices in design, requirements, risk and project management and has served on Microsoft IT’s Architectural and Standards review boards. 
 
Peter launched Navicet with a group of like-minded practitioners in 2014 to serve customers in the Puget Sound area who believe in the power of design to transform business.

More about SeaSPIN.

Tuesday, September 16, 2014, at the T-Mobile Technology Meetup.

By settling on the right measures at the beginning of the project the team gains greater autonomy, innovation, and positive impact for delivery. A simple set of questions can be used to surface hidden assumptions and create clear, meaningful goals for the entire project team and stakeholders. Peter will share some pragmatic approaches to ensure that this vision serves the project team every day, from prioritizing your backlog, minimizing risk through early testing and informing tradeoff decisions. Here are a few things you can expect to take away from this talk:

• How to create a more responsive, effective team.

• Increase stakeholder satisfaction and deliver more business value.

• Build better backlogs based on effort, benefit and dependencies. 

If you plan on attending this free event, please RSVP at the meetup.com event site.

We'll see you there.

Join us August 5th where Peter will be speaking on collaborative design and innovation.

Doors open at 5:45, presentation starts at 6:30 at the Rally Development offices: 135 Lake St South, Suite 100, Kirkland, WA 98033. It's just up the steps on the first floor of the gray building opposite Ben & Jerry's. Parking on the street or in any nearby lot you can find.

Collaborative Design as a Practice: Five Principles for Fueling Innovation

When Apple's iPod turned the mobile music player market upside down, businesses, non-profits and governments started asking themselves whether Design, which proved so remarkably effective for products, could be applied to other domains, like process, strategy, business automation or organizations. Design thinking and design practices continue to hold great appeal, but the benefits have proved elusive. Many proven design practices, such as brainstorming, prototyping and user testing are incompatible with the sensibilities and conventions of traditional business processes, such as a bias for predictability, governance and analytical thinking.

Building and managing a design capability turns out to be anything but obvious. In this talk, Peter shares a pragmatic model for design and shows how it can flourish in conventional organizations to improve collaboration, agility and creativity.

More about SeaSPIN here.

We all know business value is important, but how do you measure it? Higher revenue and lower costs are easy to describe in dollars, but what about customer loyalty, corporate or regulatory compliance, innovation and risk management? Exactly how does architecture contribute to the goals of an organization and what’s the best way to measure that contribution? Share your ideas, opinions and experience. - See more and register at IASA