Contact Us
Magenic
  • What We Do
  • How We Do It
  • Our Thinking
  • Join Us
  • Our Work
  • Industries
  • Cloud
  • Software Development
  • Quality Engineering
  • DevOps
  • Strategy
  • Experience Design
  • Data & Integration
  • Advisory Services
  • Careers
  • Culture
  • Events
  • Success Stories
  • Partnerships
  • Technologies
  • Professional Services
  • Financial Services
  • Retail
  • Health Care

Product versus project approach? No contest when creating software

April 23, 2018 // By John Doucette

As your business and IT departments come together to collaborate on new software innovations, it’s critical everyone is on board with a product-based — not a project-based — approach.

“Bring the work to the teams” is the focus of product driven software development. By creating fully functional teams, with all the roles such as a product owner, scrum master, development lead, developer, test engineer, designer, data scientist and even an architect – you get consistency and velocity. The team(s) work together, usually in business domains such as inventory, purchasing, merchandising, or marketing.

“Bring the people to the work” is a hallmark of project-based organizations, building annual budgets and prioritizing those projects in the queue which need to be delivered. There are domain teams, but much of the shared resources such as business analysts (aka product owners), test engineers, and project managers, come from other parts of the organization to work on the project. Velocity takes a while to find, and most projects have a time sink in the repeating patterns of FSNP, or Forming, Storming, Norming and Performing.

From my years of experience with both approaches, I recommend the product-based strategy because of the profound effect it can have on the overall velocity to meet market demands faster. Its structure allows entire teams to keep their eyes on the prize: the fast and efficient development of money-making vehicles that will solve clients' problems, using the latest technologies available. Here are a few tips for optimizing product-based strategies:

  • Assign a skilled product owner to oversee the process and keep your team focused.
  • Build a backlog and encourage team participation in scrums, grooming sessions, demos and retrospectives that help maintain your planned scope and timeline.
  • Throughout the process, continue to seek real-world feedback from users and review it with the team, allowing it to take ownership and make changes accordingly.

While both product- and project-based methodologies offer value, I believe product perspectives are more effective and efficient when it comes to collaborating on marketable software products.

You can learn more about how shifting from a project to product mindset can get you to market faster in our latest editorial.

Categories // Technology
Tags Product Management, Product Delivery, Project Management
SHARE:
THE LATEST:
  • FEBRUARY 23, 2021 // blog
    Stronger Product Owner = Better Software, Faster
  • FEBRUARY 19, 2021 // blog
    Security In Five Bi-Weekly Roundup – 2/19/21
  • FEBRUARY 18, 2021 // blog
    Doesn’t Everybody Know This?
Featured Content:
  • JANUARY 25, 2021 // White Paper
    The Top 7 Technology Trends of 2021

Related Posts

Podcast
Tech Consulting Fastcast 13: Top Technology Trends 2021
Learn More
Blog
The Value of Code Reviews
Learn More
Podcast
Security In Five Bi-Weekly Roundup – 11/27/20
Learn More
Podcast
Tech Consulting Fastcast 12: Security
Learn More

Ready to speak with our experts?

Have a question?

This field is required
This field is required
This field is required
This field is required

Thanks for Contacting Magenic

One of our experts will be contacting you directly within the next business day.

Return To Home
Magenic

info@magenic.com+1.877.277.1044

  • Facebook
  • Twitter
  • LinkedIn
  • YouTube
  • RSS Feed

© Magenic Inc.Privacy NoticeTerms & ConditionsSitemap