Dr. Dobb's Journal - July 2008 - (Page 62)

Instantly Search Terabytes of Text N dozens of indexed, unindexed, fielded data and full-text search options (including Unicode support for hundreds of international languages) N file parsers / converters for Common Agile Project Roles There are several roles common to agile teams. Sometimes a person will take on several roles and sometimes several people may be in the same role. Each role is briefly described and common synonyms indicated for most. Some synonyms are inappropriate within the context of agile projects and some are inaccurate. The common agile project roles are: • • Agile DBA. This person works closely with developers and technical experts to support data-oriented activities on team. Architecture Owner. This person is responsible for the architecture of the system, or subsystem, that the team is working on. Architecture owners don’t develop and then dictate the architecture, but instead they facilitate the identification of the architecture, actively help to implement it, guide the implementation of the (sub)system, and mentor developers in the architecture and in architecture skills. Also known as technical lead and architect (inappropriate due to the collaborative leadership nature of the role). Developer. This person models, writes, tests, and documents the system. Also known as programmer (inaccurate due to the scope of the role). Domain Expert. This person has expertise in one or more aspects of the domain. This includes support staff, business specialists, business executives, auditors, and the “gold owner”. Also known as a subject matter expert (SME). Independent Tester. This person performs continuous, investigative testing throughout the lifecycle to find defects that were not discovered by the development team’s testing efforts. Also known as tester, investigative tester, and quality assurance (inaccurate due to the scope of the role). Product Owner. This person represents the stakeholder community. They are responsible for prioritizing the requirements and are the primary source of domain information. Also known as customer, stakeholder representative, and end user (inaccurate as end users are only one of many stakeholders). Team Coach. This person is responsible for keeping the team on track, for helping team members deal with problems, and for helping the team to secure necessary resources. Also known as team lead, Scrum master, and project manager (inappropriate as this is primarily a leadership role and agile teams are self-organizing). Technical Expert. This is a person with expertise in one or more technical aspects of the system. This could be a security person, a build expert, a tool smith, a legacy data owner, an operations staff member, or many other technical roles. They are brought on to the team on an as needed basis for a short period of time, sometimes just a few hours or days, to help them address a technical issue. Also known as subject matter expert (SME). hit-highlighted display of all popular file types N Spider supports static and dynamic web data; highlights hits while displaying links, formatting and images intact N API supports .NET, C++, Java, databases, etc. New .NET Spider API • • • • h Spider Desktop wit h Spider Network wit CD/DVDs Publish for ider Web with Sp Win & .NET Engine for Linux Engine for • New 64-bit • The Smart Choice for Text Retrieval ® since 1991 N “Bottom line: dtSearch manages a terabyte of text in a single index and returns results in less than a second” – InfoWorld N “For combing through large amounts An interesting observation is that as the size of the team grows, there is very little difference in the day-to-day activities of developers. They are insulated from the complexities of large teams by activities of the coordinators. of data,” dtSearch “leads the market” – Network Computing N dtSearch “covers all data sources Size Matters If you don’t see your traditional job role on the diagrams, there’s a good reason—the work is likely being done, but in a different manner. For example, product owners and developers do business analysis, yet the role of business analyst doesn’t appear in any of the diagrams. I often work in organizations that have traditional roles such as business analyst, quality assurance analyst, architect, designer, and so on in their organization/process charts. Invariably these organizations are still transi- powerful Web-based engines”– eWEEK N dtSearch “searches at blazing speeds” – Computer Reseller News Test Center See www.dtsearch.com for hundreds more reviews, and hundreds of developer case studies tioning to agile and are still in the process of evolving their culture to reflect agile philosophies. It takes time, often several years, to shift to the agile paradigm. Perhaps the spam is right after all—size does in fact matter because it is one of the determinants of your team organization. The agile community is in the process of rediscovering the divide-and-conquer techniques of yesteryear, applying them in more collaborative and lean ways, but inevitably in a manner that experienced IT professionals will quickly recognize. DDJ Contact dtSearch for fully-functional evaluations Scott is Practice Leader Agile Development for IBM Rational. 1-800-IT-FINDS www.dtsearch.com 62 Dr. Dobb’s Journal l www.ddj.com l July 2008 http://www.dtsearch.com http://www.dtsearch.com http://www.ddj.com

Table of Contents Feed for the Digital Edition of Dr. Dobb's Journal - July 2008

Dr. Dobb's Journal - July 2008 Contents Friday Night Fish Fry Alia Vox Developer Diaries Developer’s Notebook Engineers Without Borders Conversations Patricia Tries Event-Based Architectures Graphs Versus Objects Lock-Free Queues Dr. Dobb’s Architecture & Design World Java and the Nokia N10 Internet Tablet Effective Concurrency The Agile Edge Swaine’s Flames

Dr. Dobb's Journal - July 2008

For optimal viewing of this digital publication, please enable JavaScript and then refresh the page. If you would like to try to load the digital publication without using Flash Player detection, please click here.