• Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
  • Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!

Agile is Tulip!

Collapse
X
  •  
  • Filter
  • Time
  • Show
Clear All
new posts

    #51
    Originally posted by aussielong View Post
    You need a business architect involved at every scrum, that understands everything end to end , because people tend to lose the big picture in agile.
    Conveying the big picture is the Product Owner's job in Scrum (Or business visionary in DSDM etc). All of these methodologies rely on communication - and if communication is bad it doesn't matter what methodology you're using, you're going to fail.
    ...my quagmire of greed....my cesspit of laziness and unfairness....all I am doing is sticking two fingers up at nurses, doctors and other hard working employed professionals...

    Comment


      #52
      Originally posted by aussielong View Post
      You need a business architect involved at every scrum, that understands everything end to end , because people tend to lose the big picture in agile.
      It's generally good to hire as many non-developers as possible, you definitely don't want more than 10% of the team actually doing any tangible work. So you probably want a business architect, business analyst, data architect, enterprise architect for each couple of developers on the project, as well as a half-dozen testers and a test manager. Possibly you'll want a test architect as well.
      Originally posted by MaryPoppins
      I'd still not breastfeed a nazi
      Originally posted by vetran
      Urine is quite nourishing

      Comment


        #53
        Originally posted by d000hg View Post
        It's generally good to hire as many non-developers as possible, you definitely don't want more than 10% of the team actually doing any tangible work. So you probably want a business architect, business analyst, data architect, enterprise architect for each couple of developers on the project, as well as a half-dozen testers and a test manager. Possibly you'll want a test architect as well.


        POTD.

        I guarantee somebody somewhere is now thinking "we haven't got a test architect, that must be why it's all going wrong"
        While you're waiting, read the free novel we sent you. It's a Spanish story about a guy named 'Manual.'

        Comment

        Working...
        X