{"text_format":"2","workbook":"xls","n_sheets":1,"sheets":["report2"],"not_rendered":{"charts":0,"images":0,"macros":0,"external_links":1,"defined_names":1,"comments":0,"pivot_tables":0},"unopened":[],"bounds":{"document_bytes":16777216,"sheet_cells":100000,"run_cost":"one","rows_first":2000,"rows_last":500,"rows_between":2000,"halvings":0,"cell_chars":16384,"cell_head_chars":4096},"cells_cut":0,"cells_raw":0,"read":"whole","date_system":"1900","formulas":"cached_only"}

{"sheet":"report2","index":0,"n_rows":12,"n_cols":5,"rows_kept":12,"cut":false,"hidden":false,"merged":[[0,2,0,3],[0,4,0,5],[1,2,1,3],[1,4,1,5],[2,2,2,3],[3,2,3,3],[4,2,4,3],[5,2,5,3],[6,2,6,3],[8,2,8,3],[9,2,9,3]],"flags":["formulas_cached_only"]}
[null,"1.","Record Nr.",null,"UNINA9910305147403321"]
[null,null,"Titolo",null,"ISO/IEC/IEEE 26515:2018(E) ISO/IEC/IEEE International Standard - Systems and software engineering - Developing information for users in an agile environment / / Software & Systems Engineering Standards Committee of the IEEE Computer Society"]
[null,null,"Pubbl/distr/stampa",null,"New York : , : IEEE, , 2018"]
[null,null,"ISBN",null,"1-5044-5297-6"]
[null,null,"Descrizione fisica",null,"1 online resource (32 pages)"]
[null,null,"Collana",null,"ISO/IEC/IEEE ; ; 26515"]
[null,null,"Soggetti",null,"Agile software development"]
[{"$nulls":4},"Software engineering"]
[null,null,"Lingua di pubblicazione",null,"Inglese"]
[null,null,"Formato",null,"Materiale a stampa"]
[null,null,null,"Livello bibliografico","Monografia"]
[null,null,null,"Sommario/riassunto","This document provides requirements and guidance to information developers and related roles on how to adapt the processes described in the ISO/IEC/IEEE 265NN family of International Standards to develop quality information for users. This document is independent of the agile development methods and tools that are used to produce the software. This document gives an overview of agile methodologies although it neither encourages nor discourages the use of any particular agile methodology. Therefore, this document uses generic agile terminology as much as possible."]