Search Results Heading

MBRLSearchResults

mbrl.module.common.modules.added.book.to.shelf
Title added to your shelf!
View what I already have on My Shelf.
Oops! Something went wrong.
Oops! Something went wrong.
While trying to add the title to your shelf something went wrong :( Kindly try again later!
Are you sure you want to remove the book from the shelf?
Oops! Something went wrong.
Oops! Something went wrong.
While trying to remove the title from your shelf something went wrong :( Kindly try again later!
    Done
    Filters
    Reset
  • Discipline
      Discipline
      Clear All
      Discipline
  • Is Peer Reviewed
      Is Peer Reviewed
      Clear All
      Is Peer Reviewed
  • Series Title
      Series Title
      Clear All
      Series Title
  • Reading Level
      Reading Level
      Clear All
      Reading Level
  • Year
      Year
      Clear All
      From:
      -
      To:
  • More Filters
      More Filters
      Clear All
      More Filters
      Content Type
    • Item Type
    • Is Full-Text Available
    • Subject
    • Publisher
    • Source
    • Donor
    • Language
    • Place of Publication
    • Contributors
    • Location
131 result(s) for "Robson, Sean"
Sort by:
Agile SAP
In this unique book, Sean Robson offers practical advice on the most effective way to see projects through from beginning to end. Basing his strategies on the twelve principles of the Agile Manifesto, and drawing on his vast experience, he particularly focuses on the use of Scrum and Kanban and their suitability for certain types of projects, enabling you to select the most appropriate method for the task in hand. As you read this book, you will learn how to build customer loyalty by delivering consistently high standards and offering greater flexibility and transparency. You will realize cost savings as you analyze your expenditure, reduce waste, and increase efficiencies in the delivery cycle. Effectiveness will increase as you promote greater inter-company collaboration and reduce the stress that so often accompanies large-scale projects. You will be able to eliminate unnecessary paperwork as you improve the clarity of requirements. Late projects, and those that exceed budget, will be a thing of the past!
Evaluating an operator physical fitness test prototype for tactical air control party and air liaison officers : a preliminary analysis of test implications
\"The U.S. Air Force asked the RAND Corporation to assist its development and validation of gender-neutral tests and standards for battlefield airmen (BA) specialties. The Air Force has conducted an extensive validation study of occupational relevance of physical fitness tests and standards. Following the fitness test validation study, one enlisted specialty (Tactical Air Control Party [TACP]) and one officer BA specialty (Air Liaison Officer [ALO]) moved forward with an implementation plan to further evaluate a set of recommended tests and continuation standards. This report describes RAND's assistance to the Air Force on two fronts: (1) conducting a preliminary evaluation of potential issues and concerns that might influence implementation effectiveness and (2) developing a framework for evaluating the implementation of occupationally relevant and specific tests and standards. This work provides the foundation for ongoing review and evaluation of Air Force fitness tests and standards, which are designed to ensure that airmen are capable of performing critical physical tasks associated with their assigned specialties\"--RAND website.
Late Ordovician Conulariids from Manitoba, Canada
Six species of conulariids, assigned to four genera, were recovered from the type locality of the Cat Head Member of the Red River Formation in southern Manitoba, Canada. These are middle Katian (Late Ordovician) in age. The most abundant conulariid species from this locality, Conularia porcella, is new, and is represented by 21 specimens. Additionally, 28 three-dimensionally preserved micromorphic conulariids, assigned to Eoconularia aff. loculata, were recovered using acetic acid preparation from limestone samples of late Katian (Late Ordovician) age. These samples had been collected from Churchill, northern Manitoba, by the Geological Survey of Canada's J. B. Tyrrell in 1894. These taxa are unusually abundant for conulariids, which are normally represented by only a few specimens from any given locality, and this abundance may be a reflection of the exceptional preservation at these two localities.
CAMBRIAN AND ORDOVICIAN LINGULIFORM BRACHIOPODS FROM THE SHALLOW BAY FORMATION (COW HEAD GROUP), WESTERN NEWFOUNDLAND
Linguliform brachiopods were recovered from the Upper Cambrian Downes Point Member (lower Sunwaptan) and from the Middle Ordovician Factory Cove Member (Arenig) of the Shallow Bay Formation, Cow Head Group, of western Newfoundland. These rocks are a series of Middle Cambrian to Middle Ordovician conglomerates, lime mudstones, and shales that formed a sediment apron at the base of the lower Paleozoic continental slope of Laurentia. The linguliform brachiopod fauna consists of sixteen species assigned to twelve genera. Three new species are described: Picnotreta lophocracenta, Neotreta humberensis, and Siphonotretella parvaducta.
BUSINESS BLUEPRINT
The main focus of Agile blueprinting is to build an initial product backlog, and accompanying documents, representing the main requirements for the project. To help clarify requirements, a baseline system can be built to validate requirements. Note that I have labeled these steps as ‘Iteration 0’ and ‘Iteration 1,’ whereas the new ASAP 8 Agile version defines Iteration 0 as the first iteration in realization. Although the nomenclature is different, the process is essentially the same. The demo system should reflect a subset of the backlog requirements and be leveraged in the realization phase. Blueprint is neither Scrum nor Kanban.
REALIZATION
Before getting into the build phase, it is important to revisit the issue of requirements. In an Agile project, the team has not gathered detailed requirements during blueprint. They have kept things “lean” and focused on ensuring they have captured all stories, but they have not gathered all details pertinent to each story. As an example, suppose the project is building the benefits module. During blueprint, the team captured the stories concerning savings plans, but did not go into the eligibility rules for savings plans, other than to capture a child story to solution eligibility rules. This is very different
PROJECT CONCEPTION
When initially defining the project approach to the sponsor, there are some key differences that should be highlighted to the client. An Agile approach favors working software over documentation. What this really means is that we need to avoid documentation for documentation sake. In SAP, we typically create a high number of documents, and not all documents have direct value to the customer. In traditional SAP projects, customers wait a long time before seeing working software. Blueprint phases can be quite long, as the team attempts to gather all details and predict the required design. As you will see, an