When you archive a project, it’s possible that some cards still had Due Dates set on them: these dates are preserved along with all the other project data at the time you do the archiving.
But, these dates, which will inevitably become overdue dates over time, are not included in your 6AM task summary email, because there’s nothing you can do about them while the project remains in the Archive.
If you work for a government agency in the United States – at the Federal, State, or Local level – you are subject to various public disclosure requirements, thanks to the Freedom of Information Act and various other federal and state “Sunshine” laws.
(And, if you work for a governmental organization anywhere in the European Union, that’s going to be true for you as well.)
Kerika makes it one-click easy for you to meet you disclosure requirements, thanks to the Archive and Export feature:
Archiving freezes a project, presumably in it’s “done” state: everyone who used to have access to the project still does, but all cards, canvases and documents associated with that project are made read-only.
This means that you now have a pretty good record for what a project looked like when it was completed: what work was done, by whom, and which documents were used and what conversations took place.
And the kind of integrated, comprehensive view of a done project is something that you can get only from Kerika: the old mix of SharePoint and Project and regular email just doesn’t work!
Exporting is the other piece of the disclosure puzzle: with just one mouse click, you can export all (or some) of the cards in a board, in CSV or HTML format.
Exporting in HTML is particularly helpful when meeting disclosure requests because the HTML output can be easily edited, using Microsoft Word for example, to take out items that need to be redacted for security or privacy reasons.
That’s the difference with a modern project management and team collaboration software like Kerika: the worst part of your government job just became one-click easy.
We have upgraded the SSL certificate, used to secure your browser’s connection to kerika.com, from SHA-1 to SHA-2.
(SHA-2 is a cryptographic hashing algorithm developed by the National Institute of Standards and Technology (NIST) to replace SHA-1.)
This puts Kerika ahead of moves that Google and Microsoft will soon take, for the Chrome and Internet Explorer browsers, respectively, that will start showing warning signs when you visit a website that uses the older SHA-1 certificates.
If you are not sure whether your favorite secure site has upgraded to SHA-2, Symantec has a helpful tool you can use:
If you are working off a long Backlog (like we do at Kerika!), then you will have many Scrum Boards that pull items off this shared Backlog over time, and with our new Archive feature you will want to freeze old Scrum Boards as you get done with Sprints.
(Each Sprint should be done as a separate Scrum Board, that connects to the same Backlog.)
When you archive one particular Scrum Board, you only freeze that board: the Backlog remains available for use — and modification — by other Scrum Boards, now and in the future.
Which means that when you open an Archived Scrum Board, the view you will get of the Backlog will show the Backlog as it exists today, not as it existed when you archived the Scrum Board.