[Tool Review] — Pie — Work chat that’s all signal, no noise


If you’re running Agile in your team, you’re likely logged in to several group chat rooms right now. At the very least, you’re plugged into rooms for engineering and product discussions. There’s also rooms for design and marketing that you pop into every now and then. And you’re definitely in some kind of ‘random’ chatroom for watercooler stuff.

With so many chat rooms, and so many discussions, it can sometimes be hard to keep up. There are times where you load your chat app and find something like 500 unread items. If you work in a distributed team, or even if you’ve just stepped away for a few hours, you’ve definitely seen this before. How can you separate the important discussions from the off-topic fluff?

[Enter]: Piework chat that’s all signal, no noise.

Pie lets you quickly create a new chat room for everything you want to share, so discussions stay focused and on-topic.

Let’s have a look:


A chatroom for every topic. This is the first thing you’ll notice when you first use Pie. Instead of the traditional group chatroom model, Pie is more like a hybrid between message boards and chat.

You can quickly know what your team is talking about, and you can drop in and comment only on the topics you find interesting:


You can post notes, upload files and share links to Pie, so you can start a conversation about anything you want.

Frictionless sharing. With so many articles and resources on Agile coming out all the time, one of the most common things we do in group chat rooms is to drop in, paste a link, and nudge everyone to read.

We do this several times a day, so that minute or two that you’re knocked out of your workflow to share something adds up.

Pie makes this a lot easier with their Chrome extension — it’s the only chat app out there that lets you share something without leaving the webpage you’re reading.


And with the way Pie is set up, your link shows up as a new topic, so you won’t interrupt any ongoing conversations when sharing something new.

Tagged chat topics. You can use hashtags on Pie to create collections of chatrooms, or to help you find old conversations:



Pie gives you a central place to have all your team’s conversations, instead of having to pay attention to email threads, comments in Google docs and all the group chats you have going on.

It’s free for companies of all sizes. Try it out with your team: http://piethis.com

To be or not to be – Agile Architecture

This is an attempt to highlight how the practice of architecture is misunderstood in most of the Agile projects & the root cause behind them – so that you may avoid them at your organization/project.

Agile has always challenged people with the age old question – how much to design upfront? But is the confusion just there? Frankly, it doesn’t even start there! Anyone understands the need of an architect, but how do we position an Architect within an Agile environment? How does Enterprise Architects work in sync with a Solution Architect? How should business leverage the niche skills of an architect to ensure the scalability of the application? And how are the architects coping with the changing dynamics of development methodology? How does this practice work in an onshore-offshore environment?

We take a look in to the current challenges & answer to all the above questions. We try to ensure that Agile delivery makes the best use of architects and architects don’t shy away from Agile world.

Flaw at Onset

architecture-agile-epicsIf we look from the very inception of a project i.e. the phase where we visualize requirements & float the RFP, we always acknowledge that the backbone of development will always be its architecture. Now, let’s step back & try to visualize how we place our requirement to the market & how they get interpreted.

While floating an RFP – just like any project, we strive to get the final figures from the vendor. In general, any response from a reputed vendor is acceptable, but the lower figures will excite us more. True! Situations tend to get more complex – if it’s an Agile project (well, we all wish to be Agile, isn’t it) – we tend to add some bells & whistles by adding the sizing constraint as well. How? Well, we often put a request of providing dollar value to Story Points. How does that help? Ideally – it doesn’t help us anyways apart from giving us a very high level understanding on how each module may impact us from investment perspective. Continue reading “To be or not to be – Agile Architecture”