#NIMBLE SOFTWARE SOFTWARE#

Later, when you need a UI, you switch to Python or Spring Boot. When you have the database, you use psql or pgadmin to enter simple data. When the data gets more complex later, you can decide on a database. If you need a table, use a text file or a spreadsheet.

What you really want to do is to postpone all choices that may limit you in what you do. These decisions then limit choices you make further down the road. Traditionally, you decide on architectural issues and tooling at the start of a project. They are simultaneous: while working on something you realize you need something additional or you need to change things. Working and reflection are not alternating processes. start working (“build API in Spring Boot”).start working (“add notes, transcribe letters”).reflect (“I need a table, letters are hard to read so I need to transcribe them”).start working (“start scanning the letters”).set short term goal (“create inventory of letters”).set long term goal without being too specific (“write book”).If I would create a development method from this project, it would go something like this:

The web site is work in progress, and it will be so for many years to come. Then I thought a web site would be more useful than a book, so I dropped the book and added more functions to the web site. Then I realized that now I had everything in a database, I could make it available via a web site. To access the database I wrote an API in Spring Boot. When making notes for the book, I converted the single table into a structured database so I could store the notes. I added data to the table, which I had created in postgres. After I scanned the letters, I decided to transcribe them into ascii. When scanning the letters, I realized I needed a list or table to keep track of them. I had no plan when I started to scan the letters. One of my projects is It started with me getting two boxes of historical letters. The smallest projects I know are one person projects where you are the owner, the developer, the user and everything.

I like to work in large projects in the same way I work in small projects. Fortunately, product owners stop stakeholders from changing their mind, they make sure that requirements remain focused towards the original goal. Stakeholders (users and customers, represented by product managers and product owners) may change their focus and require features and functions that are not in line with what you have been working on so far. Requirements in consecutive iterations are not necessarily on a smooth path towards a goal. Because you don’t want to specify in too much detail at the start of the project, you divide your project in smalls steps (sprints) and you specify and verify every two weeks. You want to specify all kinds of things in advance so you can monitor progress and verify that you received what you ordered. the product has no bugs or flaws - this includes security issues, performance issues, errors, crashes, etc.

the product is good, in the sense that the user likes it and likes to work with it, or at least accepts it.

product implements all required features in the way they were specified.

#NIMBLE SOFTWARE SOFTWARE#

The goal of a software development project is to deliver software with the following features:Ĭost and time are obvious, quality needs more specification. But does it work? Does it help you toachieve the goals you set? What goals did you set when you deciced to use Scrum and be agile? What is the purpose of Scrum and Agile anyway? What is the purpose of any method for software development? Goal Today, if you work in software development, you use Scrum.

Nimble software