![commenteer commenteer](https://uploads.celebrityinsider.org/uploads/2021/04/ammika-harris-even-makes-blank-staring-a-full-time-modeling-flex-1.jpg)
And if you build shippable, workable software each sprint, well, you always have something potentially useful to deliver.
COMMENTEER HOW TO
Effort estimates (as long as they know how to do the work) aren’t that important. Several developers I know only \break down their work into identifiable tasks. Depending on your project, you may simply work off a backlog, not necessarily do any estimates to forecast how much you can accomplish. (Not all of the GitHub projects were open source ones, but still…). Is this an affirmation of the No Estimates movement, or just how people work on certain kinds of projects? Open source projects are quite different from product development. On small projects (10 people or less), 55% of the respondents said they did not estimate their stories on a daily basis. This paper raised as many questions in my mind as it answered. Fortunately we also had more time to discuss her work over lunch. I had three short minutes after the presentation to carry on a dialog with Olga about their findings. The paper I commenteered, “Why We Need a Granularity Concept for User Stories” by Olga Liskin and her colleagues, reported on results gleaned from surveying developers (who self-selected themselves as agile developers) working on both private and open source projects on GitHub. If you go to the Open University’s website you’ll see these topics listed under their Empirical Studies PhD program: The emergence of Agile software development, the role of physicality and co-location in agile software development, and XP and end user developmentĪgile software development is being studied and data being collected. If the research papers I sampled are an indicator, PhD students seem to be busy doing empirical studies on agile practices, processes, and values. In addition, four experience reports were published (in contrast, 27 experience reports will be published and presented this year at the Agile Conference). Short papers touched on agile organizational transformations, Randoori Coding Dojos, and how expertise is located on agile projects. Research topics were wide-ranging including a case study on UX Design, a survey of user story size and estimation accuracy, another on agile development practices, a case study on visualizing testing, another on agile and lean values, and one comparing scripted with exploratory testing. The XP 2014 paper acceptance rate was somewhat selective, with over 50% of the submissions rejected. I listened to several research presentations and volunteered to be a commenteer for one research paper. Unlike other agile conferences I’ve attended, research is a prominent part of this conference. I also sampled research AND non-research sessions in equal measure. I gave a workshop on Understanding Design Complexity (using commonality-variability analysis) and a tutorial on Agile Architecture Values and Practices. Ambrose is, “si fueris Romae, Romano vivito more si fueris alibi, vivito sicut ib,” or “if you should be in Rome, live in the Roman manner if you should be elsewhere, live as they do there.”Īs Italians do, I enjoyed good food, good company, and great wine.
![commenteer commenteer](https://www.gamekings.tv/wp-content/uploads/20160606_e3vooruitjelle_splash-180x180.jpg)
As they say, “when in Rome, do as the Romans do.” The actual quote attributed to St.
![commenteer commenteer](https://creators-images.vice.com/content-images/contentimage/no-slug/ca6026057d0a17c206cefcc6b99cc61d.jpg)
I attended my first XP conference in Rome in May.