background preloader

AgileZen

AgileZen

Viadesk SmartQ: Visual Project-Management That Conforms to You When it comes to project management, most web apps offer the same basic features: a group of to-do lists, some kind of messaging board, a few gigs of file storage, shared document-editing, a calendar of some sort, and if you’re lucky, a set of reports. But what most don’t offer is the ability to develop a project-management workflow that conforms to the way your team already works, and without this customization, you lose precious time trying to get everybody up to speed on the new way of doing things. In my experience, that ramp-up time usually results in project members abandoning the app and reverting to project management by email. Enter SmartQ. Overview SmartQ provides a visual representation of your workflow SmartQ is a project-management app based on the Kanban production system developed in the 1940s by Toyota. Getting Started with SmartQ This is where the fun comes in. What makes SmartQ different from other project-management apps is the “Workflow Designer” attached to each project.

Heroku | Cloud Application Platform Insanely simple time tracking These terms of service govern the relationship between Toggl OÜ ("Toggl") and anyone who uses or has access to, or attempts to use or gain access to, any time tracking application provided by Toggl. The terms and conditions set forth herein apply regardless of the environment in which the application is used, the geographic location of such use and the technical means employed therefore. Please consider the below text carefully for it is only if you fully agree with all terms and conditions contained herein that you may use the applications referred to. If you find anything in this document that you do not understand or agree with, please refrain from using Toggl's applications. Any use or access of the same or any attempt to do so shall be deemed to constitute your consent to be bound by these terms of service. 1. 1.1. "Customer" -- any person or entity that has a valid User Account. "Party" -- each of Customer and Supplier; 1.2. 1.3. 1.4. 2. 2.1. 2.2. 3. 3.1. 3.2. 3.3. 3.4. 3.5. 4. 5.

LumoFlow Web Sticky Notes Vanity — Welcome to Vanity Apollo HQ Comparing Open Source Agile Project Management Tools Comparing Open Source Agile Project Management Tools There are many project management tools designed to support Agile methodologies such as Scrum and eXtreme Programming (XP), including several open source options. This article compares the most compelling open source options on the following criteria: Feature setUsabilityViabilitySuitability for large projects and products Background Agile development methods, including Scrum, XP, Crystal, FDD, and DSDM, have gained widespread adoption and acceptance in recent years. Agile software and open source have enjoyed a tight relationship through the years, with several open source projects being inspired by and integral to the agile movement. Unit testing: XUnit (JUnit, NUnit, etc.), various Mock Objects frameworksAcceptance testing: Fit and FitNesse, HttpUnit, etc.Integration tools: Cruise Control, HudsonBehavior driven development tools… Contenders AgilefantIceScrumAgiloeXPlainPMTXPlanner* Comparison Summary Legend: √ Feature is included Notes: Agilo

Introducing rollout: Condionally roll out features with redis | James on Software Aug 01, 2010 When we work on new features, we like to push them to production regularly. We've found that long-lived branches tend to introduce more defects than short-lived ones. When we're ready to alpha the feature, we'll roll it out to staff. If we do find a problem, we need to be able to disable the feature in real-time. We do all of this using a tool we put together called rollout. How it works gem install rollout I like to assign an instance of Rollout to a global variable. $redis = Redis.new$rollout = Rollout.new($redis) I can check whether a user has access to a feature like this: $rollout.active? Let's say I want to roll out a chat feature. if $rollout.active? The simplest way to start rolling out our chat feature is by giving access to a single user: $rollout.activate_user(:chat, User.find_by_nickname("jamesgolick")) $rollout.active? When alpha testing, it's convenient to be able to provide access to whole groups of users (staff, for example) at once. To provide access to a group:

Related: