Agile methods appear to offer a more dynamic way to drive a project forwards. So, can we derive RAMS requirements in a more efficient manner when working within an agile systems development environment? Recent experience has provided some interesting insights into whether improvements can be realised and how we might capitalise on the more iterative nature of an agile systems development environment. This paper explores recent experiences in the early stages of rail development projects (EN50126 phases 3-5). Applying both a Scrum methodology and a Kanban approach provided two slightly different perspectives from which to learn. This paper looks at the benefits and pitfalls of deriving RAMS requirements within an agile systems development framework. Lessons have been learned around systems modelling, use case development and specialist discipline integration and this paper presents a series of recommendations based on those lessons.