1. Agile Product Management Craftsmanship
Steven Davidson II
Senior Manager IT Ascena Retail

3. Session Details Why should a Product Manager become more technical?
Low hanging fruit to be more technical
Analytics
Interactive Prototyping
Understanding Technology Stacks
How prioritization and planning is improved
How Speed to Market is improved
Common pitfalls to avoid
Closing / Takeaways
With agile we have found that when technical resources become more business savvy, stronger solutions are architected and built. Now we are seeing that having technical savvy Product Managers leads to better communication with their teams and ultimately better products.  What small technical investments can a Product Manager make to better collaborate with their team?

4. Session Details Why should a Product Manager become more technical?
Low hanging fruit to be more technical
Analytics
Interactive Prototyping
Understanding Technology Stacks
How prioritization and planning is improved
How Speed to Market is improved
Common pitfalls to avoid
Closing / Takeaways

6. Session Details Low hanging fruit to be more technical
Why should a Product Manager become more technical?
Low hanging fruit to be more technical
Analytics
Interactive Prototyping
Understanding Technology Stacks
How prioritization and planning is improved
How Speed to Market is improved
Common pitfalls to avoid
Closing / Takeaways

7. Session Details Analytics
Why should a Product Manager become more technical?
Low hanging fruit to be more technical
Analytics
Interactive Prototyping
Understanding Technology Stacks
How prioritization and planning is improved
How Speed to Market is improved
Common pitfalls to avoid
Closing / Takeaways

12. Why?
Provides you and your team with hard data that allows you to make smart decisions that help your company and your customers.

13. Session Details Interactive Prototyping
Why should a Product Manager become more technical?
Low hanging fruit to be more technical
Analytics
Interactive Prototyping
Understanding Technology Stacks
How prioritization and planning is improved
How Speed to Market is improved
Common pitfalls to avoid
Closing / Takeaways

17. Why?
Helps provide visual and interactive clarity to the product you want built. It also provides an interactive mockup that can be used for early user testing.

18. Session Details Understanding Technology Stacks
Why should a Product Manager become more technical?
Low hanging fruit to be more technical
Analytics
Interactive Prototyping
Understanding Technology Stacks
How prioritization and planning is improved
How Speed to Market is improved
Common pitfalls to avoid
Closing / Takeaways

21. Why?
Allows for you and your technical team to have better discussions about the time needed and the needed investments to provide key features to your customers.

22. Session Details How prioritization and planning is improved
Why should a Product Manager become more technical?
Low hanging fruit to be more technical
Analytics
Interactive Prototyping
Understanding Technology Stacks
How prioritization and planning is improved
How Speed to Market is improved
Common pitfalls to avoid
Closing / Takeaways

23. Prioritization and Planning Improvements
Feature breakdown at the product management level is improved
Feature
Story
Task

25. Session Details How Speed to Market is improved
Why should a Product Manager become more technical?
Low hanging fruit to be more technical
Analytics
Interactive Prototyping
Understanding Technology Stacks
How prioritization and planning is improved
How Speed to Market is improved
Common pitfalls to avoid
Closing / Takeaways

26. Speed to Market Improvements
Optimize and adjust your product roadmap based on an understanding of technical trends in your industry and user base

27. Session Details Common pitfalls to avoid
Why should a Product Manager become more technical?
Low hanging fruit to be more technical
Analytics
Interactive Prototyping
Understanding Technology Stacks
How prioritization and planning is improved
How Speed to Market is improved
Common pitfalls to avoid
Closing / Takeaways

30. Session Details Closing / Takeaways
Why should a Product Manager become more technical?
Low hanging fruit to be more technical
Analytics
Interactive Prototyping
Understanding Technology Stacks
How prioritization and planning is improved
How Speed to Market is improved
Common pitfalls to avoid
Closing / Takeaways

31. Improved Interactions
Team
&
Customers

35. Equals
Happier Team
&
Happier Customers

36. Happier Product Manager

37. Questions and Answers