Ayende's Rhino.Security is an enterprise authorization framework. I recently added it to my Sharp Architecture project using Billy McCafferty's instructions and some help from Bart Reserhove's blog.
The next step is a spike to implement Rhino.Security authorization and then determining the best course of intercepting queries with permissions. Also, I understand that I can use the event subsystem in NHibernate, instead of an interceptor. I have to check both out.
Friday, February 5, 2010
Scrum: Now, bite sized!
Our small development team has been adopting Scrum using the Lightweight Scrum TFS template.
Adopting. I should say "attempting to adopt".
I have been researching the web for "freesources" on Scrum adoption, the lifecycle of a project, roles, user stories, implementation in a .NET shop, creating of executable specifications, etc.
Wow. Scrum is all over the place -- as in, widespread adoption and many opinions on proper implementation.
Our team is small -- two developers and a Scrum Master. Our initial sprint is for evaluation. We are tracking how to implement using a small bite-size project -- a simple display/edit screen. The user stories as of the moment don't even include authorization. We simply want to evaluate all of the scrum ceremonies and artifacts in action, in a short life-cycle.
What's more, we are also implementing our project using domain-driven design. If that seems like a recipe for failure, I disagree. The luxury we have is low visibility and a small enough team that we can communicate well.
Let's see how this goes.
Adopting. I should say "attempting to adopt".
I have been researching the web for "freesources" on Scrum adoption, the lifecycle of a project, roles, user stories, implementation in a .NET shop, creating of executable specifications, etc.
Wow. Scrum is all over the place -- as in, widespread adoption and many opinions on proper implementation.
Our team is small -- two developers and a Scrum Master. Our initial sprint is for evaluation. We are tracking how to implement using a small bite-size project -- a simple display/edit screen. The user stories as of the moment don't even include authorization. We simply want to evaluate all of the scrum ceremonies and artifacts in action, in a short life-cycle.
What's more, we are also implementing our project using domain-driven design. If that seems like a recipe for failure, I disagree. The luxury we have is low visibility and a small enough team that we can communicate well.
Let's see how this goes.
Subscribe to:
Posts (Atom)