agile

This question already has an answer here: What is the difference between Scrum and Agile Development? [closed] 7 answers Mostly people say Scrum and Agile interchangeably but what is the difference between Scrum Practice as compared to Agile Practice ? Agile is a general philosophy regarding software production, Scrum is an implementation of that philosophy pertaining specifically to project management. Scrum is a type of Agile method just like an apple is a type of fruit. Scrum is not the only Agile method though. The popular ones are: Scrum eXtreme Programming (XP) Kanban I'm sure there are

Conceptually related to the independent content-hosting with Git here . I would like to separate 3 things: ticketing -version-control (management), programming -version-control and structural -version-control (more here ). Now everyone should be able to see tickets and how they have evolved from an idea into a code/product. Currently, I have large problems because tickets are in proprietary coffins in Bitbucket and Github, apparently their business strategy to lock users. I want to manage my tickets in some repository -- related tickets here , here and here . If I do a ticket, I want to commit

I am from an XP background. I know the process very well and have solid working experience with it. I have found it to be the best way to develop software. I find myself in the position of a process doctor of sorts and this creates much self examination and revaluation of my own understandings. A very common thing I hear is that some work can’t be made into stories. I personally don’t believe this. The excuses include Its too big (The developer will have nothing to show until the end of 5 weeks). it’s a complicated algorithm or abstract concept (will take 5 weeks to write and nothing to show).

Having used "days" as the unit for estimation of tasks in Scrum I find it hard to change to using Story Points. I believe story points should be used as they are more comparable to each other - being less dependent on the qualifications of whoever addresses the task etc. However, it isn't easy to make a team start using Story Points when they're used to estimating in days. So, how to make a team change to Story Points? What should motivate the team members to do so, and how should we apply the switch? If you want to change to using story points instead of duration, you just got to start

Let's say that a developer is interested in learning Scrum, but nobody else on the team is interested. I realize that Scrum is made for teams, and the process would have to be modified to fit a single person. Is there any benefit to be gained by the developer trying Scrum, even if the team doesn't? If so, how would the process be modified to suit the situation? I think there's benefit to be gained by any method that helps you develop goals, tasks, keep on top of work and deliver something often. Your individual work-products would gain the same advantages that teams gain with scrum: You'd get

I have mixed feelings about TDD. While I believe in testing I have a issues with the idea of the test driving my development effort. When you code to satisfy some tests written for an interface for requirements you have right now, you might shift your focus from building maintainable code, from clean design and from sound architecture. I have a problem with driven not with testing. Any thoughts? No. If done right, Test Driven Development IS your design tool. I hope you forgive me for linking to my own blog entry, wherein I discuss the pitfalls of Test Driven Development that went wrong simply

I'm curious as to what other people use for physical Kanban/Scrum boards in their companies. I appreciate that because of sensitive business information you may not be able to provide a photo of the board. I"m looking at to find out what does your board looks like , and how you organize user stories and tasks as they move through a typical sprint/iteration? Typically I've worked in a places that organize the board as follows with each User Story | Todo | In Progress | Ready for QA | Done | UC-001 | Domain Object, Service | DAO(Bob) | | | UC-002 | Payment UI Screen | | Payment Srv (Don)| | UC

My firm just got its first large-scale development project inquiry and I would like to use an Agile process. The client has a vision for the application but openly admits to having very few requirements and recognizes that we will have to charge by the hour. Because of this, I've all but sold him on an Agile approach. The problem is that he wants a figure to budget around. I've read a number of articles that pretty much advocate against giving up an estimate because the client will budget for that number and even as requirements change, the number in their head and in the books doesn't. I've

I was watching Rob Connerys webcasts on the MVCStoreFront App, and I noticed he was unit testing even the most mundane things, things like: public Decimal DiscountPrice { get { return this.Price - this.Discount; } } Would have a test like: [TestMethod] public void Test_DiscountPrice { Product p = new Product(); p.Price = 100; p.Discount = 20; Assert.IsEqual(p.DiscountPrice,80); } While, I am all for unit testing, I sometimes wonder if this form of test first development is really beneficial, for example, in a real process, you have 3-4 layers above your code (Business Request, Requirements