Planview

MARCH 20, 2023

Five years ago, Planview CTA Mik Kersten outlined the “turning point” in his bestselling book, Project to Product: How to Thrive and Survive in the Age of Software with the Flow Framework. Incorporating Flow Metrics and business outcomes into regular operational reviews has been proven to increase the likelihood of operationalizing the shift.

Project 52

Project Technical Review Software Review Survey 52

Planview

MAY 3, 2023

You’ve implemented agile ways of working at a team level, but as an enterprise, you’re still slow to market and are having trouble reacting to changes. Blumhorst and Derbyshire suggest that, when considering what software solution to use, whether PPM or PSAAs, you must first think about your desired internal and external outcomes.

Software Review 52

Software Review Project Software Roadmap 52

Leapfrogging

APRIL 15, 2024

Adaptability and responsiveness are key outcomes of collaborative teams, which are essential for thriving in an era of continuous change. Clear objectives act as a roadmap, guiding the team’s efforts and helping to measure success. Goals should be specific, measurable, achievable, relevant, and time-bound (SMART).

Collaboration 100

Collaboration Software Review Tools Technical Review 100

Planview

APRIL 6, 2023

The data measures the flow of business value through all the activities involved in a software value stream. This debunks the perspective that business agility and successful transformation are limited to companies of a certain profile. Some of them would take this report and turn it into their roadmap on what to get right first.

Competition 52

Competition Technical Review Software Review Agile 52

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. I first encountered Agile Development in 2005, when a team I supported was chosen to help pilot Scrum development methodology at Yahoo!

Agile 111

Agile Technical Review Software Review Development Team Review 111

Huub Rutten

FEBRUARY 23, 2021

There are so many layers between the Board room and for example a software developer or an industrial designer. Note: this risk is per definition embedded in several Agile methodologies. ( Note: this risk is per definition embedded in several Agile methodologies. Agile gives a lot of power to the developers, the shop floor.).

Management 52

Management Fractional CTO Technical Review Roadmap 52

Huub Rutten

FEBRUARY 23, 2021

There are so many layers between the Board room and for example a software developer or an industrial designer. Note: this risk is per definition embedded in several Agile methodologies. ( Note: this risk is per definition embedded in several Agile methodologies. Agile gives a lot of power to the developers, the shop floor.).

Management 52

Management Fractional CTO Technical Review Roadmap 52

Huub Rutten

FEBRUARY 23, 2021

There are so many layers between the Board room and for example a software developer or an industrial designer. Note: this risk is per definition embedded in several Agile methodologies. ( Note: this risk is per definition embedded in several Agile methodologies. Agile gives a lot of power to the developers, the shop floor.).

Management 52

Management Fractional CTO Technical Review Roadmap 52

Ecosystems4Innovating

SEPTEMBER 1, 2023

They are fundamentally changing the way organizations are undertaking their businesses. Add in software to direct and help facilitate discovering, buying and selling, payments, service fulliment and final delivery. Organizations constantly search for Agility and Flexibility: A marketplace approach allows for agile evolution.

Design 64

Design Agile Software Review Technical Review 64

ITONICS

JUNE 7, 2019

Agility of Strategy. Except for M&A, which typically needs longer timeframe due to regulatory reasons, all other 10 practices are carried out more frequently by top performers than by the rest of the companies in the survey pool. As a result, adequate resources must be provided to the most beneficial innovation projects.

Strategy 50

Strategy Strategy Software Review Technical Review 50

Idea to Value

SEPTEMBER 7, 2021

To get the outcomes the executives are expecting from innovation, they’d need to build an agile organization where innovation happens at scale. As so many organizations are embarking on this journey towards becoming more innovative and agile, there’s unfortunately a lot of fake agile and innovation theater out there.

Agile 302

Agile Innovation Technical Review Leadership 302

Boxes and Arrows

NOVEMBER 17, 2015

In-house designers often have to advocate for design priorities versus new features or technical change. Meaning anyone who provides the vision for a product, whether it be in code, wireframes, comps, prototypes, or cocktail napkins. Did it instigate change? The roadmap doesn’t just benefit the project team or the designer.

Underperforming Technical Team 94

Underperforming Technical Team Software Review Roadmap Design 94

Paul Hobcraft

MARCH 15, 2016

The subject was the changes occurring at the front end of innovation. My argument was the results we have obtained from a disconnected set of front end activities was poorer than they should be and this needs changing. The software solutions I allude too, well those clients interested or curious enough can contact me.

Software Review 100

Software Review Innovation Software Engagement 100

hackerearth

SEPTEMBER 29, 2017

This requires a talented ‘innovation team’ – the right synthesis of strategists, technologists, and communicators - to lead this fundamental change and operate at the core of the ‘innovation machine’; to introduce the new culture , to inspire teams and drive innovation by example. Team Responsibilities. Measure, Assess, Adjust.

Technical Review 68

Technical Review How To Software Review Ideation 68

Innovation in Practice

AUGUST 8, 2016

In Cragun and Sweetman's upcoming book, Reinvention: Accelerating Results in the Age of Disruption [Greenleaf Book Group Press, July 2016] , the authors propose a simple formula, common principles, and set of tools for individuals and organizations facing disruptive and radical change. It’s no longer enough to change when you have to.

Disruption 40

Disruption Technical Review Software Review Agile 40

ITONICS

MAY 14, 2018

Large corporations have taken steps towards being more agile and adapting to the rapid pace of digitization by improving their oftentimes long innovation processes and giving more autonomy to employees. Often, it’s due to the speed at which they can innovate and this has a lot to do with their size. Adapt or die. Listen and say yes!

Company 57

Company Technical Review Software Review Innovation 57

The Inovo Group

APRIL 17, 2017

There is an apparent split between companies that find it easy to build a collaborative, customer-centric culture (smaller, more agile startup-type companies) and those that don’t (i.e., P&G), software (e.g., Wall Street will force this change because the companies that become digital will vastly outperform those that do not.

Disruption 40

Disruption Artificial Inteligence Technical Review Tips 40

Boxes and Arrows

DECEMBER 23, 2014

In a flash of insight, he realized that software could replace pencil-and-paper accounting for everyone. They had users try their new software, Quicken, while they ran a stopwatch. Then they’d tweak the software and retest until processes that took an hour were reduced to a quarter of that.

Design 104

Design Software Review Underperforming Technical Team Software 104