The Appsecute platform aims to improve collaboration and increase productivity through consolidating information associated to an applications lifecycle. The software as a service platform accepts messages directly from people and from integrated technology platforms, then it aggregates those events online for viewing by everyone within an organization.
Open office layout is usually considered the default layout for Agile teams. Cubicle farms are boring and a thing of the past. Open office is known to improve communication, collaboration and build stronger teams. Is it all as good as it sounds?
The 2010 US Scrum Gathering kicked off Monday in Orlando with a buzzworthy day of "deep dive" learning, collaboration, and healthy debate.
Many of us, who are new to Agile, would believe that putting an Agile team together in a room gets the job done. A few of us would actually pay attention to what makes a room a team room which can enhance productivity and motivation. Many Agile teams have already shared their perspective on what would make an ideal team room. Here are a few recent ones.
IBM Rational and InfoQ preent an eBook, Scaling Agile with C/ALM, "dedicated to all of the functional and dysfunctional organizations that are eager to break down the organizational and cultural silos, and become a finely tuned software delivery machine." The eBook explores the barriers to team integration and scaling and then shows, in detail, how to overcome these obstacles.
Gizmox announces the release of a free preview version of its Visual WebGui, version 6.4, product. VWG promises a point-and-click tool for RIA development (DHTML or Silverlight) that requires no HTML, CSS, or XAML coding; and that can be integrated with Photoshop, Expression Blend, and Flash CS.
MindTouch announces the ability to publish content from any Microsoft Desktop application to its collaborative industrial wiki. New user functionality includes: one-click publishing from any MS application and in-place editing of Microsoft Office. The new functionality is delivered as, Aurelia Reporter, Desktop Connector, and MS Word and MS Outlook connectors.
Author and Agile consultant, Mike Cohn recently wrote a blog entry summarizing a chapter in his new book Succeeding With Agile talking about the ideal Agile workspace. He points to things that need to be visible in the space an Agile team works in to help them be more effective.
Demoed at RubyFringe, Github introduced a new service called Gist. While similar to popular paste services, it adds a twist: pasted snippets can be accessed like git repositories, which can be updated from the web interface.
The Linking Open Data Community Project has accomplished a global RESTful SOA giving access to over two billion interlinked statements (RDF triples) from some 50 distributed providers with one serious limitation: this stunning network provides read access only. The upcoming SPARQL Update language is going to overcome this.
What might this be: "envisioned as a decentralised world-wide information space for sharing machine-readable data with a minimum of integration costs"? Is this about REST? Nope. According to SWEO, it is about the Semantic Web. Cool URIs will help making this way. So it might be worth looking whether RESTful SOA URIs can also be "cool".
While Agile processes recommend to colocate team members for synergy, it's not always possible. More and more projects are utilizing talent from locations all over the world to solve various problems. In these cases leaders and facilitators can contribute significantly to teamwork by mastering the ability to run effective remote meetings.
Larger team size prevents from adopting the whole range of language abstraction tools and puts constraints on productivity. Reg Braithwaite believes that tools should not be tuned to the size of the team. He advocates for building teams around the tools and keeping them small. It appears however that team growth is often inevitable. What can be done then to maintain quality and productivity?
Inconsistencies between the user interface and user’s expectations can be an important source of bugs. According to Leonardo Vernazza, this is due the fact that the user and the UI do not talk the same language. Using a DSL, characterized by a high abstraction level, would be instrumental for avoiding the risk of translation errors and would therefore reduce the testing burden.
"Big Visible Charts" aren't unique to Agile - Lean manufacturing also has its Kanban Boards. "Kanban" roughly means "card or sign," and each Kanban card is "pulled" onto the board only when the work represented by an "in progress" card is retired. In this InfoQ article, Kenji Hiranabe proposes using Kanban Boards to track Agile project status (Time, Task, and Team) to enhance collaboration.