Hi everyone, David from TeamUp Labs here to give you an update on the new features our developers have been busy with over the last few months.
Hi again! It’s been a little while since we last updated this blog. We’ve been hard at work in the background and I have the pleasure to share two major TeamUp Labs! announcements with you today.
We’ve incorporated! We’re a real company registered with Companies House. We have a bank account and shares and even a company stamp. It’s been challenging to get to this stage. We’ve had to learn about the responsibilities of company Directorship and accounting. But it’s great that it’s happened. Incorporating also shows that our commitment to TeamUp Labs is genuine. Our desire to build tools that help teams deliver great products remains unwavering,
More excitingly, I’m thrilled to announce that we have released our first Jira application. Example Mapping for Jira is now available on the Atlassian Marketplace for Jira Cloud users.
I’m delighted about this. I value the Example Mapping tool available at http://www.teamuplabs.com, but I recognise there are drawbacks. For example, the Example Map belongs under a single user’s account. That user had to log in to access it if the team wanted to review it or change it. Also, having to go to a different website, log in, create the example map and then copy the output, is not the ideal UX.
By creating Example Mapping for Jira we’ve addressed these problems. With the application installed you can create, edit and view an Example map from any Issue. You will no longer need to leave your story workflow to get all the benefits of Example mapping, it’s right there inside Jira.
The Example map anchors to the Jira issue, instead of a user’s dashboard. This means anyone who can access the issue can view and edit the Example map. This makes it much easier for the whole team to contribute in real time. Data is now stored in Jira and you no longer need a separate TeamUp Labs user to be able to use Example mapping.
We’ve also included a host of other improvements in this release. Drag and drop of rules and examples works better than ever. The summary view in the Jira issue is cleaner and easier to read than it was before, and requires no export. We’ve also squashed a few bugs.
Example Mapping for Jira is the best version of our Example Mapping solution, and we’d be delighted if you tried it. Our intention is to evolve the application further over the next few months. Your feedback would be invaluable to help us make it as useful as it can be.
Thanks for reading. As always, you can get in touch with us @TeamUpLabs. Looking forward to hearing from you.
It has been a long time coming, but the first phase of Drag and Drop is now live and ready to use. It took a long time because we had a set of quite particular requirements, so it was hard to find a flexible enough library and then make it work the way we wanted.
Some of our requirements were:
- Ability to drag rules
- Ability to reorder examples within a rule
- Ability to move examples between rules
- Rules can extend beyond the confines of the screen in both directions (e.g. you may want 20 columns x 4 rows)
- Rules have a definitive order, so that when they are exported as text, your carefully constructed Example Map is not in a surprising order
- Rules can easily extend vertically to accomodate Rule text and Examples
To get the definitive order we went back to first principles of Post-it notes on a table. You wouldn’t lay the notes out like HTML lays out elements, and you wouldn’t use vertical compacting. Instead you would most likely have multiple rows, which is what we have opted for. You can either fill up the top row and then start adding to the next row, or keep going horizontally and scroll the page, or whatever you like. Rules can be dragged between the rows. When the Example Map is exported the order is from left to right of the first row, then the next row, and so on.
Here is an example Example Map showing two rows:
We also took the opportunity to fix Jira exporting, so now if you use JSON in your Example Map, it will appear properly in Jira.
As mentioned this is phase one. We have not yet implemented the ability to drag Examples, or Questions, although we have spiked these and no they are possible! Please try out drag and drop Example Maps and let us know what you think on Twitter @TeamUpLabs.
On Tuesday 8th January TeamUp Labs! (Brigitte Maenhout, Tom Fairweather and David Hackman) presented our first ever talk to an audience of eager Agile enthusiasts. We were lucky enough to be invited to the excellent Agile South Coast – Southampton Chapter where we gave a presentation and workshop on Example Mapping. Here is how our presenters felt it went.
How did you think it went?
Tom: I was really pleased with how it went. This was our first public talk, so we had a modest goal of not looking stupid. We were a little nervous beforehand but increased in confidence throughout the talk. The Agile South Coast audience were receptive, engaged and full of questions. Some of them were chomping at the bit to get their hands on our Example Mapping tool.
Brigitte: Well, one thing is for sure, I left the room with a BIG smile on my face and I felt exhausted, but at the same time super energised! The people at @AgileSouthCoast were such an enthusiastic and energetic audience, lots of participation and insightful questions! It was just amazing to see and experience. I truly hope they were able to see how passionate we are about what we can achieve with TeamUp Labs and that they enjoy using our tools.
I would love to go back there and hear the feedback of people who used our tool so we can improve it even more. In fact, thanks to Steven from @AgileSouthCoast it looks like we will to do a user forum session on our example mapping tool.
What did you get out of it?
Brigitte: Energy! Lots of it 🙂 to get such a positive and welcoming reaction from people who are genuinely interested in exploring agile tools and mindset to improve their lives and the lives of the teams they are in, is a real motivating experience. It added to our momentum as a team.
David: I think we got some amazing feedback, not just on the tool or the technique but also on us as a team and how we presented. I also felt like the meet up validated that there is a need for tools that do we really help teams work together effectively and build the right thing.
Were you nervous beforehand and how did you cope with that?
David: A little. This was our first time talking about TeamUp Labs and I really wanted to make sure we did a good job of explaining our tool and the technique so that the attendees found it valuable (which I think they did!). Before we started the talk I spoke to a few of the people who attend the ASC meetup regularly – they were really nice and welcoming, which helped a lot to settle my nerves.
Tom: Yes, we were a little nervous. We played pool and chatted with the ASC members to relax before it started, but to be honest this didn’t work that well for me. My nerves dissipated throughout the talk.
What was your most memorable moment?
Tom: I would have to say dropping three globs of pizza sauce down my shirt minutes before it was due to start. Luckily some water and lots of rubbing with paper towels made it not noticeable. Other than that, the interactive session was memorable for being chaotic with a very engaged audience.
Brigitte: There was this one person in the audience and he had been listening very attentively and at a certain he just said, with such enthusiasm and determination: “So, how can I had my hands on this tool?!” and that itself was so rewarding and a moment I am truly grateful for! 🙂
What were your goals, and did you meet them?
Brigitte: Feedback! In the moment and of course inspire people to take a look at our tool and give us feedback later so we can continuously improve and really build a suite of tools which will improve the way we work and what we can achieve. A conductor for true creativity and collaboration!
Did we meet them? It’s too early to tell. We met some of them, we got valuable feedback in the sessions, we saw a glimpse of the inspiration and the days after quite a few new people signed up for our tool. So, now, the real measurement of our success will be if we can get feedback after people have used the tool. So, as you can see, quite a few of our acceptance criteria have been met!
Tom: Not look stupid, get feedback from agile enthusiasts, get some new people to try TeamUp Labs’ tool. Yes, we met these goals. There were about thirty people in the crowd, and we had a small bump of eight new users the following day and no doubt some more after that.
What would you do differently next time?
Brigitte: Well, it wasn’t perfect, there might have been some things we could have focused on more; or less, but I do find that there is beauty in imperfection, it’s the source of learning and progress.
This was the very first time that we did this presentation and I got so much out of it. Even the moments of perceived chaos where we got so much audience participation that it was a bit overwhelming (in a ‘this is awesome!’ way) and I could have done perhaps a better job facilitating. I was just taken in by the moment by how much people wanted to participate, I ended up enjoying the energy and embracing the chaos. so, for next time, we’ll have to figure out a way to keep the energy but just streamline it a bit better. So, we will tweak the presentation going forward, based on the knowledge that we gained, but if I could go back in time to this presentation, I wouldn’t change a thing.
David: I think we could refine our workshop to make it easier for larger groups to participate and feel heard. I also think we will get more polished in our delivery of the talk the more we do it, so I’m looking forward to the next opportunity!
If you’d like to find out more about Example Mapping please go to our home page or read some of our blog posts. If you’re interested in finding out more about Agile South Coast they post their upcoming events here. I’m sure they’d be delighted if you went to one of their events, and I’m also positive you’d learn something useful!
As always, you can keep up to date with TeamUp Labs by following us @TeamUpLabs on twitter.
I first heard the term Exaptation at Agile Tour London 2018. It wasn’t a term I was aware of before, but it piqued my interest during Liz Keogh’s opening talk. In simple terms Exaptation is making use of something in a way other than the initial intention or design for use. I’d like to talk about a few good examples of Exaptation in this post.
One of the most powerful natural examples of Exaptation is bird flight. Feathers were not originally intended for flight, instead their purpose was heat regulation and attraction of the opposite sex for reproductive purposes. Flight was a by-product of the fact that they had wings, but it is (in most cases, barring Ostriches etc.) now the characteristic that is quintessential to the concept of a bird.
Technology, too, has seen significant examples of Exaptation throughout the years. The rockets used by NASA (Werner Von Braun’s V2 rocket) to allow humankind to breach the barrier of making orbit was due to the exaptation of the technology of the rocket. The explosive power of the first ICBM was transformed to enable Space flight instead of enhancing a nation’s firepower. A weapon of war’s purpose was completely altered to allow the Global civilization to a take step forward and look up to the stars, instead of each other’s borders. On a slightly lighter note, LSD was never intended to be a recreation drug and its psychotropic properties were only found 5 years after it’s initial synthesize.
In Software as well, there are strong examples of companies pivoting because they create something that becomes so essential, it must become the entire focus of their operations. A fantastic example is the all reaching Social Media platform Twitter. Twitter was formed out of a podcast Publishing house called Odeo, and the tool itself was more about internal messaging. When the team realised the power of their code, they pivoted away from the crowded Podcast industry and are now a household name.
Slack also came from a company focussed on a completely distinct vertical. At the time the company behind Slack were working on a browser based MMO. They built a set of tools around this MMO to help their admins and their community managers work with their users. This tool became SLACK (Searchable Log of All Knowledge and Conversation). The MMO that Tiny Speck were working on was called Glitch. How many people know about that game compared to the success that Slack has enjoyed since?
Exaptation doesn’t just come from a failing company though, it can also occur in extremely successful ones. In gaming, Valve pivoted from making games to selling them through Steam. This developer was one of the highest regarded in the industry and had just released the critically acclaimed Half Life 2. Rather than continue to make this series, Valve pivoted and decided they could be more successful selling games and owning the PC ecommerce space. They do still of course make games, but it would be hard to argue that this is their purpose anymore.
Here, at TeamUp Labs, our goal is to make tools that improve your ability to build valuable software as a team. Our first tool, the Example Mapping tool, has been well received and we have received a lot of feedback. We’re continuing to enhance the functionality with focus on splitting and drag and drop in the UI, but we’d love to hear what you need to make it as helpful as possible in the use cases you have. I’ve personally used it for Feature Kick Offs, and other members of the team have used it for SWOT analysis amongst other things, but we recognise the tool will be used in ways beyond our original intentions, and we’d love to hear more about how you, our users, have exapted it!
Thanks for reading. As always, you can get in touch with us directly @TeamUpLabs. Looking forward to hearing from you.
Photo by Pixabay on Pexels.com
For many years I’ve felt strongly that choosing to rewrite a piece of software is something you have to think really hard about. You have to have good reasons to do it, and it’s often the wrong choice. It’s a classic issue in software engineering where you think it won’t take long, and that you’ll quickly be back to productivity.
Experienced teams know the trap of assumptions. Every one assumes you are on the same page and is eager to jump into development, get it done, quick, quick, quick… and then nagging doubt sets in…
“Ah, that’s not how I imaged it”,”Ow, I think I might have misunderstood this”, “Well that’s not what I was thinking!”