Boxes and Arrows

SEPTEMBER 2, 2013

The adoption of Agile software development approaches are on the rise across our industry, which means UX professionals are more likely than ever to support Agile projects. In 2009, I moved on to Salesforce.com, where Agile methods (including Scrum) were implemented across their entire research and development organization.

Agile 111

Agile Technical Review Software Review Development Team Review 111

Boxes and Arrows

JANUARY 31, 2010

Unfortunately, the enthusiasm I had for my new job waned after six months when an executive was appointed Head of Product Development—who insisted he knew SCRUM 1 better than anybody. As the Creative Director, I deferred authority to him to develop the product as he saw fit.

Agile 108

Agile Design Underperforming Technical Team Software 108

Planview

SEPTEMBER 12, 2023

The software development methodologies and organizational design principles harnessed by digital natives are well documented. Quantifying the Disconnect Between Business Leaders and Technology Teams Consider one of the most startling findings from The 2023 Project to Product State of the Industry Report.

Artificial Inteligence 72

Artificial Inteligence Data Roadmap Tools 72

Collective Innovation

AUGUST 14, 2017

Having a large amount of metrics available isn’t very helpful if people don’t know how to understand them. There is usually a wealth of trade magazines and if you work with dealers or distributors they are a fantastic resource for giving insight into what is doing well. Data Analysis.

Survey 40

Survey Artificial Inteligence Data Analysis 40

Boxes and Arrows

APRIL 15, 2009

Integrating Effective Prototyping into Your Design Process – Fred Beecher Senior User Experience Consultant Fred Beecher shows his audience how to determine what, for your particular situation, is the most effective way to use prototyping to improve the user experience of your site or software. Listening more than you speak.

Underperforming Technical Team 74

Underperforming Technical Team Design Conference Culture 74

Corporate Innovation

DECEMBER 17, 2015

These partnerships may take the form of Proof of Concept projects with startups, getting to know VC firms and their portfolios, and familiarizing themselves with university groups doing research in the established strategic problems. (It Stage 3: Productizing the Solution to Corporate Problems. What solution are we productizing?

Underperforming Technical Team 56

Underperforming Technical Team How To Innovation Disruption 56

Corporate Innovation

DECEMBER 17, 2015

These partnerships may take the form of Proof of Concept projects with startups, getting to know VC firms and their portfolios, and familiarizing themselves with university groups doing research in the established strategic problems. (It Stage 3: Productizing the Solution to Corporate Problems. What solution are we productizing?

Underperforming Technical Team 56

Underperforming Technical Team How To Innovation Disruption 56

Corporate Innovation

DECEMBER 17, 2015

These partnerships may take the form of Proof of Concept projects with startups, getting to know VC firms and their portfolios, and familiarizing themselves with university groups doing research in the established strategic problems. (It Stage 3: Productizing the Solution to Corporate Problems. What solution are we productizing?

Underperforming Technical Team 40

Underperforming Technical Team How To Innovation Disruption 40

Steve Blank

DECEMBER 17, 2015

These partnerships may take the form of Proof of Concept projects with startups, getting to know VC firms and their portfolios, and familiarizing themselves with university groups doing research in the established strategic problems. (It Stage 3: Productizing the Solution to Corporate Problems. What solution are we productizing ?

Underperforming Technical Team 35

Underperforming Technical Team How To Innovation Disruption 35

Boxes and Arrows

JUNE 29, 2009

However, designers should be aware of a wiki’s benefits and drawbacks for documentation, since UI specs uniquely reflect a project and its context. The documentation needs are often based on the size of the project, launch date, team dynamics, audience, technology, and the product development process.

Software Review 76

Software Review Technical Review Agile Software 76