Noteplan 2.0 update#
Noteplan 2.0 manual#
Noteplan 2.0 full#

Furthermore, I sometimes actively email the users to have a look at the newest increment. This works best if you have a beta program.

Noteplan 2.0 update#

This deviates from the vanilla Scrum, because the review should be a single event at the end of the sprint.Īfter releasing an update I often get emails with feedback right away, because I encourage users to write back in the change-log and in general. to validate that you are on the right track. Instead of inviting them to a meeting (which becomes quite difficult if it’s “just” a small app) you can talk with your users via email, Twitter, Reddit, etc. Sprint ReviewĪt the end of a sprint, in the Sprint Review, you can inspect the product yourself, but it’s way better if you can get feedback from your users.

Noteplan 2.0 manual#

The amount of points you are getting done (and this means “done-done”, including unit tests and manual testing, etc.) in a sprint is your velocity. Why story points? You can calculate your average velocity, measure your productivity and make planning more predictable. This is quite straightforward and Jira supports creating a product backlog, sprint backlog and sprint goal including a start and end time.Īll the user stories (not bugs) you select for the sprint backlog should be also estimated using story points (this number represents the relative size between user stories, usually from 1–13 and picked from the Fibonacci sequence: 1, 2, 3, 5, 8 or 13). This can take just a few minutes if you kept the backlog clean and up to date. Here you set yourself a goal (good habit!) and pick all the user stories from the prioritized product backlog in Jira you think you can accomplish in the next 2 weeks (assuming your sprint is 2 weeks). Here is how you can do “Solo Scrum” as indie developer. You still can and should hold the Scrum events.

It doesn’t actually matter if you are solo or in a team. And finally, there is the Daily Scrum meeting or “standup” to synchronize activities and create a plan for the current day.This makes the sprint planning way faster and easier. In between, you meet up for Backlog Refinement to keep the backlog clean and updated.and the Sprint Retrospective (after the review) to reflect on how you were doing and to find ways to improve yourself.the Sprint Review at the end of a sprint to gather feedback about the product increment you just have finished, ideally from real customers.the Sprint Planning at the beginning of a sprint to decide the goal of the sprint and pick the maximum of user stories you can handle to fulfill the goal in this sprint,.Scrum Events for Oneįirst, a quick summary of the events. You need something digital for simple copy-paste and search functionality. I have also tried the physical approach using whiteboards, index cards, post-its, etc. The other 2% of my time I spent in the reports at the end of the sprint. 98% of the time I use the product and sprint backlog inside Jira and add or refine the user stories. No matter how I did it, I quickly lost the overview. I have tried to accomplish this inside Trello earlier, but it was too messy. The UX is not always intuitive, but it gives you what you need (and way more) to implement Scrum for a low price. I learned Scrum by introducing it into the company I worked before and got the PSM 1 certificate. I have used the Scrum framework to build version 2.0 of my app, “ NotePlan ”, from scratch (a complete re-write) in swift, which I had to learn in the process. I’m also filling the framework here with practices I found work great for me. This is not quite “Scrum by the book”, however, Scrum encapsulates very useful habits which make us humans happier and more productive even outside the work environment as personal Scrum. In the following paragraphs I will describe how I use the Scrum framework by first going through the Scrum events, how I apply them for the development of my app and then how I manage the backlog.

Noteplan 2.0 full#

However, the agile framework is full of gems even for one-man operations and indie developers. And there is a Scrum master and product owner around. Scrum is normally for teams with at least 3 developers.