Software Development Best Practices

7 common project risks and how to prevent them

Read more about 7 common project risks and how to prevent them
Log in or register to post comments

Body

Analyzing risk is an important part of the project planning process. Having a clear sense of the project risks you face, can help you prevent or prepare for upcoming risks. In this article, learn about seven of the most common project risks. Then, empower your team to find solutions before these issues derail important initiatives.

What is Feature Flag-Driven Development?

Read more about What is Feature Flag-Driven Development?
Log in or register to post comments

Body

Feature flag-driven development allows you to quickly release iterations of your features to market, receive feedback, improve, and redeploy. It allows you to roll out features to small segments of your users in order to mitigate risk all while receiving valuable feedback.

What is the difference between "New feature" and "New development"?

Read more about What is the difference between "New feature" and "New development"?
Log in or register to post comments

Body

The main diference between both concepts could be: in one case your are implement a new element with new capabilities; on the other hand you are re-implementing an existing feature.

What is Software evolution?

Read more about What is Software evolution?
Log in or register to post comments

Body

Software evolution is the continual development of a piece of software after its initial release to address changing stakeholder and/or market requirements.

What is user story?

Read more about What is user story?
Log in or register to post comments

Body

A user story is a tool in Agile software development used to capture a description of a software feature from a user's perspective. The user story describes the type of user, what they want and why. A user story helps to create a simplified description of a requirement.

Metaphors in software development

Read more about Metaphors in software development
Log in or register to post comments

Body

The most primitive metaphor for software development grows out of the expression "writing code." The writing metaphor suggests that developing a program is like writing a casual letter you sit down with pen, ink, and paper and write it from start to finish. It doesn't require any formal planning, and you figure out what you want to say as you go.

WRITING A PROJECT BRIEF FOR A SOFTWARE DEVELOPMENT AGENCY: 6 THINGS TO CONSIDER

Read more about WRITING A PROJECT BRIEF FOR A SOFTWARE DEVELOPMENT AGENCY: 6 THINGS TO CONSIDER
Log in or register to post comments

Body

Whether you operate as a startup business or an international company in need of a unique software solution writing a solid project brief is essential. The reason for that is simple – IT projects are quite difficult to manage from their inception to launch without management difficulties.

What Is A Software Development Brief?

Read more about What Is A Software Development Brief?
Log in or register to post comments

Body

If you’ve got a business need for custom software and are looking for a development company to create it, your first step should be a software development brief. A well written brief not only ensures your software developer really understands your business, but it also sells them your vision and how it will work.

Removing Software Development Waste to Improve Productivity

Read more about Removing Software Development Waste to Improve Productivity
Log in or register to post comments

Body

One way to improve productivity is to reduce waste: objects, properties, conditions, activities, or processes that consume resources without benefiting stakeholders. However, reducing waste can be very challenging. People quickly acclimate to wasteful practices and waste is often hidden by bureaucracy, multitasking, poor prioritization, and invisible cognitive processes. To better understand software development waste, we conducted an in-depth study of waste at Pivotal Software, a large American software development organization, known for using and evolving Extreme Programming.

Frictionless Software Development

Read more about Frictionless Software Development
Log in or register to post comments

Body

How Friction Slows Us Down

I once joined a project where running the “unit” tests took three and a half hours.

As you may have guessed, the developers didn’t run the tests before they checked in code, resulting in a frequently red build. Running the tests just gave too much friction for the developers.

I define friction as anything that resist the developer while she is producing software.

Since then, I’ve spotted friction in numerous places while developing software.

Subscribe to Software Development Best Practices