we write about the things we build and the things we consume post-agile: an update on our development process, talking to each other More often than not, when asked about our development process, we wish there was a one word way to put it. But then we wouldn't be able to convey the essence of how we get things done: by talking to each other . Over a year ago, Chris described the initial form of this process , and time has come to share with you how it got shaped meanwhile by a larger team and feeding back our experience. in short We're not using Agile anymore, we're not doing Kanban , we don't make it the company's business to comment on individual preferences like, say, Pomodoro (as long as they don't inconvenience anyone), and we don't expect to find all the answers in the next development process fad, though we keep up to date. We're very keen that the tools we use don't define our work, we tweak little things daily and weekly, as they come up, and we take on major iterative work every month or quarter -- as often as required. The bet is that maintaining a healthy dialogue at all levels and at all times, we'll all be more successful. appy hour We get together every single day at noon sharp. Those working remotely call in. We take up to ten minutes to look at what everyone has done, is doing, and needs help with,