Michele Pasin / Quotes

#features

Often with #sprint #idea #host #entities #typical-features #criteria #game #customers #schedule #team #list #number

A New Semantic Similarity Based Measure For Assessing Research Publication’s Contribution

Assessing researchers without waiting for citations

important feature of this idea is that our method does not require as long delay for assessment as the widely used cita- tion counts (typically decades) and can be therefore applied also to fairly young researchers.

#idea #features

Dolce-lite-plus

Features (ontology)

Features are 'parasitic entities', that exist insofar their host exists. Typical examples of features are holes, bumps, boundaries, or spots of color. Features may be relevant parts of their host, like a bump or an edge, or dependent regions like a hole in a piece of cheese…

#host #entities #features #typical-features #criteria

Gamasutra - Scrum And Long Term Project Planning For Video Games

Customers control scope through the backlog

One major benefit gained from transitioning from deterministic schedules to iterative planning cycles is that the customers assume more control over the schedule and budget by manipulating the scope. This is done by continually prioritizing the list of features that they want…

#game #customers #features #schedule

Scrum (software Development) - Wikipedia, The Free Encyclopedia

Sprint backlog (scrum)

The sprint backlog is the list of work the Development Team must address during the next sprint. The list is derived by selecting stories/features from the top of the product backlog until the Development Team feels it has enough work to fill the sprint. This is done by the…

#sprint #team #features #list #number #lines

User story and epics (scrum)

A feature that is added to the backlog is commonly referred to as a story and has a specific suggested structure. The structure of a story is: "As a I want to so that " This is done so that the development team can identify the user, action and required result in a request and…

#action #group #sprint #features #results #levels

The Transaction Manifesto: A Direction For Nosql Database Technology

Database transaction

A transaction is a set of database reads and writes that is handled as a unit with a few crucial properties. First, all reads in the transaction see the same snapshot of the database (e.g. do not see changes to the data resulting from other transactions executing concurrently)…

#database #acid #features