Edit: the R6#12 version is replaced by R6#12.1. If you installed R6#12, we strongly recommend that you update in order to benefit from the following bug fix:
- ICESCRUM-882 – Insufficient drop-down width makes hard to see and chopse estimates, ranks etc. (table & post-it view)
Here comes a new version of iceScrum and iceScrum Pro!
This version is mainly a maintenance update with several bug fixes before biggest changes to come in the next version: R7#1.
We wish you an happy new year! All the best for your Scrum projects!R6 – Sprint 12 (17/12/2013 – 31/12/2013) Bug fixes
- ICESCRUM-835 – Sometimes, return to sandbox isn’t applied immediately (refresh needed)
- ICESCRUM-837 – Return to sandbox prepend the story instead of inserting it in the right place (a refresh fix that)
- ICESCRUM-840 – It is possible to enter the task board in table view but it doesn’t work properly
- ICESCRUM-839 – Scrollbar hides numbers in table view
- ICESCRUM-844 – Add PO on task board view
- ICESCRUM-838 – Commit message with a 0 remaining time on a Todo story doesn’t finish the story
- ICESCRUM-836 – Opening a dropdown at the bottom of table view leads to a blank page
- ICESCRUM-593 – Server config via JNDI
We’ve been getting pretty particular about our stub/mock expectations at work. A few months ago I would been perfectly happy with:1
I didn’t worry about specifying that I didn’t pass any arguments to the constructor. After it was pointed out that the stub didn’t really fully specify its’ expectations I changed to this style:1
Then a colleague pointed out a nice bit of syntactic sugar. You can simply specify a no_args matcher if no arguments are passed in:1
A more complete stub with better readability. Reminds me of how I fell in love with RSpec the first time I saw it back in 2006.
Now that the team is armed with new weapons, it is time to help the Scrum Master to fight back. If you didn’t read my first post on this topic have a look at the 10 things a Scrum Master can do to drive the team crazy blog post I wrote two years ago. Here we go:
- Get you own office, if possible in a different city or even country. Working at the same location as your team could be harmful.
- Count the number of finished tasks per team member and confront those lazy buggers with the obvious low performance.
- Try to restrict the communication with the team to Email only. You don’t want to hear their whiny voices.
- Don’t tell the team what you are working on. Transparency only applies to the rest of the team.
- Always cite the Scrum guide if members don’t stand to the Scrum rules. Continuous repetition will help raising the team’s understanding for this process.
- If a team member has a question, point them to Google. Google has all the answers, right?
- Ignore the Product Owner. It is his responsibility to create and maintain the backlog, not yours.
- Don’t attend the Sprint Review. It is a meeting exclusively between the PO and the team.
- Nurture your lack of interest about the product the team is building. This is something the PO has to take care of.
- Bring drums to the team’s office and play them like on a slave ship. Every good team needs a beat.
I’m looking forward to your additions in the comments
It’s been a long time since I wrote “10 things to drive your Scrum Master crazy” and it’s about time to give you some new weapons. So, here they are:
- Hide the SM’s beloved moderation markers.
- Play on your smartphone during the (planning) meetings, as long as they are not talking about YOUR tasks.
- Always lament about the same things but don’t change anything.
- Keep blaming and finger pointing everyone else except yourself for all the problems, you are only a victim.
- Ignore all agile values as they don’t apply to you.
- Simply ignore your Scrum Master, especially when he tries to coach you. Coaching is evil!
- Ignore the findings from your latest retrospective because you have more important stuff to do.
- Write as many things as possible on ONE post-it. Clustering is much more fun this way.
- Don’t put your tasks on the sprint backlog. Your Scrum Master is an evil micro manager. I swear. Transparency sucks.
- Ask your boss to put the Scrum values into the performance goals of every employee.
Here comes a new version of iceScrum and iceScrum Pro!
This version should improve your experience thanks to several bug fixes and UI/UX improvements.R6#11 – R6 – Sprint 11 (25/10/2013 – 06/12/2013) New features and improvements
- ICESCRUM-505 – Choose the default project visibility
According to the transparency agile principle, iceScrum projects are public by default. However, your projects often carry sensible data so you may want to make new projects private by default. This is now possible thanks to a new configuration entry (available both in config.groovy and iceScrum Pro Administration).
- ICESCRUM-340 – Better story template integration
New story template
Story template integration was not consistent. In order to improve that, we looked at how this feature was used and we noticed that story templates were mostly a replacement for the description when users wanted more structuring. To prevent redundancy and make story structuring easier, we now bring the template structure directly into the description (in plain text).
When creating a story, the description field is now pre-filled with the story template (« As a… I want to… In order to »). This feature encourages the use of the story template, that we believe helps write better stories. However, the whole template is selected on the first click so if you don’t want to use it, just start typing as usual and the template text will be replaced by what you type.
Former story template migration
Former template fields are removed from iceScrum. As a consequence, old templates from existing or imported projects will be migrated (appended) into the story description (or in the notes if they don’t fit).
If neither the description nor the notes can handle them, which is very unlikely to happen, then they will be written into the logs of your server so you don’t lose them. However, as usual, we strongly recommend that you back up all your data before upgrading.
The former « As a » template allowed linking an actor to the story. This is still possible thanks to a new autocomplete feature. When you type « a » anywhere in the story description, you can now choose an actor from the ones defined in your project.
Autocompleted actors are inserted with a dedicated markup that allows iceScrum to recognize them,
e.g. A[5-Administrator]. Only the right hand-side text is displayed in post-its and reports, while the left hand-side is the ID of the actor to link to the story. Please note that only one actor can be associated to the story so if more than one actor markup is found, only the first actor is linked to the story.
- ICESCRUM-533 – BDD template for acceptance tests
When creating an acceptance test, it is now pre-filled with the well-known « Given… When… Then » BDD template (highlighted with our markup language). This feature encourages the use of the BDD template, that we believe helps write better acceptance tests. However, the whole template is selected on the first click so if you don’t want to use it, just start typing as usual and the template text will be replaced by what you type.
- ICESCRUM-532 – Move a story from the backlog to the sandbox
Accepting a story is an important decision that must be taken conscientiously. However, even the Product Owner can make mistakes so it is now possible to move a story from the backlog back to the sandbox.
- ICESCRUM-600 – UI components upgrade for better accessibility and nicer UI (…and it’s just the beginning )
We upgraded to the latest version of the UI components we use in order to bring iceScrum closer to the standards that make the web a better place. Also, select and multi-select drop-downs are more consistent with the iceScrum UI and now offer a search field when their content exceeds five elements.
- ICESCRUM-834 – Summary of new features when iceScrum has been upgraded. Thanks to Sebastien!
- ICESCRUM-803 – Confirmation on release delete
- ICESCRUM-827 – Confirmation on feature delete
- ICESCRUM-809 – Focus on first input in login, register and retrieve forms
- ICESCRUM-828 – Task board great performance improvement (iceScrum Pro)
- ICESCRUM-633 – Some story dependencies aren’t imported
- ICESCRUM-635 – Sometimes, activities aren’t imported
- ICESCRUM-767 – Project export drops task comments
- ICESCRUM-829 – Switch user in task board doesn’t work with LDAP users (iceScrum Pro)
- ICESCRUM-800 – Bug in task board when hiding/showing done work (iceScrum Pro)
- ICESCRUM-830 – Unwanted switch back to Scrum Master in Task Board (iceScrum Pro)
- ICESCRUM-765 – Ex members don’t appear in finder creator dropdown
- ICESCRUM-831 – Quirks mode is enabled by default in modern IEs and prevents from using iceScrum
- ICESCRUM-597 – Overlapping release name prevents from using release menu in the timeline
- ICESCRUM-599 – Shift to next sprint inter-release requires at least two sprints in the next release
- ICESCRUM-812 – « Show more » isn’t displayed in the project list if the user is part of exactly 10 projects
- ICESCRUM-791 – Bugs when the admin uses project bundle (iceScrum Pro)
- ICESCRUM-775 – Impossible to delete a project that belongs to a bundle (iceScrum Pro)
- ICESCRUM-808 – Hitting enter on team form displays team leave confirmation
- ICESCRUM-818 – Project charts aren’t updated
- ICESCRUM-792 – User profiles can’t be opened from the project admin
- ICESCRUM-826 – Initial time is gone when task moved from Todo to Done directly.
- ICESCRUM-782 – Error when last task is done and AT of parent story not success
- ICESCRUM-699 – Errors when starting iceScrum with Oracle (iceScrum Pro)
- ICESCRUM-833 – Commit to a done task with 0 remaining time in the commit message moves the task to « in progress » (iceScrum Pro)
- ICESCRUM-794 – FullScreen API doesn’t work on Safari
- ICESCRUM-801 – User profile dead links for stories from other projects
- ICESCRUM-793 – Autocomplete on actors doesn’t work anymore
- ICESCRUM-795 – Notifications are mixed under the same Gmail thread
We’re very excited to announce that the new timesheet feature is now available in tinyPM 3.1. The timesheet is simple and easy to use. It allows you to log the time spent on tasks and gives you instant access to weekly reports by presenting them in a nice and clean table view. You may check out your tinyPM account right now or read on to learn more.
View and log the time spent on tasks of all of your projects with the new ‘My timesheet’ view.
Navigating your timesheet
Use the arrows to move back and forth through the weeks.
It’s easy to record how long you spent on a task. Just click the selected cell and change the value instantly. Using <TAB> key you can fill in several cells (days) quickly.
What tasks are contained in the timesheet?
tinyPM knows what tasks you’re working on and displays the appropriate ones. Additionally, the cells are marked with color on days that you’ve been working on a given task.
For an overview of your team activity, just click the ‘Team’ button. You will see a list of people you share the projects with and their summary of hours displayed weekly.
In the sidebar, there is a summary of the current and the previous month – total hours by project and options to export them.
For each project you can download a CSV file, which contains all hours entered by all users during the month. This file you may easily open in your ‘office’ application and convert into your favorite report.
You can also download a ready to print report in a PDF format.
We hope this timesheet makes time tracking easy and fast for you. We’d like to know what you think, as we plan to continue improving it, so the feedback and new ideas are highly welcome.