We have been using JIRA On-Demand or JIRA Cloud for a few years now. It was an easy SaaS decision and helped us get started very quickly. After a while, we realized that most of the cool add-ons for JIRA are only available to the JIRA Server instance. Our web applications have an Issue-Track (Critical-Response) form that users fill out to report a problem or ask for an enhancement. Currently we take these forms and manually transfer them into JIRA. The JIRA licenses are too expensive to give all our customers a JIRA user ID’s. So we designed an integrated JIRA interface into our Issue Track page that talks direct to our JIRA-Cloud Instance. No more copy-paste. One of our government customers has a security rule that only allows API usage to servers with a single IP address. Well, JIRA Cloud instances from Atlassian are actually hosted on Amazon Web Services which uses a pool of IP addresses for better performance which makes sense. For us to get a single IP we will need to migrate our JIRA Cloud instance to a JIRA server instance. We have decided to stay as close to the way Atlassian manages their cloud instances so we will be using AWS as well but, with a single IP address. I will document this journey over time in this Blog, one for some reference documentation and two because I like to share.
Two of my favorite tools which I use on a daily basis. Now they can talk to each other without having to jump through a bunch of hoops. It appears to be limited to Justinmind Enterprise edition.
I have been doing rapid prototyping for web and mobile applications for a few years now. The answer to the question above is a definite YES! If the user can “play” the prototype on the device it will be used on; they will be more likely to see things that need to adjusted. “Play” includes viewing pages, entering data into forms, interacting and navigation. This article from Justinmind’s Emily Grace Adiseshiah explains better than I can, more of the justification for real Rapid Prototyping web and mobile applications. As a designer, I’m a big fan of Justinmind and use it every day. As a developer, I could write prototype scaffolding that could become the framework for the actual application. While this may save a little time; Justinmind adds a collaboration layer that makes interaction with the user simple. Recently Justinmind and Atlassian’s JIRA announced requirements integration which allows the prototype to feed the requirements to the developers via of JIRA’s. If you’re going to be agile then you have to seriously consider rapid prototyping.
Git is the de facto standard for agile software development when it comes to version control systems. This well-supported open source project is flexible enough to support a range of workflows that suit the needs of any given software team. This Atlassian article is a great overview on how to handle the branches in a typical development project that has small and big changes as well as things breaking.
No truer word are spoken than these, “The Agile Manifesto is simple, clean and doesn’t enforce any methods.” This opinion piece by Yusuf Autas is right on the money. Less is more, less meeting, less new roles, less new terminology. Focus on building something quickly, refine it until the customer says “Wow”! Some of the Scrum disciplines are just in place so management can see a process they might be able to interject new goals and visions. I like to use Kanban Tool to organize my projects. This is simple and to the point task management system.
Larger projects may require some better tasks tracking in which case I would use Atlassian’s JIRA and its boards. It is possible to connect these two tools together to take advantage of the best features of each of them.
I am currently working on some presentation and course material on putting the Agile train back on track after the Scrumnado wrecks I have witnessed. I will post them here at GeekMustHave.