Remove Collaboration Remove Development Team Review Remove Product Development Remove Training
article thumbnail

The UX Professionals’ Guide to Working with Agile Scrum Teams

Boxes and Arrows

In 2009, I moved on to Salesforce.com, where Agile methods (including Scrum) were implemented across their entire research and development organization. Many of the problems they reported indicated that both UX professionals and technical staff lacked a shared understanding of each others’ team roles and responsibilities.

Agile 111
article thumbnail

How to market a new product to the new generation of first time leaders?

Be-novative

With that said, tailor-made feedback and future-proof assessments are vital when it comes to first-time managers. We help to turn your team from the most common denominator of “average” into superhero’. Gathering knowledge and best practices through Collaborative Learning ??

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Atelier Louis Zero: Spot, Play, Go,… Zero!

Innovation Excellence

After working in the tourism industry and language training in B2B, she took her nunchaku to shake up the world of innovation! She naturally joined Louis Zero’s team as Shake my Firm project manager and then took on the development of Louis Zero workshop as a whole. Training can also be fun and immersive !

article thumbnail

Atelier Louis Zero: Spot, Play, Go,… Zero!

Innovation Excellence

After working in the tourism industry and language training in B2B, she took her nunchaku to shake up the world of innovation! She naturally joined Louis Zero’s team as Shake my Firm project manager and then took on the development of Louis Zero workshop as a whole. Training can also be fun and immersive !

article thumbnail

Control and Community: A Case Study of Enterprise Wiki Usage

Boxes and Arrows

Wikis introduce to the Internet a collaborative model that not only allows, but explicitly encourages, broad and open participation. We needed to spread the load so that a broad range of developers, tech writers, professional service consultants and others could all contribute what time and knowledge they had to a shared goal.