All posts in Software Development


Ditch Scrum! 3 Shape Up Processes & Checklists to 5x Your Dev Cycle

Shape-Up-processes
We’ve cut our development cycle by 70% since making the move to Shape Up.

This alternative development method is a breath of fresh air from all things Scrum, Agile, Kanban, Scrumban, Fake Agile, Bad Agile… you get my drift.

What started off as Basecamp‘s internal approach to developing and shipping software at lightning speed, has become a clearly written (and illustrated), freely contributed, and easily accessible e-book: Shape Up: Stop Running in Circles and Ship Work that Matters.

Although I sincerely recommend you read the book, this post is here to save you from studying the 143 pages of text by providing you with three nifty checklist templates. The checklists take you through the Shape Up process and its 3 key phases: Shaping, betting, and building.

In this post, I’ll briefly touch on the fundamental concepts of Shape Up’s approach. I’ll also introduce each of the phases and their corresponding checklist.

Let’s get shaping!
Continue Reading

An Interview with Ivy: Shape Up From a Product Designer’s Perspective

shape ups design processI wrote a post about Shape Up, a development methodology, and you the reader wanted me to dive deeper. So, I did just that and interviewed Process Street’s Product Designer, Ivy.

Ivy answers common questions concerning how Shape Up works in practice, and although I briefly touch on the core phases of Shape Up’s approach, this post should be seen as a follow up to my original post which provides a full low-down of what Shape Up is and how it differs from alternative development methods like Scrum and Kanban.

So, make sure to read my last post on Shape Up so you have all the context you need for this post.

In this post, we’ll be covering:

Let’s kick things off with a brief re-cap of Shape Up’s key phases 🚀.
Continue Reading

The Inside Secrets of a Process Street Full Stack Engineer

The Inside Secrets of a Process Street Full Stack Engineer

Until a few weeks ago, I had no idea what exactly a full-stack engineer was, let alone what the role entailed. I know, I know – I work for a tech startup, I should know these things.

You’re right; I should.

So, to educate myself, I sat down with one of Process Street’s engineers, Herbie Porter, to discuss what he does, his first year at Process Street, and the art of making pandemic cocktails:

It is my privilege to introduce you to…
Continue Reading

A Basic Introduction to Creating a Software Requirements Specification

A Basic Introduction to Creating a Software Requirements Specification

Kamelia Stone is Content Manager at Marketbusinessnews. She likes to travel, meditate, and draw inspiration from different sources, primarily from books.

Software Requirements Specifications (SRSs) document describes the various software features, capabilities, coding tests, and functions that are to be implemented in the product.

These parameters also include characteristics, design details, and implementation obstacles for the development team. The structure of SRS can be modified, depending on the project, and various features/functions can be added during the process.

SRS lies in the initial, bottom stage of the entire development process. The next stages include user requirements, which detail the needs of end-users, and describing beyond the goal of the final product (business requirements).

No matter how the SRS structure is shifted during the development process, functional (if/then, data handling, etc.) and non-functional (usability, scalability, etc.) requirements always take place.

This post for Process Street will discuss:

Now let’s get straight to business.
Continue Reading

Quicken Your Software Deployment & Generate More Value with CI/CD

This is a guest post by Gabe Nelson. Gabe is a content specialist with over 7 years of experience, currently working with Semaphoreci.com. He has a passion for programming and has written hundreds of content pieces in numerous niches. Currently, he lives in Missouri with his wife and kids.

Let’s face it: the longer your software takes to get from ideation to iteration, the more irrelevant it becomes.

With the innovation of new paradigms and working methods to meet the right here/right now demands of consumers in a hyper-connected world, your developers need workflows that will deliver your software into production environments the second they’re able to.

The millisecond micro nanosecond, even.

Managing your software deployment processes and procedures to not just keep up with, but stay ahead of, the competition can seem like a Sisyphean task, but it doesn’t have to be.

Continuous integration (CI) and continuous delivery (CD) together constitute the light at the end of a software developer’s tunnel. No doubt that’s why implementation is commonly described in terms of “pipelines” – CI/CD takes you straight through the problems.

More specifically, CI/CD pipelines make it easy for developers to deploy working code into functional and error-free production environments. That’s because these workflows do a great job of automating entire pipelines of your team’s code releases and updates. This frees up developers to create new features and processes instead of spending hours debugging faulty code.

In this Process Street guest post, I’ll do a quick walkthrough of the basics of CI/CD, then dive into how CI/CD can generate more value for and quicken your software deployment.

Read on…
Continue Reading

Get a free Process Street account
and take control of your workflows today.

No Credit Card Required