InfoQ Homepage Use Cases Content on InfoQ
News
RSS Feed-
Inside InfluxDB 3.0: Exploring InfluxDB’s Scalable and Decoupled Architecture
InfluxData recently unveiled the system architecture for InfluxDB 3.0, its newest time-series DB. Its architecture encompasses four major components responsible for data ingestion, querying, compaction, and garbage collection and includes two main storage types. The architecture caters to operating the DB on-premise and natively on major cloud providers.
-
Real-Time Messaging Architecture at Slack
Slack recently described how it sends millions of messages daily in real-time across the globe. The company provides a comprehensive insight into its architecture, designed to manage real-time messages at scale. It highlights the unique challenges posed by delivering real-time messages across different time zones and regions and how Slack's engineers designed the infrastructure to handle them.
-
Deploying Scrum and SAFe at Philips Lighting
InfoQ interviewed Frank Penning, PMO manager from Philips Lighting, about the main challenges that Philips Lighting is facing in product development, why Scrum is not enough, how they apply SAFe, and the benefits that they have gained from deploying agile methods for product development.
-
Applying Use Cases in Agile: Use Case 2.0, Slicing and Laminating
To incrementally develop and deliver products using agile software development, requirements are gathered and organized into a product backlog. A requirement technique that is used in agile software development is use cases. Some techniques to apply use cases for managing product requirements in agile are use case 2.0, slicing and laminating.
-
Practices for Scaling Agile in Enterprises
Enterprises that are adopting agile organizational-wide will at some time have to scale their agile practices. In a session at the Agile Methods in the Finance Sector and Complex Environment conference, attendees shared their experiences with scaling agile in enterprises.
-
Do Use Cases Have a Place In Scrum?
In Scrum, requirements are commonly expressed as user stories. But is it OK to also make use of use cases in Scrum? And, if so, under what circumstances should you do so?
-
Use Cases or User Stories?
User stories are better than use cases - right? Not necessarily. It depends on whom you ask. There are definite benefits to user stories as they encourage conversation and discourage the "throw over the wall" mentality of more heavy-weight requirements documents. But do they have drawbacks?